Solution ER605 ER7206 - “Use Fixed IP Address” (DHCP Reservation) Doesn't Take Effect. [Thread Closed]
Update as of Jan 30th 2023:
Thank you all for your feedback on this forum to let us know that the DHCP issues are still existed, and more importantly, thanks for our loyal users who worked with our support engineers to figure out the issue with great cooperation.
Please follow the solution post below for the new beta firmware to fix all the DHCP issues that have been located.
ER605 ER7206 v1 - DHCP Server May Fail With 1.2.0 and 1.2.1 Firmware
As the above solution post has already updated the Beta firmware for the DHCP issues, and will be updated if there is any new DHCP issues came up, so this old thread will be locked to stop updating.
Thank you all for your great patience when we're trying to figure out the issue and fix it!
Any further issues with the above Beta firmware, please feel free to Start a New Thread from HERE.
Updated on Nov 11st 2022:
Update the firmware to fix all the DHCP issues that have been reported to the support team, including the issue
- DHCP Server failed to assign valid IP addresses to some clients. Reported Here.
- Different clients have duplicated IP address on the Omada Controller. Reported Here.
- Offline wireless clients were still shown up in Clients list and reported as connected to the Omada Router. Reported Here.
Note:
ER605 v2 ONLY have the last DHCP issue mentioned above, which is a mis-report by the router.
Please scroll down for the Available Solutions part for the Beta firmware. Thank you!
Beta Firmware Download:
Please be sure you have read the Beta Test Agreement before proceeding!
ER605(UN)_v1_1.2.2_Build 20221015 (Beta)
ER605(UN)_v2_2.0.2_Build 20221025 (Beta)
*The above beta firmware is adapted to Omada Controller v5.5, not for Controller v5.6.
ER7206_v1_1.2.3 Build 20221104
**The above ER7206 1.2.3 official firmware is available in the cloud, fully adapted to Omada Controller v5.6.
Recent Solution Post:
ER605 ER7206 v1 - DHCP Server May Fail With 1.2.0 and 1.2.1 Firmware.
Updated on Sep. 21, 2022:
Remove the 0918 Beta firmware as some users reported it causes CPU spikes issue.
Updated on Sep. 19, 2022:
Update the Beta firmware and add the latest Beta firmware for ER605 v2/ v2.6, which have added the fix that Omada Router may wrongly report the clients status to the Omada Controller, causing the issue that offline clients were still shown up in the Controller Clients list, and connected to the Omada Router (instead of the SSID or network). For more details, check this related post.
Updated on Sep. 16, 2022:
Update the Beta firmware for ER605 v1 and ER7206 v1 with the latest version, which has fixed the recent DHCP failure issue. For more details, please check out the solution post below.
ER605 ER7206 v1 - DHCP Server May Fail With 1.2.0 and 1.2.1 Firmware.
Updated on July 28, 2022:
Add the beta firmware for ER7206 v1 and ER605 v2.
Updated on July 27, 2022:
With the release of the 1.2.1 firmware, we received some feedback that the DHCP Reservation stops taking effect after upgrading to the 1.2.1 firmware, while reverting to 1.2.0 firmware doesn't have the issue.
For example, you've reserved a fixed IP 192.168.0.150 for some clients (including IOT clients, PC, Printer, etc.), most of them would obtain the reserved IP addresses, but some of them wouldn't. The impacted clients may obtain the reserved IP addresses after several reboots on the clients and the router, but after running for some time, the problem occurs again.
After further troubleshooting and investigation with our community members @PapyPom, @Riverfront, @Skeidinho, (thank you all so much for your great cooperation!), the R&D team has finally addressed the issue.
Available Solutions Updates:
The following Beta firmware can fix the DHCP Reservation issue on both 1.2.0 (or 2.0.1) and 1.2.1 firmware, and the subsequent official firmware will add the fix soon. As a temporary solution, you may install the Beta firmware below to fix the issue, (the beta firmware for ER7206 v1 and ER605 v2 will be provided gradually, please wait patiently).
Updated on Sep. 16, 2022:
Update the Beta firmware for ER605 v1 and ER7206 v1 with the latest version, which has fixed the recent DHCP failure issue.
ER605_v1_1.2.1_Build 20220726 (Beta)
ER7206_v1_1.2.1_Build 20220727 (Beta)
ER605_v2_2.0.2_Build 20220727 (Beta)
Newer version >> ER605(UN)_v1_1.2.2_Build 20220902 (Beta)
Newer version: >> ER7206(UN)_v1_1.2.2_Build 20220902 (Beta)
Updated on Sep. 19th 2022:
Newer version >> ER605(UN)_v1_1.2.2_Build 20220918 (Beta)
Newer version >> ER7206(UN)_v1_1.2.2_Build 20220918 (Beta)
Newer version >> ER605(UN)_v2_2.0.2_Build 20220918 (Beta)
Note: Please be sure you have read the Beta Test Agreement before proceeding!
Thank you all for your huge support and patience!
This Article Applies to:
ER605(UN)_V1_1.2.0 Build 20220114 and earlier firmware
ER7206(UN)_V1_1.2.0 Build 20220117 and earlier firmware
Background:
Omada SDN Controller v5.0 has supported to configure DHCP Reservation for Omada Devices (mentioned HERE), and also support to reserve static IP address outside the DHCP Range (mentioned HERE). Besides, the DHCP issue caused by wrong configuration (duplicated DHCP reservation) has also been fixed completely with the gateway 1.2.0 official firmware (mentioned HERE).
However, we noticed that there are still some feedback on the "Use Fixed IP Address" (DHCP Reservation) issue after Omada Controller v5.0 (check Here for update) and Gateway 1.2.0 official firmware (check Here for update) is released.
Issue Description/Phenomenon:
Configuring the "Use Fixed IP Address" on Omada SDN Controller for some clients (IOT devices) doesn't take effect. For example, set static IP 192.168.0.150, the client consistently gets a different address after restart.
For more details, you may check for the following threads.
Use Fixed IP Address not working.
IP address reservation still not working reliably
Thanks for all of your effort to work on the issue.
After further investigation and tests, TP-Link support team has addressed the problem finally.
Available Solutions:
The R&D team has made a Beta firmware to adapt to the behavior of the IoT devices accordingly.
Welcome to install and verify that it can resolve your issue effectively.
ER605(UN)_v1_1.2.0_Build 20220328 (Beta)
ER7206(UN)_v1_1.2.0_Build 20220328 (Beta)
Note: Please be sure you have read the Beta Test Agreement before proceeding!
[Case Closed] Update:
The issue has been fixed in the official 1.2.1 firmware, please check for an update from Here.
Thank you for your attention!
Feedback:
Still doesn't take effect for your clients with the Beta firmware above?
It might be a different case, please don't hesitate to comment below for further assistance.
Looking forward to hearing from you for the test results of the above Beta firmware!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Fae Thanks for all your help and support. Updating to the beta version seems to have worked for me. My cameras are now back to their reserved addresses. But...I will continue to monitor to see if any other 'side effects' should appear with this beta.
- Copy Link
- Report Inappropriate Content
Hi All,
The beta firmware for ER7206 v1 and ER605 v2 has just been provided. Thank you for your attention!
Fae wrote
Updated on July 28, 2022:
Add the beta firmware for ER7206 v1 and ER605 v2.
The following Beta firmware can fix the DHCP Reservation issue on both 1.2.0 (or 2.0.1) and 1.2.1 firmware, and the subsequent official firmware will add the fix soon. As a temporary solution, you may install the Beta firmware below to fix the issue,
- Copy Link
- Report Inappropriate Content
@Fae I'm running 2.0.2 Build 20220727 Rel.68295 on me ER605, and it's fixed the stealth ports problem (Omada Gateway Cannot Get Full Stealth On The GRC ShieldsUp Test. - Business Community (tp-link.com)). However, address reservation is now broken!
I have lots of reserved addresses on my network, but since installing version 2.0.2 beta, when rejoining the network the devices are being assigned new IP addresses.
Are there any fixes to get my address reservation back, other than reverting to the previous non-beta firmware (if indeed that's possible)?
- Copy Link
- Report Inappropriate Content
Dear @gruntfuttock,
gruntfuttock wrote
@Fae I'm running 2.0.2 Build 20220727 Rel.68295 on me ER605, and it's fixed the stealth ports problem (Omada Gateway Cannot Get Full Stealth On The GRC ShieldsUp Test. - Business Community (tp-link.com)). However, address reservation is now broken!
I have lots of reserved addresses on my network, but since installing version 2.0.2 beta, when rejoining the network the devices are being assigned new IP addresses.
Are there any fixes to get my address reservation back, other than reverting to the previous non-beta firmware (if indeed that's possible)?
Sorry for any trouble caused! The 2.0.2 beta firmware is made to fix the stealth ports issue, which hasn't added the fix for the address reservation yet. However, the beta firmware provided in this post has fixed both issues, please install the beta firmware in this thread instead. I'll replace the beta firmware in the post(Omada Gateway Cannot Get Full Stealth On The GRC ShieldsUp Test.) soon.
- Copy Link
- Report Inappropriate Content
Dear @NotYoNetwork,
NotYoNetwork wrote
Will there be a Beta for the TL-R605? This is the model of my gateway, this model is also having issues with reserved DHCP addresses
TL-R605 is a former name for ER605, please be free to install the firmware of ER605.
- Copy Link
- Report Inappropriate Content
Hello,
I have been using firmwares 1.2.0 and 1.2.1 stable for a while and have been having the aforementioned DHCP issues. I found this thread and tried the beta firmware for my ER605 V1 and it still does not work. This has been quite frustrating as I rely on a number of devices maintaining a static IP. Is there any progress on this?
If the additional information is useful, the three devices are an old android tablet, a raspberry pi with an asus usb wlan adaptor, and a smart inverter. I have tried setting a static IP in the configurations of the devices and removed the reservations in omada, but the device still ended up with a random IP, even though the reserved address was free. A number of devices have reserved addresses on the network that have remained functional though. All the omada hardware seems to remain on the allocated address, as well as IP cameras and a NAS. On the wifi side, I have a number of smart devices with fixed IP's configured on device which have remained on their allocated addresses without reservation in omada.
- Copy Link
- Report Inappropriate Content
Dear @jonod,
jonod wrote
If the additional information is useful, the three devices are an old android tablet, a raspberry pi with an asus usb wlan adaptor, and a smart inverter. I have tried setting a static IP in the configurations of the devices and removed the reservations in omada, but the device still ended up with a random IP, even though the reserved address was free.
Do you mean that static IP addresses configured on these devices (an old android tablet, a raspberry pi with an asus usb wlan adaptor, and a smart inverter) instead of on the ER605 router via Omada Controller would still end up with a random IP but not the reserved IP addresses?
If the static IP address configured on the wireless client itself doesn't take effect either, it's possible that the reserved IP is already taken by other clients in the network, thus the wireless client choose to obtain an IP address from the DHCP.
How did you confirm that the reserved addresses were free? If convenient, could you please shut down your device (such as the old android tablet) and then ping the IP you want to reserve on the device for confirmation?
- Copy Link
- Report Inappropriate Content
My apologies @Fae, I have many of the devices on my network on daily reboot schedules, as well as most of my omada network. It appears as if everything is now working on the beta software now that its had some to settle. I had rebooted everything before but had no luck. I look forward to DHCP working correctly on the next stable version.
With regards to the fixed IP's on the devices, yes it was set to fixed on the device and it would still end up on a random IP. I had checked that nothing was using the IP's using the omada clients list but I have noticed that it is not always up to date/accurate, and also a network scanner app on my phone. I had not attempted to ping the IP's as it did not look like there was anything there. I had also attempted multiple reconnects with both the IP reservation in place (validating that the MAC addresses were correct) and deleted from the table.
- Copy Link
- Report Inappropriate Content
Dear @jonod,
jonod wrote
My apologies @Fae, I have many of the devices on my network on daily reboot schedules, as well as most of my omada network. It appears as if everything is now working on the beta software now that its had some to settle. I had rebooted everything before but had no luck. I look forward to DHCP working correctly on the next stable version.
With regards to the fixed IP's on the devices, yes it was set to fixed on the device and it would still end up on a random IP. I had checked that nothing was using the IP's using the omada clients list but I have noticed that it is not always up to date/accurate, and also a network scanner app on my phone. I had not attempted to ping the IP's as it did not look like there was anything there. I had also attempted multiple reconnects with both the IP reservation in place (validating that the MAC addresses were correct) and deleted from the table.
That's all right. Glad to hear that it works finally! If there is anything new came up, welcome to let us know. Have a nice day!
- Copy Link
- Report Inappropriate Content
Dear @NotYoNetwork,
NotYoNetwork wrote
@Fae just wanted to add, that my DHCP is now also working with the beta.
Thanks for your kind feedback!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 4
Views: 22486
Replies: 57