Bug Report: WAN Failover Issue on ER707-M2 V1.2/V1.3 with Firmware v1.4.2
Dear Support
I am writing to report a critical bug regarding the WAN failover feature found in the latest firmware version 1.4.2 on the ER707-M2 (V1.2 / V1.3). This issue did not occur in the previous firmware version 1.3.2.
Please find the detailed scenario and test results below:
[Network Configuration & Application] This deployment is for a maritime vessel network with the following strict requirements:
-
WAN 1 (Primary WAN): Connected to Starlink (used when offshore).
-
WAN 2 (Primary WAN): Connected to a SIM Card (Chunghwa Telecom) via MR600 (used when docked).
-
WAN 3 (Backup WAN): Connected to VSAT.
[Issue Description]
-
Failover failure from WAN1 to WAN2: When WAN1 experiences a network disconnection/outage (while the physical cable remains plugged into the ER707-M2), the router fails to failover to WAN2. Traffic remains stuck on the disconnected WAN1. The router will only switch the traffic to WAN2 after the WAN1 cable is physically unplugged.
-
Failback failure from WAN2 to WAN1: Similarly, if the WAN1 cable is plugged back in and WAN2 subsequently goes offline, the router does not automatically failback to WAN1. Again, traffic remains stuck until the WAN2 cable is physically removed.
[Impact] Since firmware v1.4.2 blocks downgrading back to v1.3.2, we are currently unable to revert to the working version. This issue severely impacts daily operations, as the vessel relies on automatic switching between SIM and Starlink networks depending on its proximity to the shore.
This behavior has been verified as a regression bug introduced in v1.4.2. Could you please forward this case to the RD team for an urgent fix?
Thank you for your prompt assistance.
Topology
All Device
