Solution ER605 ER7206 v1 - DHCP Server May Fail With 1.2.0 and 1.2.1 Firmware [Updated on Nov 11th 2022]
Updated on Nov 11th 2022:
Add the official firmware ER7206_v1_1.2.3.
Add some notes for the firmware.
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.
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!
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.
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:
TP-Link will release the official firmware soon to resolve the issue.
If you are looking for a quick solution, you may install the Beta firmware below to fix the issue temporarily.
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)
Updated on Nov 2nd 2022:
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.
Updated on Nov 11st 2022:
ER7206_v1_1.2.3 Build 20221104 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.
Note:
(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.
Thank you for your attention!
Feedback:
Still have DHCP issues with the Beta firmware above?
It might be a different case, please don't hesitate to comment below for further assistance.
If this was helpful, welcome to give us Kudos by clicking the upward triangle below.
If there is anything unclear in this solution post, please feel free to comment below.
Previous Solution Post:
ER605 ER7206 - “Use Fixed IP Address” (DHCP Reservation) Doesn't Take Effect
Behold, the absolute insanity of the Sep 18th beta!
Exact same config, network structure and router not doing much other than serving my laptop
Sep 2nd build CPU graph......
Sep 18th build CPU graph......
I have sent off my router config to support, thanks for raising the ticket. thought it would be good to visualise the issue here as well
@GRL I have read already two posts from you mentioning cpu spike and not working vpn, tp-link support warned me about cpu spikes and performance issues which occure with this beta, but in no way I can confirm any of it. My cpu is used less than it was before, same goes for memory and there are no spikes despite using it fully including vpn:
here as example with v1.2.1 on one site where it is used a lot:
and here another er605v1 on a network with just one client which is 90% fully unused, also v1.2.1:
My question would be, how to reproduce your issue?
Do you use any cpu heavy tasks like encrypted vpn (ipsec/openvpn)? er605v1 is not really a good device for vpn encryption as well as it heats up and as addition it uses a lot cpu so that other router functions are affected, that all was known prior to even 1.2.1, that is why I fail for now to understand what exactly causes cpu spikes. Can you please SSH to your router run top (that is something like task manager on windows). Watch processes and check which process spikes with your config.
