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
@modebm 192.168.1.x is a non routable IP address so your answer would be LAN address.
- Copy Link
- Report Inappropriate Content
Yes it should be but if the WAN interface is inside a DMZ in a double-NAT scenario and the IPs for the networks where heavily tweaks so that .1 is not the routing IP of the network segment, this would be possible. Also in Lab environments with such IP setup where .1 is the WAN IP of the router you could do such thng. I wanted to be sure here before writing this.
If it is the address on a LAN port it is an expected result as from inside you want to reach those ports, thus they should be open.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@mrusli I am sorry but I have to tell you that it is not the WAN side. As @Fleegle61 and I was suspecting you are pinging the routing IP of a LAN interface of the router and this has to be open to a) allow accessing the management interface from inside and b) allow the Omada controller to configure the device. But mind you this is from **inside**! This is desired and intended!
WAN would either be a public IP address or the client IP in a double NAT where you are checking from within the DMZ. The .1 address is usually not reachable from there as it the router is a NAT router.
-----[ modem ]-------WAN-IP--->[ (client interface for the modem) router (routing interface)]<--- 192.168.1.1 --- computer
or
-----[ router 1 ]-------DMZ with its own IP range--->[ (client interface for the modem) router 2 (routing interface)]<--- 192.168.1.1 ---[ computer with an IP of 192.168.1.xxx]
You need to call nmap from either through the modem or within the router 1. and there you can see that the ports are in stealth mode as they should. At least it is on my ER605.
Or in simple tearms: the nmap requests need to come through a WAN cable ;) and there you would not be able to ping 192.168.1.1 as I stated.
- Copy Link
- Report Inappropriate Content
But I have tested the lastest November 2022 firmware for the ER605 V2. That i tested the ports via GRC Sheildup that the latest beta firmware failed the stealth mode test. That need to be fix immediately just like the previous version of beta ER605 V2 in July firmware version. And the performance is slower that 7% what was reported by one user in the forum. https://community.tp-link.com/en/business/forum/topic/522628?replyId=1166546
- Copy Link
- Report Inappropriate Content
I connected in this manner.
Internet ----> [Fiber Optic Modem]----> [ER605 v2 WAN Ethernet port connected directly to Fiber Optic Modem]----> ER05 V2 LAN Ethernet connected to computer ------> Computer
Did a GRC Sheild up firewall test. the latest beta firmware for the ER605 V2 on November 2022 release failed the GRC Sheild up test and not even stealth.
The old ER605 V2 firmware release on July 2022 worked. But not the ER605 V2 November 2022 firmware, it is confirmed that the latest beta firmware is failed with GRC Sheild up firewall test.
@Fae You need to fix this GRC Sheild Up failed problem with the latest firmware ER605 V2.
- Copy Link
- Report Inappropriate Content
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.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 4
Views: 22054
Replies: 63
Voters 2
