Solution ER605 ER7206 - “Use Fixed IP Address” (DHCP Reservation) Doesn't Take Effect.
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.
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!
Please be sure you have read the Beta Test Agreement before proceeding!
*The above beta firmware is adapted to Omada Controller v5.5, not for Controller v5.6.
**The above ER7206 1.2.3 official firmware is available in the cloud, fully adapted to Omada Controller v5.6.
Recent Solution Post:
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.
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
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.
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.
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.
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!
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!