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 (Firmware 1.4.5)

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 (Firmware 1.4.5)
a week ago - last edited a week ago
Model: ER707-M2  
Hardware Version: V3
Firmware Version: 1.4.5 Build 20260722 Rel.15863

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?

  0      
0
#1
Options
1 Accepted Solution
Re:ER707-M2 Failback to Primary WAN Does Not Occur After WAN Recovery (Firmware 1.4.5)-Solution
a week ago - last edited a week ago

Automatic failback appears to function correctly only when Load Balancing is enabled. With Load Balancing disabled, failover occurs but failback does not occur.

 

With Load Balancing enabled and WAN weights set to 100:1 (Comcast:T-Mobile), failover and failback both work correctly.

Recommended Solution
  0  
0
#5
Options
18 Reply
Re:ER707-M2 Failback to Primary WAN Does Not Occur After WAN Recovery (Firmware 1.4.5)
a week ago

Additional Observation:

 

After reboot, WAN1 (Comcast) becomes active correctly.

 

Several hours later, traffic is found to have migrated back to WAN2 (T-Mobile) without any known Comcast outage.

 

WAN1 still reports Online and maintains a valid public IP address.

 

This suggests either:

- a false failover event is occurring, or

- route selection is changing while both WANs remain healthy.

  0  
0
#2
Options
Re:ER707-M2 Failback to Primary WAN Does Not Occur After WAN Recovery (Firmware 1.4.5)
a week ago

Additional Evidence from System Log

 

Example entries:

 

2026-08-05 07:18:09

The online detection result of [WAN1] was offline.

 

2026-08-05 07:18:32

The online detection result of [WAN1] was online.

 

WAN1 physical link remained connected and later recovered.

 

Observed behavior:

- Router fails over to WAN3 (T-Mobile).

- WAN1 subsequently returns online.

- Router does not automatically revert traffic to WAN1.

  0  
0
#3
Options
Re:ER707-M2 Failback to Primary WAN Does Not Occur After WAN Recovery (Firmware 1.4.5)
a week ago

TP-Link support states that Online Detection cannot take effect if Load Balancing is disabled.

 

In my testing:

- Link Backup is enabled

- Load Balancing is disabled

- WAN1 offline/online events are recorded in the log

- Failover works

- Failback does not occur

 

Is automatic failback to the configured Primary WAN expected to require Load Balancing to be enabled?

  0  
0
#4
Options
Re:ER707-M2 Failback to Primary WAN Does Not Occur After WAN Recovery (Firmware 1.4.5)-Solution
a week ago - last edited a week ago

Automatic failback appears to function correctly only when Load Balancing is enabled. With Load Balancing disabled, failover occurs but failback does not occur.

 

With Load Balancing enabled and WAN weights set to 100:1 (Comcast:T-Mobile), failover and failback both work correctly.

Recommended Solution
  0  
0
#5
Options
Re:ER707-M2 Failback to Primary WAN Does Not Occur After WAN Recovery (Firmware 1.4.5)
Friday

  @JEJ3 
hi,

Thank you for posting here.

 

Yes, if you would like to enable Link Backup on your Getaway, you will need to configure Load Balance and WAN Online Detection first. You may refer to the following guide for configuration:How to Configure Link Backup on Omada Gateway in Standalone Mode | Omada Network Support

  0  
0
#6
Options
Re:ER707-M2 Failback to Primary WAN Does Not Occur After WAN Recovery (Firmware 1.4.5)
Friday

  @JEJ3 Hi,

 

I have a very similar setup ... except that it's a T-Mobile G4AR. Some odd behaviour ... thoughts?

1) Config

- WAN2 is meant as backup, connected to LAN2 on the G4AR, because

- LAN3 is connected to the G4AR LAN1, it's supposed to be the online detection link (i.e. so Auto Backup can be enabled on the G4AR).

2) Observations / Issues

- I see in the thread setting 100:1 for the Load Balancing ... but also noting about turning it off? I can't see where to turn it off. FYI, I'm running v1.7.7 on my OC220 V1 controller.

- Do I need to disable Application Optimized Routing? Or a don't care?

- With the G4AR LAN1 connection to the LAN side of the firewall ... I have all sorts of issues with LAN traffic, and slow internet response (from other machines). If I disconnect this link, it improves. Huh? It should be set up this way, right?

- WAN2 never shoes as Online ... even when I manually enable it on the G4AR. Known issue?

- If the G4AR is disabled (not backup), ping through WAN2 still passes? Huh? It shouldn't ;).

 

Thanks!

  0  
0
#7
Options
Re:ER707-M2 Failback to Primary WAN Does Not Occur After WAN Recovery (Firmware 1.4.5)
Tuesday

  @JEJ3 A bit more on this - and not sure I fully understand how this happens :(. When I connect the G4AR LAN1 port to my LAN (as I'm supposed to do, for internet connectivity monitoring) ... my LAN DNS server changes? Huh? How can this happen? And how to avoid that of course?

 

Thanks!!

  0  
0
#8
Options
Re:ER707-M2 Failback to Primary WAN Does Not Occur After WAN Recovery (Firmware 1.4.5)
Tuesday

Sorry, @arrmo.   I can't answer your questions but I would think you need to not have your G4AR ports both connected to your router.    Connect your G4AR LAN1 port to a WAN interface on your TP-LINK router.   Do not connect anything to the LAN2 port from the G4AR.   Server up your LAN clients from the TP-Link Router.

 

Not familiar with your device but I needed to:

1. enable load balancing between my two WAN ports. I weighted it 100 to Comcast and 1 to T-Mobile.

2. create a Link Backup rule from the primary WAN port (comcast in my case) to the seconday WAN port (T-Mobile G5AR)

3. configure online detection for WAN Port 1 (comcast to ping 8.8.8.8 and DNS 1.1.1.1).  I left WAN port 2 (T-Mobile) as automatic

 

 

Good Luck

  0  
0
#9
Options
Re:ER707-M2 Failback to Primary WAN Does Not Occur After WAN Recovery (Firmware 1.4.5)
Tuesday

  @JEJ3 Thanks! But a bit confused - here's why :)

1) LAN1 is supposed to be for internet detection, right? So needing to be on the LAN side of the firewall? I am wanting to use Automatic Backup (from T-Mobile)

2) The other settings make sense, fully agree with you

 

Thanks again.

  0  
0
#10
Options
Re:ER707-M2 Failback to Primary WAN Does Not Occur After WAN Recovery (Firmware 1.4.5)
Tuesday

  @arrmo 

 

1) LAN1 is supposed to be for internet detection, right? So needing to be on the LAN side of the firewall? I am wanting to use Automatic Backup (from T-Mobile)

 

This is not a correct statement.   LAN1 and LAN2 are two ethernet connections which will each be assigned an IP address.    You are using your TP-LINK as the router and it should be assigning IP addresses to ALL computers on your network (just not your T-MOBILE or other Internet connection).    

 

Step 1 - Assuming your TP-LINK device has support for 2 or more WAN ports, plug your primary (in my case COMCAST) into WAN1 and LAN1 from your G4AR into the WAN2 port on your TP-LINK device.

 

Step 2 - Plug your other network devices (like a WIFI Access Point) into you TP-LINK routers LAN ports OR plug a SWITCH into the LAN port and then plug your devices into the SWITCH

 

 

Truthfully, you need to fire up a chat with ChatGPT or Copilot and tell it what you have and it will tell you more or less how to configure everything.

 

Good Luck

 

 

  0  
0
#11
Options

Information

Helpful: 0

Views: 350

Replies: 18