Solution Solution to DHCP Issues of Routers (ER605 | ER7206 | ER8411 | ER7212PC) [Closed on May 22nd 2023]
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Update as of May 22nd 2023:
The following official firmware has fixed the DHCP issue mentioned in this thread.
ER605 V1_1.3.0 Official Firmware (Released on May 17th, 2023)
Note: the firmware is applied to ER605 V1 and V1.60.
ER605 V2_2.1.2 Official Firmware (Released on Feb 14th, 2023)
Note: the firmware is applied to ER605 V2 and V2.60.
ER7206 V1_1.3.0 Official Firmware (Released on Mar 28th, 2023)
Note: the firmware is applied to ER7206 V1 and V1.60.
ER8411 V1_1.0.3 Official Firmware (Released on Mar 17th, 2023)
Note: the firmware is applied to ER8411 V1 and V1.60.
ER7212PC V1_1.0.3 Official Firmware (Released on Mar 21st, 2023)
As the official firmware has been released to fix the issue, this thread will be locked to stop updating.
Any further issues or concerns, please feel free to Start a New Thread from HERE.
To get better assistance, you may check Tips For Efficiently Reporting an Issue In The Community.
Update as of Mar 8th 2023:
1. Update the Beta firmware of ER7212PC v1, which fixed all DHCP issues and added some new features.
ER7212PC(UN)_V1_1.0.3 Build 20230228 (Beta)
Beta Release Note:
1) Fixed all DHCP issues based on the official firmware 1.0.2 Build 20230202.
2) Add support for modifying port PVID and optimized stability of the device.
3) Cloud Access is available for the above ER7212PC 1.0.3 Beta.
4) You may need to manually upgrade the upcoming official 1.0.3 firmware once you install the above 1.0.3 Beta.
2. Add note that ER605 v1 and ER7206 v1 have a new Beta firmware for trial, which fixed all DHCP issues and added some new features.
ER7206 V1_1.2.3 Beta Firmware For Trial (Released on Feb 28th, 2023)
ER605 V1_1.2.3 Beta Firmware For Trial (Released on Feb 28th, 2023)
Kind Note:
If you don't need the new features added in the above 1.2.3 Build 20230224 (Beta), it's okay to stay with the earlier Build 20230208 (Beta).
Notes:
(1) Please be sure you have read the Beta Test Agreement before proceeding!
(2) The above Beta has added the fix for the DHCP Reservation issue mentioned HERE.
Update as of Feb 21st 2023:
Add beta firmware for ER8411 v1 and ER7212PC v1 to fix all DHCP issues.
ER8411(UN)_V1_1.0.2 Build 20230214 (Beta)
Beta Release Note:
Fixed all DHCP issues based on the official firmware 1.0.2 Build 20230115.
Notes:
(1) Please be sure you have read the Beta Test Agreement before proceeding!
(2) The above Beta has added the fix for the DHCP Reservation issue mentioned HERE.
Edit on Feb 23rd 2023: add note that Cloud Access is unavailable for the above ER7212PC Beta.
New ER7212PC Beta will be provided soon to add Cloud Access availability. Please wait patiently.
Update as of Feb 14th 2023:
Here are the new solutions to resolve the new DHCP issues we recently received in the community, including
1. DHCP Server failed to assign an IP address when a large number of clients make DHCP requests at the same time.
2. DHCP server failed to assign the correct reserved IP address to some clients.
Beta Firmware Download:
ER605(UN)_v1_1.2.2_Build 20230208 (Beta)
Beta Release Note:
Fixed all DHCP issues based on the official firmware 1.2.1 Build 20220512.
ER7206(UN)_v1_1.2.3_Build 20230208 (Beta)
Beta Release Note:
Fixed all DHCP issues based on the official firmware 1.2.3 Build 20221104.
ER8411(UN)_V1_1.0.2 Build 20230214 (Beta)
Beta Release Note:
Fixed all DHCP issues based on the official firmware 1.0.2 Build 20230115.
Notes:
(1) Please be sure you have read the Beta Test Agreement before proceeding!
(2) The above Beta has added the fix for the DHCP Reservation issue mentioned HERE.
For ER605 V2, please check for the official firmware below to fix the DHCP issue.
ER605 V2_2.1.2 Official Firmware (Released on Feb 14th, 2023)
Note: the firmware is applied to ER605 V2 and V2.60.
As always, thank you for working with our support engineers to address the issue with great cooperation.
And thank you all for your great patience when we're trying to figure out the issue and fix it!
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.
Here are the updates of the Beta firmware to fix all the DHCP issues that have been located, including
- 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 that ER605 v2 ONLY have the last DHCP issue mentioned above, which is a mis-report by the router.)
Beta Firmware Download:
ER605(UN)_v1_1.2.2_Build 20230118 (Beta)
Beta Release Note:
Fixed the DHCP issues based on the official firmware 1.2.1 Build 20220512.
ER7206(UN)_v1_1.2.3_Build 20230118 (Beta)
Beta Release Note:
Fixed the DHCP issues based on the official firmware 1.2.3 Build 20221104.
Notes:
(1) Please be sure you have read the Beta Test Agreement before proceeding!
(2) The above Beta has added the fix for the DHCP Reservation issue mentioned HERE.
For ER605 V2 and ER8411 V1, please check for the official firmware below to fix the DHCP issue.
ER605 V2_2.1.1 Official Firmware (Released on Jan 30th, 2023)
Note: the firmware is applied to ER605 V2 and V2.60.
ER8411 V1_1.0.2 Official Firmware (Released on Jan 30th, 2023)
Note: the firmware is applied to ER8411 V1 and V1.60
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 comment below or Start a New Thread from HERE.
Updated on Nov 11th 2022:
The official firmware ER7206_v1_1.2.3 has been released to fix the DHCP issue.
**The above ER7206 1.2.3 firmware is available in the cloud, fully adapted to Omada Controller v5.6.
Updated on Nov 2nd 2022:
Update the Beta 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(UN)_v1_1.2.2_Build 20221015 (Beta)
ER7206(UN)_v1_1.2.2_Build 20221025 (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.
Note:
ER605 v2 ONLY have the last DHCP issue mentioned above, which is a mis-report by the router.
Updated on Sep 21st 2022:
Remove the 0918 Beta firmware as some users reported it causes CPU spikes issue.
Updated on Sep 19th 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.
ER605(UN)_v1_1.2.2_Build 20220902 (Beta)
ER7206(UN)_v1_1.2.2_Build 20220902 (Beta)
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)
This Article Applies to:
ER605_v1/ v1.6
with FW 1.2.0 Build 20220114 or FW 1.2.1 Build 20220512
ER7206_v1/ v1.6
with FW 1.2.0 Build 20220117 or FW 1.2.1 Build 20220512
Issue Description/Phenomenon:
Recently we received feedback that the DHCP Server failed with 1.2.0 and 1.2.1 firmware, the issue may manifest as follows:
- DHCP Server won't provide dynamic IP addresses to end clients in some cases.
Related Post: DHCP Server Fails Every Few Hours
(1) simply clicking Save on the Edit Network page will bring the DHCP server to work for a few hours.
(2) reboot doesn't help, the issue doesn't exist with the router firmware 1.1.1.
- Some clients are assigned the same IP address, causing they cannot access the internet.
Related Post: Issues with DHCP, clients get same iP addresses
(1) rebooting the router will solve the issue for a while.
(2) the issue doesn't exist with the router firmware 1.1.1.
Note:
ER605 v2 doesn't have the two DHCP issue described above.
Thank you all @jdpk, @Karel-24, @PascalSBR for reporting the issue with detailed information, and your great cooperation with our support engineers to look into the issue is much appreciated!
After further investigation and tests, the TP-Link team has addressed the problem finally.
Available Solutions:
Update as of Apr 17th 2023:
The following official firmware has fixed the DHCP issue mentioned in this thread.
ER605 V2_2.1.2 Official Firmware (Released on Feb 14th, 2023)
Note: the firmware is applied to ER605 V2 and V2.60.
ER7206 V1_1.3.0 Official Firmware (Released on Mar 28th, 2023)
Note: the firmware is applied to ER7206 V1 and V1.60.
ER8411 V1_1.0.3 Official Firmware (Released on Mar 17th, 2023)
Note: the firmware is applied to ER8411 V1 and V1.60.
ER7212PC V1_1.0.3 Official Firmware (Released on Mar 21st, 2023)
For ER605 V1, you may install the Beta firmware below to fix the issue temporarily.
Beta Firmware Download:
ER605 V1_1.2.3_Build 20230413 Beta Firmware For Trial (Released on Apr 14th, 2023)
Notes:
(1) Please be sure you have read the Beta Test Agreement before proceeding!
(2) The above Beta has added the fix for the DHCP Reservation issue mentioned HERE.
Update as of May 22nd 2023:
The following official firmware has fixed the DHCP issue mentioned in this thread.
ER605 V1_1.3.0 Official Firmware (Released on May 17th, 2023)
Note: the firmware is applied to ER605 V1 and V1.60.
As the official firmware has been released to fix the issue, this thread will be locked to stop updating.
Any further issues or concerns, please feel free to Start a New Thread from HERE.
To get better assistance, you may check Tips For Efficiently Reporting an Issue In The Community.
Thank you all for your great patience when we're trying to figure out the issue and fix it!
Previous Solution Post:
ER605 ER7206 - “Use Fixed IP Address” (DHCP Reservation) Doesn't Take Effect
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I have the ER605 v2.0 Firmware 2.1.2 Build 20230210 Rel.62992
It has allocated one fixed IP but does not allocate a second fixed IP nor does it show the IP in the client list however the device is on the network.
- Copy Link
- Report Inappropriate Content
Before the ER7206 failed to be adopted, was there anything else changed?
What's the current state of your ER7206 now? Is there showing any error message or logs when you try to adopt it?
Are the switches and other devices properly adopted and stay connected in the controller? Does your Internet connection drop?
After a week being abroad, the situation has not changed.
- The ER7206 is still in ADOPTING status.
- Luckily the clients can still use the network, so DHCP is working, after I deleted and recreated the affected networks.
- I have changed a lot and I don't remember exactly what anymore, being quite desperate at the time.
- As I changed the Gateway ACL's I am not able to access the network through the VPN anymore, so I am forced to go to the site.
- I can not access the gateway, as the passwords don't work. So I can not reset or change anything on the gateway.
- As the gateway is in adoption mode, changes to access rules are not effective: Omada can not access the gateway ether.
- The 4 switches are CONNECTED and did not change state
- One of the AP's (EAP660 HD(EU) v1.0) stays disconnected
- The internet connection seems to be stable, but no statistics are available because the gateway is not adopted.
- Copy Link
- Report Inappropriate Content
You need to do a Hardware reset, (Press and hold Reset button), then do an upgrade in stand-alone mode, reboot then you should be able to re-configure in Controller mode. See the very early solutions to get more details.Ian Dixon
- Copy Link
- Report Inappropriate Content
Hello @Welshdragon69
Welshdragon69 wrote
I have the ER605 v2.0 Firmware 2.1.2 Build 20230210 Rel.62992
It has allocated one fixed IP but does not allocate a second fixed IP nor does it show the IP in the client list however the device is on the network.
Is your ER605 managed by Omada Controller? How is your DHCP Reservation (or fixed IP address) configured?
Do you mean only one device will get the reserved IP address, while other devices with IP addresses reserved will randomly obtain IP addresses from DHCP and show up in the Clients list as Connected state with non IP address? Are you sure that those devices shown with non IP address have obtained IP addresses?
- Copy Link
- Report Inappropriate Content
Hello @HaroldH
Where is your ER7206 located? Is it located in a different network from the Omada Controller?
Do you mean that you can access the standalone web UI of the ER7206 with its IP Address, but failed to login as the password was indicated as incorrect? Did you use the Device Account you configured on the Controller before to login?
For the disconnected EAP660 HD, you may confirm it's properly powered up with a stable light and hardwired to the network with a standard cable first.
- Copy Link
- Report Inappropriate Content
Fae wrote
Hello @HaroldH
Where is your ER7206 located? Is it located in a different network from the Omada Controller?
Do you mean that you can access the standalone web UI of the ER7206 with its IP Address, but failed to login as the password was indicated as incorrect? Did you use the Device Account you configured on the Controller before to login?
For the disconnected EAP660 HD, you may confirm it's properly powered up with a stable light and hardwired to the network with a standard cable first.
I have drawn the configuration of the network to illustrate the situation.
All devices are in the same network.
The 48 port switch is in the old building, serving the attached access points. Also attached is the OC200 controller.
The ER7206 is connected to the ISP modem and the aggregation backbone switch.
The 24 ports switch is serving the attached access points in the new building.
As I can not adopt the gateway, nor access it through SSH, what are my other options?
BTW, The disconnected EAP could be due to a physical disconnection. I will need to check when I am at the site again, as the port doesn't show a green light. So forget this issue for now.
- Copy Link
- Report Inappropriate Content
Hello @HaroldH
You may try to check if the ER7206 can be discovered by Omada Discover Utility when you're at the site again. And try to adopt it with the Device Account. If it doesn't help, the fast solution might be that hard reset the router and re-adopt it from the omada controller. To figure out the issue, if you are willing to take some time to try further troubleshooting with our engineer when you're at the site, please let me know.
- Copy Link
- Report Inappropriate Content
@Fae , Colleagues,
ER605 V1 with FW 1.2.3. All clients (71 pcs of IP cams and NVR) with reserved DHCP lost connection. In the OC200 Clients tab - they are visible, but without IP addresses.
Spent 2H driving to the site and 3h. Playing with DHCP IP range settings configs, multiple reboots of ER605, OC200, NVR, and PoE switches helped to restore the connection. Just as a prevention step, I changed ER605 V1 to ER605 V2 with FW 2.1.2 and will monitor the situation.
The last FW 1.2.3 definitely has bugs and is not ready for reliable production use. If the issue repeats again, I will go to the site with another brand equipment to change Omada completely. The support team was informed as well.
@Fae How can we help to find the issue and get a solution asap?
Thank you.
- Copy Link
- Report Inappropriate Content
sorry my friend, but v1.2.3 is still beta and use on your own risk. please wait for an official release.
- Copy Link
- Report Inappropriate Content
Hello @Alex_UTS
Sorry to hear that you have some issues with the ER605 1.2.3 Beta firmware. Our support engineer has already discussed the issue with you, and I learned from the engineer that the main concerned issue at present is the frequent client connected log on the controller, which has been reported to the R&D team for further investigation. Please keep in touch with the engineer if you have any additional information to provide. Thank you for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 12
Views: 64148
Replies: 276
Voters 6
