Solution ER605 ER7206 - “Use Fixed IP Address” (DHCP Reservation) Doesn't Take Effect. [Thread Closed]
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
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
solved it for the cameras (vlan2) but did NOT solve it for the Unraid server (vlan3), it always gets dynamic IP what ever I set.
- Copy Link
- Report Inappropriate Content
Dear @DontAskMe,
DontAskMe wrote
solved it for the cameras (vlan2) but did NOT solve it for the Unraid server (vlan3), it always gets dynamic IP what ever I set.
Thank you for your valued feedback! Could you please add more details about the issue that the Unraid server always gets dynamic IP? I'll follow up with your case in this post.
- Copy Link
- Report Inappropriate Content
EDIT
- Copy Link
- Report Inappropriate Content
Dear @btx,
btx wrote
@fae I am only today on this location (it is 600km away from my home) and if you have any suggestions or some new beta which I could test, then I could do it only today. It is not really critical, the company where it runs is ok with it as long as all other devices work, but they feel very uncomfortable running beta's. I have no remote access to the company, I will get it, but probably it will take few days, however, I do not feel comfortable to upgrade and downgrade omada and er605 over remote, as if anything goes wrong, company will be cut off the internet. Could you try to reproduce steps above?
EDIT: for some reason, steps above messed up dns configuration, I've fixed it by resetting router and setting up new omada controller. Reproducing steps above resulted yesterday in no error.
Sorry for my delayed response. Beta firmware is mainly used to fix a certain issue quickly, I'm afraid that I don't have other new beta for the issue you described above.
And thank you for your kind update on the case, glad to hear that you've fixed it finally. It's suggested to save the current backup config file in case you have to restore the configuration in the future. If there is anything new came up, welcome to let us know.
- Copy Link
- Report Inappropriate Content
EDIT
- Copy Link
- Report Inappropriate Content
From this thread for me it's not clear if this bug has caused only the IP reservation not taking effect or the router itself becoming unaccessable after the firmware update to v1.2.0 official firmware? ...as it happened in my case.
- Copy Link
- Report Inappropriate Content
EDIT
- Copy Link
- Report Inappropriate Content
Dear @Arion,
Arion wrote
From this thread for me it's not clear if this bug has caused only the IP reservation not taking effect or the router itself becoming unaccessable after the firmware update to v1.2.0 official firmware? ...as it happened in my case.
Your case is a different issue, it has nothing to do with the DHCP reservation issue described here. I'll give more details in your previous post (link).
Back to this solution post, I'd like to add that the main cause of the issue is related to the way how the wireless clients handle the ICMP request from the DHCP server. The Beta firmware only did a modification to adapt to the behavior of those wireless clients.
In addition, you may notice the start of this thread saying that this article applies to ER605 / ER7206 1.2.0 and earlier firmware. Also, it only describes the issue of the DHCP reservation, whose phenomenon is that clients consistently gets a different address after restart. Basically, if the issue you have only exists on a specific firmware, or it doesn't match the Issue Description/Phenomenon given in this thread, then it's probably that this solution post is not for your case.
Thank you for your attention!
- Copy Link
- Report Inappropriate Content
@Fae Any idea when the non beta version will come out for this?
- Copy Link
- Report Inappropriate Content
Hi there,
Here is an update on the DHCP Reservation issue, please have a check. Thank you for your attention!
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.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 4
Views: 21769
Replies: 63
Voters 2
