An ER605 that is configured with two WANs with a primary link and link backup and that has an active VPN client fails to recover properly from a primary WAN failure.

Specifically, if the following events occur:

1) Wireguard VPN client is enabled.
2) Primary WAN fails
3) Primary WAN recovers

The ER605 will show on the Transmission -> Load Balancing -> Backup Detection page that the primary interface is online and the backup interface is offline. However, all traffic except online detection pings will continue to be routed through the backup interface.

After this occurs, if you physically disconnect the backup interface and wait for traffic to resume being routed through the primary interface, then reconnect the backup interface, the ER605 functions correctly again, routing traffic through the primary interface.

I reported this behavior to the Omada Case Portal. They investigated it and reported:

After further analysis, we confirmed that this is a known limitation. Our development team is already aware of this behavior, and an improvement is planned for a future firmware update. However, there is currently no estimated release date for when this improvement will be available.

This is not a "limitation". It is a bug that renders the ER605 unusable.

An ER605 that is configured with two WANs with a primary link and link backup and that has an active VPN client fails to recover properly from a primary WAN failure.

Specifically, if the following events occur:

1) Wireguard VPN client is enabled.
2) Primary WAN fails
3) Primary WAN recovers

The ER605 will show on the Transmission -> Load Balancing -> Backup Detection page that the primary interface is online and the backup interface is offline. However, all traffic except online detection pings will continue to be routed through the backup interface.

After this occurs, if you physically disconnect the backup interface and wait for traffic to resume being routed through the primary interface, then reconnect the backup interface, the ER605 functions correctly again, routing traffic through the primary interface.

I reported this behavior to the Omada Case Portal. They investigated it and reported:

After further analysis, we confirmed that this is a known limitation. Our development team is already aware of this behavior, and an improvement is planned for a future firmware update. However, there is currently no estimated release date for when this improvement will be available.

This is not a "limitation". It is a bug that renders the ER605 unusable.