WANFailover WAN Failover v2.2.0 Release

[Kingp1n]

Hoping someone can help. Failover occurs but...
1. When I test (pull the Primary cable) ASUS's Dual WAN shows the connection fails over but when I reconnect the Primary cable it never fails back. It just shows the Primary as a hot-spare?
2. After failover, traffic is not routed to my LTE device.

device config...
<< ASUS GT-AX6000 >>
Primary WAN (WAN): Cable Modem
Secondary WAN (LAN-1) *to RUTX11 LAN-1 for failover
- Dual WAN enabled (Disabled: Allow Failback, DNS Query, Ping)
- Ranger scripts, default settings

<< RUTX11 - LTE modem >>
WAN port (WAN) : Static IP 192.168.2.2 * to network for management UI
LAN port (LAN-1) : Static IP 192.168.3.2 *to ASUS LAN-1 for failover

I would recommend reporting any issues thru GitHub:
Ranger802004/asusmerlin https://share.google/mGwZlu473PsMcl7ov

 

[Livin]

I would recommend reporting any issues thru GitHub:
Ranger802004/asusmerlin https://share.google/mGwZlu473PsMcl7ov

I saw little to no activity on Github but just created Issue on Git... https://github.com/Ranger802004/asusmerlin/issues/125

 

[Ranger802004]

***v2.2.1-beta1 has been released to the Beta update channel***
Release Notes:
v2.2.1-beta1 - 03/20/2026
Deprecated:
- Deprecated firmware version check for compatibility with WAN Failover.

Enhancements:
- Interface status will display as Unplugged accordingly on status console.
- Updated From Address email field to display WAN Failover instead of the to address.

Fixes:
- Fixed issue with status console displaying Status as Unresponsive instead of Failover Disabled for an unplugged interface.

 

[Ranger802004]

I saw little to no activity on Github but just created Issue on Git... https://github.com/Ranger802004/asusmerlin/issues/125

I have been away for personal issues including having a new baby and a family member who spent months in a hospital out of town since October 2025. I have gone through all of the cases open on the repo and responded and made immediate bug fixes to the ones I could address. As I responded to yours as well and suspect your router has a invalid entry in NVRAM where the script pulls parameters from for Dual WAN. Per my recommendation I recommend force disabling / re-enabling Dual WAN on your router to get the proper interface set in NVRAM for your secondary interface.