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.