Solution ER605 v2 2.1.0 Build 20221230 May Lead into Adopting - Provisioning Loop [Case Closed]
Solution ER605 v2 2.1.0 Build 20221230 May Lead into Adopting - Provisioning Loop [Case Closed]
Updated on Jan 30th 2023:
The official firmware 2.1.1 has been released to fix the issue mentioned in this post.
If you still have the adopting issue with the official firmware 2.1.1, it might be a different case, please don't hesitate to Start a New Thread from HERE.
To get better assistance from Community, you may check Tips For Efficiently Reporting an Issue In The Community.
Updated on Jan 18th 2023:
Add the Beta firmware ER605_v2_2.1.0.
Add some notes for the firmware.
Here is the Release note.
This Article Applies to:
Omada Controller v5.7 or below
ER605_v2
with FW 2.1.0 Build 20221230
Issue Description/Phenomenon:
Recently we received feedback that after upgrading to ER605 2.1.0 Build 20221230, ER605 will get caught in the loop of adopting- provisioning- configuring under below conditions*, resulting in unstable issue on the network. And this cannot be resolved by rebooting.
*Note that the issue above will only occur when both of the following conditions are satisfied:
-
Omada Controller v5.7 or below manage ER605 v2
-
The WAN connection type is PPPOE
After further investigation and tests, the TP-Link team located the problem is that when the WAN connection type is PPPoE, the newly added MRU function is not adapted to the controller version (v5.7 and below).
Available Solutions:
Case 1:
If you are not satisfied the following conditions, please refer to the Case 2 directly.
- You can still access the Internet.
- When Controller and the ER605 are on the same site, you can perform the following steps when you are on site.
1. Please go to the official website to download the firmware version ER605_V2_2.0.1 Build 20220223.
2. Please change the WAN Connection Type from PPPOE to Dynamic IP on the controller.
Note: After modification, the network will be disconnected for a period of time, you need to ensure that the controller and router on the same site.
3. After the Controller and Gateway Keep in a stable Connected state, you can downgrade the firmware version of ER605 to 2.0.1 on the Controller, and modify the WAN Connection Type back to PPPoE after the downgrading.
Case 2:
If you are no longer able to access the Internet, please follow the steps below:
1. Please hardware reset the ER605.
2. You can use the default IP address 192.168.0.1 to login the management page in Standalone mode, and now you can do the Basic Network settings like WAN Connection Type (PPPOE).
Note: If the LAN Network you used previously is not 192.168.0.0/24, it is recommended that you can modify it to original subnet in this moment.
For example: The original LAN network you used is 192.168.10.0/24, we suggest you modify the LAN to 192.168.10.0/24 either in Standalone mode, it will be very helpful to restore the network.
3. Please go to the official website to download the firmware version ER605_V2_2.0.1 Build 20220223, and downgrade it in standalone mode.
4. Now you can login the controller, and adopt the ER605.
Note: If the controller’s IP address is obtained from ER605 automatically, it is recommended that you unplug and plug the Ethernet cable between controller and Router/Switch to trigger the DHCP, try to adopt the ER605 after the controller obtained the original IP address(like 192.168.10.X) . Then the adoption process will be easier.
Updated on Jan 30th 2023:
The official firmware 2.1.1 has been released to fix the issue mentioned in this post.
If you still have the adopting issue with the official firmware 2.1.1, it might be a different case, please don't hesitate to Start a New Thread from HERE.
To get better assistance from Community, you may check Tips For Efficiently Reporting an Issue In The Community.
Feedback:
If your WAN Connection Type is not PPPOE and still have the same issues with the latest 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.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Marcel.
I'm not in a position to downgrade router firmware at the moment, this is deployed in a business where they will lose money if they don't have internet. Their network is working completely fine at the moment, I just get the pleasure of receiving a notification every ten minutes that the router has disconnected. The issue is not the router firmware, I did not upgrade that. I upgraded the controller firmware. TP-Link needs to issue an updated/patched controller firmware that fixes this issue. Downgrading the router firmware isn't a solution, it's a temporary fix. Since I did not update the firmware of the router, and did not have this issue before updating the controller, I am concluding the issue is the controller firmware.
- Copy Link
- Report Inappropriate Content
Dear @DDI ,
DDI wrote
I am currently in the provisioning loop.
WAN is not set to PPPOE. Client had disconnects every 10-15 minutes today. I updated switch firmware and OC200 firmware, and now the constant provisioning is happening. Client is not on-site to see if the internet is working or not.
Are we supposed to use the same instructions to fix the issue if it is not PPPOE?
Thank you so much for taking the time to report the issue to our community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue.
The ticket ID is TKID230131501, please check your email box and ensure the support email is well received.
Thanks!
- Copy Link
- Report Inappropriate Content
can i use ER605(UN)_v2_2.1.0_Build 20230117 (Beta) but the version of my OC200 is just 5.7.6?
when will the version 5.8.x be available for OC200?
- Copy Link
- Report Inappropriate Content
@Kash01976 I wouldn't hold my breath, Fae completely abandoned the Thread about the 7206 having DHCP issues, no word for weeks now, and no fixes for the broken junk we're still dealing with. At this point it's time for the lawyers to get involved, they broke our systems, and now it's time for them to pay for that :) I refuse to accept that my 7206 should be forced to run outdated firmware because they cannot get the basic features right in the new firmware.
- Copy Link
- Report Inappropriate Content
When will v2_2.1.0 (or other) be patched and released again? It was quickly removed from TP-links's ER605 firmware download page the day the problems stating showing up on the forums.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I don't have PPoE ..... Mines pure Dynamic (FTTP NBN) and it's having a million and one issues now. I was on Omada 5.5.7 on the OC200. I updated to 5.7.6 I think it is. It was fine until that. Now it's dropping in and out, now it just plain says it's disconnected but the net still works. It failed to update some settings when I as adjusting them on the OC200 Omada panel and boom....... went to adopting, provisioning, got stuck on configuring..... then dropped, then stuck on adopting. I did a reset of it....... rejoined ....... took ages, went through and now it's messed up again. Come on TPLink. Seriously. Fix it. Fix Omada ....... PROPER QoS, IP Stats listed in Omada, Simple IP Blocking...... Stability!
I ended up messing around with it for AGES....... trying to figure out what I wanted to do. I tried removing the OC200 completely and reset everything, setting them all up standalone but ran into the issue of not being able to figure out how to get VPN working on the ER605, the EAP610 and EAP615 wouldn't run a 2.4+5G network with the same name and just randomly had issues. Also the ER605 I found on that newer firmware even the BETA in standalone mode pretty much did the exact same thing as Omada......... it saves settings and hangs etc. So I'd say the ER605 firmware is purely the issue.
And this is BUSINESS GRADE stuff. And you release this garbage? Who's doing the testing........ 100% TP Link fail.
In the end I went back to ER605 Firmware 2.01 and left Omada on 5.7.6 and it seems to be working fine.
I run a 172.16.x.x 255.255.0.0 network here..... if TP Link see this. Also a few IP's try breaking into the VPN, is there any VPN protection? So eg. If someone tries 10 times in 24 hours their IP gets blocked AUTOMATICALLY.
Weirdly they only try once an hour.
AGAIN........... What you need to fix in the ER605 it dropping or pausing the connection when changing anything on it such as adding/removing port forwarding or ACL rules. It should not be dropping connections when doing this. It's very annoying having to announce the networks going offline for a second to make a small change.
- Copy Link
- Report Inappropriate Content
Just upgraded and the GRC Shields up is reporting stealth mode. So far so good. There was some weirdness with admin access using the Vivaldi browser saying it was not supported, but all the sudden it seems to be working... wondering?
My ER605 is operating in standalone mode.
- Copy Link
- Report Inappropriate Content
Updated on Jan 30th 2023:
The official firmware 2.1.1 has been released to fix the issue mentioned in this post.
If you still have the adopting issue with the official firmware 2.1.1, it might be a different case, please don't hesitate to Start a New Thread from HERE.
To get better assistance from Community, you may check Tips For Efficiently Reporting an Issue In The Community.
- Copy Link
- Report Inappropriate Content
@Hank21 Seems I just hit the problem with my ER605 v1 being stuck in Adopting. I have no remote availability now to upgrade or downgrade its firmware which is currently v1.2.3. Though I doubt that would even be an option if it's in Adopting mode.
I've never had this happen before until this firmware version. While we have internet connectivity I've lost any remote connectivity to it (which is how I actually found this problem) as none of the port forwarding settings are working. I'll have to physically power it off/on and hopefully re-adopts properly where I can then think about downgrading to one of the previous versions I've used without this issue.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 13
Views: 7619
Replies: 20