ER707-M2 Failback to Primary WAN Does Not Occur After WAN Recovery (Firmware 1.4.5)
ER707-M2 Failback to Primary WAN Does Not Occur After WAN Recovery
Product: TP-Link ER707-M2
Hardware Version: v1.30
Firmware Version: 1.4.5 Build 20260722 Rel.15863
Network Configuration
WAN1 (Primary)
- Comcast Xfinity XB8
- Dynamic IP
- Receives Public IP
- Example IP: 73.105.XX.YYY
WAN2 (Backup)
- T-Mobile G5AR
- Dynamic IP via DHCP
- Example IP: 192.168.12.220
- Gateway: 192.168.12.1
LAN
- ER707 LAN IP: 192.168.50.1/24
Configuration
Load Balancing: Disabled
Application Optimized Routing: Disabled
Policy Routing: No Policy Routes Configured
Static Routes: No Static Routes Configured
Online Detection:
WAN1 = Auto
WAN2 = Auto
Both WAN interfaces report: Online
Link Backup Rule:
Primary WAN: 2.5G WAN1
Backup WAN: WAN/LAN3
Mode: Enable backup link when any primary WAN fails
Status: Enabled
Observed Behavior
Initial Boot Test
With both WAN interfaces connected:
Result:
Traffic correctly exits WAN1 (Comcast).
Verified by:
- WhatIsMyIPAddress.com reports Comcast public IP address.
- Traceroute shows Comcast as the upstream provider.
Failover Test
Action:
Disconnect WAN1 (Comcast).
Result:
Traffic correctly fails over to WAN2 (T-Mobile).
Verified by:
- WhatIsMyIPAddress.com reports a T-Mobile IP address.
- Traceroute output:
Hop 1: 192.168.50.1 (ER707)
Hop 2: 192.168.12.1 (T-Mobile G5AR)
This confirms failover is functioning properly.
Failback Test
Action:
Reconnect WAN1 (Comcast).
Observations:
- WAN1 obtains a valid Comcast public IP.
- WAN1 reports Online in Online Detection.
- WAN2 remains Online.
- Routing table contains both default routes:
0.0.0.0/0 -> Comcast Gateway via WAN1
0.0.0.0/0 -> T-Mobile Gateway via WAN2
Result:
Traffic remains on WAN2 indefinitely.
Verification:
- Waited several minutes after WAN1 recovered.
- Rebooted ER707 after upgrading firmware.
- Traceroute continues to show:
Hop 1: 192.168.50.1 (ER707)
Hop 2: 192.168.12.1 (T-Mobile G5AR)
- WhatIsMyIPAddress.com continues to report a T-Mobile IP address.
Additional Testing
Test A
1. System booted with both WANs connected.
2. WAN1 (Comcast) was active.
3. Disconnected WAN1.
4. Traffic failed over to WAN2.
5. Reconnected WAN1.
Result:
Traffic remained on WAN2.
Test B
1. While WAN2 was active, disconnected WAN2.
2. Traffic failed over to WAN1.
3. Reconnected WAN2.
Result:
Traffic remained on WAN1.
This appears to indicate that whichever WAN is active after a failover event remains active until it fails again.
Expected Behavior
Configured Design:
WAN1 = Primary
WAN2 = Backup
Expected behavior:
1. Use WAN1 when both WANs are healthy.
2. Fail over to WAN2 if WAN1 fails.
3. Automatically return to WAN1 when WAN1 is restored and reports Online.
Actual behavior:
1. Use WAN1 at boot.
2. Fail over to WAN2 when WAN1 fails.
3. WAN1 returns Online.
4. Traffic remains on WAN2 indefinitely.
Question
Is this behavior expected?
Specifically:
Does Link Backup intentionally operate as a non-preemptive failover mechanism where traffic remains on the currently active WAN until that WAN fails?
Or should the ER707-M2 automatically fail back to the configured Primary WAN after recovery?
If automatic failback is supported, is there an additional configuration setting required to enable Primary WAN preemption/recovery?
