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
I have to ask it here because I've only seen posting the new betas in this DHCP Reservation issue thread:
Does this newest available v1.2.2 beta solve the annoying ! ACL issue that the upgrades after v1.1.1 caused?
- Copy Link
- Report Inappropriate Content
I don't know if I am the only one but 1.2.3 broke the dhcp reservation for my tapo C100 camera.
Randomly I have to force a reconnect for them to regain their reserved ip.
- Copy Link
- Report Inappropriate Content
@Fae I'm still having issues with DHCP and reserved addresses specifically on wireless. Any time my router gets rebooted or if I make any wireless changes then all of my devices get booted off my WLAN and continue to try to connect but do not get an IP Address. The only fix I have found for this is to go into my DHCP Reservation list and disable any device on the list and then re-enable it. Once I do that all of my clients start getting IP Address again.
Here is a list of my gear and the firmware version for each:
ER7206 V1 1.2.3
TL-SG2428P V1 1.1.6
TL-SG3428 V2 2.0.9
TL-SG2008P V1 1.0.5
TL-SG2008 V3 3.0.4
TL-SG3210 V3 3.0.4
TL-SG2218 V1 1.1.4
EAP225-Outdoor V1 5.0.9
EAP660 HD V1 1.1.1 (4 of these)
EAP615-Wall V1 1.1.0
OC200 1.20.1
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@kogan Yes, All of the switches and router are interconnected with a SFP cable or a Transceiver. The router is at the demarc and connected to the POE Switch via Cat6 with a SFP transceiver on the switch side. Do you think that could be causing the problem with DHCP and Address Reservations?
- Copy Link
- Report Inappropriate Content
If you use LAG, dont use LACP -> try to use static LAG
And for SFP Modules / SFP / DAC , try to only use normal Ports, without RSTP, only loopback.
just for the test.
thanks (some of my customers problems were solved these ways)
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Fae, the latest firmware for the ER605 V2 dated release on November 2022 does not seems to fix the stealth mode issues. Can you please informed to your engineering team to fix the firewall stealth mode issues. There is a missing option under the firewall settings.
Someone reported that there is a performance drop issues with the ER605 V2 firmware issues.
There seems to be an open ports when i do a Nmap Test. So i do not know whether this is acceptable.
$ sudo nmap -Pn -sS -p 1-65535 192.168.1.1
Starting Nmap 7.93 at 2023-01-09 06:14 UTC
Nmap scan report for 192.168.1.1
Host is up (0.0032s latency).
Not shown: 65528 closed tcp ports (reset)
PORT STATE SERVICE
53/tcp open domain
80/tcp open http
443/tcp open https
1723/tcp open pptp
4433/tcp open vop
8080/tcp open http-proxy
20002/tcp open commtact-http
MAC Address: 14:EB:B6:E6:26:23 (TP-Link Limited)
Nmap done: 1 IP address (1 host up) scanned in 8.64 seconds
- Copy Link
- Report Inappropriate Content
@mrusli is 192.168.1.1 a WAN or a LAN interface?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 4
Views: 22032
Replies: 63
Voters 2
