Fixed IP Address NOT working
I'm starting to get annoyed with the inability of this TP-Link equipment to maintain a designated FIXED IP address on a device.
I need to assign static IP addresses to my IOT devices (sadly, the devices in question I'm having problems with are TP-LINK devices as well !!) to ensure smooth operation with my home automation solution.
I have gone ahead and used a Fixed IP Address:
NOTE .. The IP address does not match the fixed ip address.
Forcing the client to reconnect will temporarily solve the issue but the device will eventually fall back to a DHCP assigned address.
As a workaround and to try to resolve the issue I assigned all my IOT devices an address between 192.168.50.10 and 192.168.50.49.
I then continually force reconnected all the devices until they had their properly assigned fixed IP address.
Lastly,I went into my DHCP settings and set the starting range to be 192.168.50.50:
NOTE: The Omada SDN will NOT allow you to manually input an IP address that falls outside of the defined DHCP range. To get around this, you have to change them BEFORE modifying your range.
Not sure what else I can do but surely I'm not the only one experiencing this issue.
Is this known to TP-Link ? Is it slotted to be resolved anytime soon ?? Is there a work around that actually works ???
As an FYI : Here is a screenshot of my devices and their versions (running the latest version on everything):
I am running the latest version of the Omada Software controller :
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @Omikomi, @Koboldo, @MaziarR, @TandS, and other community members,
Sorry for any trouble caused. After further troubleshooting and investigation with @PapyPom (Thank @PapyPom so much for your great cooperation!), the R&D team has finally addressed the issue.
As a temporary solution, the following solution post has provided the Beta firmware to fix the issue, other beta firmware will be provided gradually, and the subsequent official firmware will add the fix soon.
Solution ER605 ER7206 - “Use Fixed IP Address” (DHCP Reservation) Doesn't Take Effect
Thank you all for your huge support and patience!
- Copy Link
- Report Inappropriate Content
Hello @tsmithf, @ANILE8, @pnprv, @anthonype,
The following official firmware has already fixed all the DHCP issue we received in the community.
ER605 V1_1.3.0 Official Firmware (Released on May 17th, 2023)
Note: the firmware is applied to ER605 V1 and V1.60.
ER605 V2_2.1.2 Official Firmware (Released on Feb 14th, 2023)
Note: the firmware is applied to ER605 V2 and V2.60.
If you still have some issues even though your ER605 is running with the above or newer firmware version (you can tell which firmware is newer by the Build number), and you have tried reboot with no luck, I'd encourage you click here to start a new thread to elaborate the issue for further assistance, this will help you get the answers or solutions more quickly.
BTW, the Lock to AP feature requires to update the EAP firmware to the adapted firmware. The following post has provided some EAP device firmware for early access, which has added support for the Lock to AP feature. @tsmithf, @ANILE8 you may have a check.
EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Aug 15th, 2023)
- Copy Link
- Report Inappropriate Content
How about do not change the DHCP IP range? Leave it on 50.10-50.254, can Clients get the right fixed IP address?
- Copy Link
- Report Inappropriate Content
yeah,
I run fixed ip addresses in the DHCP range and according to my insight logs , the hosts which have it configured , seem to consistently recieve the same ip
( annoyingly you don't have 1 screen to see all fixed ip's ) all seem to have a fixed ip adress , even for devices which are off longer then the lease time.
- Copy Link
- Report Inappropriate Content
@Virgo In this case, Changing the DHCP range isn't having any effect.
I'm not a network expert but I believe in practice it is common, when having to use a pool of fixed IP address to place them outside the DHCP range.
This was also a suggested workaround.
NOTE: The router allows this in stand alone mode.
My setup has my fixed IP address in the range of 192.168.50.3 - 192.168.50.45 and so I setup my DHCP range for all other device to be 192.168.50.50 - 192.168.50.254.
Sadly some devices set to have fixed IP addresses still get overridden IP address inside the DHCP range.
Here is another example..
- Copy Link
- Report Inappropriate Content
@TandS
You ever make any progress on this? I'm apparently having the same problem. At the moment, I have a very simple network with only one LAN. DHCP pool is 192.168.0.10-.254
Using all Omada equipment: ER605 gateway, TL-SG2218 switch, and EAP-245s.
Setting the "Use Fixed IP Address" is not working and the client consistently gets a different address, even after forcing a disconnect.
- Copy Link
- Report Inappropriate Content
ER605 v1.0
Version 1.2.0
TL-SG2008P v1.0
Version 1.0.2
EAP660 HD(Canada) v1.0[Custom]
Version 1.0.0
Same situation TP-Link please issue fix
- Copy Link
- Report Inappropriate Content
Dear @TandS, @supermarkert, @iscandium,
Thank you for your valuable feedback!
Regarding the "Use Fixed IP Address" doesn't take effect issue, the R&D team has made a Beta firmware trying to fix the issue.
Welcome to install the Beta firmware and comment with your feedback from the solution post below:
Solution ER605 ER7206 - “Use Fixed IP Address” (DHCP Reservation) Doesn't Take Effect
- Copy Link
- Report Inappropriate Content
@Fae I am still seeing issues with fixed IP address assignments not taking effect. Both wirelessly connected through EAP access points and hardwired connections.
I am using a TL-R605 v1 Gateway on firmware 1.2.1, Omada SDN controller v5.3.1.
Any help would be greatly appreciated.
- Copy Link
- Report Inappropriate Content
Dear @geaston,
geaston wrote
@Fae I am still seeing issues with fixed IP address assignments not taking effect. Both wirelessly connected through EAP access points and hardwired connections.
I am using a TL-R605 v1 Gateway on firmware 1.2.1, Omada SDN controller v5.3.1.
Sorry to hear that you still have the issue. To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue.
The ticket ID is TKID220710506, please check your email box and ensure the support email is well received. Thanks!
- Copy Link
- Report Inappropriate Content
@Fae I also have the issue - TL-R605 v1.0 with firmware 1.2.1, just tried a bunch of reboots, the DHCP reservation fails (the requested address is of course available). Controller OC200, firmware 5.1.7.
EDIT : It's halfway broken : I can set a new IP, and it will set the device to that IP, but when I want to set it up at the IP it had before the firmware upgrade, it fails.
- Copy Link
- Report Inappropriate Content
Dear @PapyPom,
PapyPom wrote
@Fae I also have the issue - TL-R605 v1.0 with firmware 1.2.1, just tried a bunch of reboots, the DHCP reservation fails (the requested address is of course available). Controller OC200, firmware 5.1.7.
EDIT : It's halfway broken : I can set a new IP, and it will set the device to that IP, but when I want to set it up at the IP it had before the firmware upgrade, it fails.
Thank you for your kind feedback! So the DHCP reservation now works well after you set a new fixed IP address on those devices?
Could you please try to ping the IP address you set before the firmware upgrade and see if you can get a reply, or use "arp -a" command to check the ARP entries and see if you can find that IP address?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 14664
Replies: 42
Voters 0
No one has voted for it yet.