Business Community > Gateways > ER605 v2 – Dual WAN causes “Adopting → Adopt Failed” loop in Omada Cloud (FW 2.3.3)
< Gateways

ER605 v2 – Dual WAN causes “Adopting → Adopt Failed” loop in Omada Cloud (FW 2.3.3)

ER605 v2 – Dual WAN causes “Adopting → Adopt Failed” loop in Omada Cloud (FW 2.3.3)

ER605 v2 – Dual WAN causes “Adopting → Adopt Failed” loop in Omada Cloud (FW 2.3.3)
ER605 v2 – Dual WAN causes “Adopting → Adopt Failed” loop in Omada Cloud (FW 2.3.3)
2 weeks ago - last edited a week ago
Tags: #Controller
Model: ER605 (TL-R605)   Omada Cloud-Based Controller  
Hardware Version: V2
Firmware Version: 2.3.3

Hi everyone,

 

I’m reporting a reproducible issue with the ER605 v2 when using Dual WAN under Omada Cloud Controller management.

 

Environment

 

  • Device: ER605 v2

  • Firmware: 2.3.3 (Build 20251029 / Rel.18504)

  • Controller: Omada Cloud

  • WAN setup:

    • WAN1: Fiber (VIVO)

    • WAN2: Fiber (VIVO)

    • Two separate modems, independent links, same ISP

  • Topology: ER605 connected directly to both modems

  • Modes tested: Load Balancing and Link Backup (failover)

 

Issue Description

 

When Dual WAN is enabled under Omada Cloud management, the ER605 enters an adoption loop:

  1. Device adopts normally with only one WAN connected.

  2. After connecting WAN2 and applying Dual WAN settings:

    • Status changes to Adopting

    • Then to Adopt Failed

  3. The device keeps looping between Adopting → Adopt Failed.

  4. If WAN2 is physically disconnected, the device immediately returns to Connected.

This happens every time and is fully reproducible.

 

What I already tested

 

  • Factory reset

  • New site / new organization in Omada Cloud

  • Manual adoption (Auto-Find never discovers the device)

  • Load Balancing and Link Backup

  • Hardware Offload on/off

  • Full configuration validation in Standalone mode

 

In Standalone mode, Dual WAN works perfectly with no instability. The issue only happens when the device is managed by Omada Cloud.

 

This looks like a firmware / controller compatibility issue involving ER605 v2 + Dual WAN + Omada Cloud Controller (possibly more evident when both WANs are from the same ISP).

 

Questions to TP-Link / community

 

  • Is this a known issue?

  • Is there any beta firmware or hotfix available?

  • Any recommended workaround besides using Standalone mode?

  • Is a controller-side fix planned?

 

For now, I’m keeping the ER605 in Standalone mode for stability and full usability.

 

Thanks in advance for any feedback or confirmation.

  0      
 
  0      
 
#1
Options
2 Accepted Solutions
Re:ER605 v2 – Dual WAN causes “Adopting → Adopt Failed” loop in Omada Cloud (FW 2.3.3)-Solution
a week ago - last edited a week ago

 Hi @gustavoIAT 

Thank you so much for taking the time to post the issue on the TP-Link 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 TKID260222749 please check your email box and ensure the support email is well received. Thanks!

 

Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.

 

Many thanks for your great cooperation and patience!
 

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  1  
  1  
#2
Options
Re:ER605 v2 – Dual WAN causes “Adopting → Adopt Failed” loop in Omada Cloud (FW 2.3.3)-Solution
a week ago - last edited a week ago

 Hi @Hank21 ,

 

Thank you very much for your quick response and for escalating the case to the support engineers — I really appreciate the assistance.

 

I’ve received the 2.3.3 beta firmware via email and have already installed it on my ER605 v2.

So far, the results look very promising: the device was successfully adopted in Omada Cloud with Dual WAN enabled, and the previous “Adopting → Adopt Failed” loop has not reoccurred.

 

I will continue testing stability over the next 2–3 days (including reboots, WAN failover scenarios, and load testing) to ensure everything remains stable.

 

I’ll update this thread with a final confirmation and detailed feedback once testing is complete, so it may help others facing the same issue.

 

Thanks again for the great support and fast escalation.

 

Best regards,


Gus

Recommended Solution
  0  
  0  
#3
Options
3 Reply
Re:ER605 v2 – Dual WAN causes “Adopting → Adopt Failed” loop in Omada Cloud (FW 2.3.3)-Solution
a week ago - last edited a week ago

 Hi @gustavoIAT 

Thank you so much for taking the time to post the issue on the TP-Link 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 TKID260222749 please check your email box and ensure the support email is well received. Thanks!

 

Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.

 

Many thanks for your great cooperation and patience!
 

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  1  
  1  
#2
Options
Re:ER605 v2 – Dual WAN causes “Adopting → Adopt Failed” loop in Omada Cloud (FW 2.3.3)-Solution
a week ago - last edited a week ago

 Hi @Hank21 ,

 

Thank you very much for your quick response and for escalating the case to the support engineers — I really appreciate the assistance.

 

I’ve received the 2.3.3 beta firmware via email and have already installed it on my ER605 v2.

So far, the results look very promising: the device was successfully adopted in Omada Cloud with Dual WAN enabled, and the previous “Adopting → Adopt Failed” loop has not reoccurred.

 

I will continue testing stability over the next 2–3 days (including reboots, WAN failover scenarios, and load testing) to ensure everything remains stable.

 

I’ll update this thread with a final confirmation and detailed feedback once testing is complete, so it may help others facing the same issue.

 

Thanks again for the great support and fast escalation.

 

Best regards,


Gus

Recommended Solution
  0  
  0  
#3
Options
Re:ER605 v2 – Dual WAN causes “Adopting → Adopt Failed” loop in Omada Cloud (FW 2.3.3)
a week ago

Quick update:

 

I’ve now completed extended stability tests with:

 

  • Dual WAN enabled (both WANs active simultaneously – Load Balancing mode, weights 7:5)

  • Failover scenarios (disconnecting WAN1 and WAN2 individually)

  • Multiple reboots

  • Sustained load testing (simultaneous speed tests on two devices, continuous 2 simultaneous 2K streaming, and large file upload)

 

Results so far

 

✅ The ER605 v2 is now successfully adopted and remains stable under Omada Cloud management.
✅ No more “Adopting → Adopt Failed” loop.
✅ Device stays Connected even during WAN failover tests.
✅ Throughput and load balancing behave as expected.
✅ No unexpected disconnections during stress testing.
✅ The switch (TG108E) that previously appeared intermittently now shows consistently under current clients.

 

During heavy load, I observed only a few isolated ping timeouts, but the device never disconnected from the controller and immediately continued responding — which appears normal under saturation conditions.

 

At this point, the tested firmware appears to resolve the issue when using Dual WAN under Omada Cloud, even with two WANs from the same ISP.

 

I will continue monitoring stability over the next couple of days, but it´s almost certain that the tested FW solved the issue and is also an improvement over the latest oficial FW we can find in TP-link´s website.

 

Many thanks to TP-Link support and the engineering team for the quick escalation and beta fix.

 

I´ll post a final confirmation after longer-term stability validation (if this thread is still unlocked by then), but i´m pretty confident that it can be already marked as solved.

 

Best regards,

 

Gus

  0  
  0  
#4
Options

Information

Helpful: 0

Views: 244

Replies: 3

Tags

Controller
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.