Dual WAN Failover ***v2 Release***

[Ranger802004]

Hello,
Ranger802004, your script is a life saver!
Thank you so much.

Thank you, I try and make the best possible tool available for Dual WAN users!

 

[Ranger802004]

***v2.1.1-beta2 Released***
Release Notes:
Enhancements:
- Added 388.5 to supported firmware list.
- Added 388.6 to supported firmware list.

Fixes:
- Updated logic for IPv6 Address data collection.
- The default rules created by the firmware will be deleted if a custom load balancing rule priority is configured.
- OpenVPN Clients will be restarted during failover events.
- Null values for WAN Web GUI IP Addresses are now valid.

Note:
To update to beta release you must enable Dev Mode in the Configuration.

 

[DougA]

I have another thread with questions regarding WAN 0 and WAN 1 issues, but figured I would post it here in case others have a similar questions. I have everything installed and working, with one exception. When both WAN interfaces are connected, it shows the Primary WAN as Hot Standby, and my Secondary WAN as Connected. How do I switch so the Primary WAN is connected and the Secondary WAN is in Hot Standby.

 

[Ranger802004]

I have another thread with questions regarding WAN 0 and WAN 1 issues, but figured I would post it here in case others have a similar questions. I have everything installed and working, with one exception. When both WAN interfaces are connected, it shows the Primary WAN as Hot Standby, and my Secondary WAN as Connected. How do I switch so the Primary WAN is connected and the Secondary WAN is in Hot Standby.

Monitor the system log and make sure the WAN0 Target IP is pinging successfully.

 

[DougA]

Monitor the system log and make sure the WAN0 Target IP is pinging successfully.

I plugged the secondary WAN in again and this time it seems to be working. Primary WAN is up and Secondary WAN shows as Hot Standby. Thanks for the script, nice work.

 

[BikeHelmet]

***v2.1.1-beta2 Released***
Release Notes:
Enhancements:
- Added 388.5 to supported firmware list.
- Added 388.6 to supported firmware list.

Fixes:
- Updated logic for IPv6 Address data collection.
- The default rules created by the firmware will be deleted if a custom load balancing rule priority is configured.
- OpenVPN Clients will be restarted during failover events.
- Null values for WAN Web GUI IP Addresses are now valid.

Note:
To update to beta release you must enable Dev Mode in the Configuration.

Hey, would you be willing to implement a new feature? I just realized that something is turning flowcache back on, on my RT-AX56U router. On it and the RT-AX68U (and probably other AX models), when it's enabled, traffic doesn't show up in FlexQOS. You can be downloading a game at 50mbit from Steam, and it'll happily insist that you're using 600kbit on Net Control Packets. Then if you Putty in and do fc disable, it instantly jumps to ~50000kbit on File Transfer or Other. There's also significant pingspikes if it's enabled, and they disappear when it is disabled.

My thought is, since you already have QOS configuration options there, maybe add a "Flowcache work-around" toggle that if enabled, applies fc disable periodically when the connection changes or a connection shifts mode. (Hot Standby, Connected, etc.)

Just a thought, but it would be handy for people afflicted by the flowcache bug.

 

[Ranger802004]

Hey, would you be willing to implement a new feature? I just realized that something is turning flowcache back on, on my RT-AX56U router. On it and the RT-AX68U (and probably other AX models), when it's enabled, traffic doesn't show up in FlexQOS. You can be downloading a game at 50mbit from Steam, and it'll happily insist that you're using 600kbit on Net Control Packets. Then if you Putty in and do fc disable, it instantly jumps to ~50000kbit on File Transfer or Other. There's also significant pingspikes if it's enabled, and they disappear when it is disabled.

My thought is, since you already have QOS configuration options there, maybe add a "Flowcache work-around" toggle that if enabled, applies fc disable periodically when the connection changes or a connection shifts mode. (Hot Standby, Connected, etc.)

Just a thought, but it would be handy for people afflicted by the flowcache bug.

I would recommend to submit this request via the GitHub.

 

[AndrewL733]

Hello @Ranger802004 ,

Thank you for your very hard work. You have obviously put a huge amount of time into this project. I am wondering if you can tell me whether your WAN failover solution will solve my specific problem?

• I have an ASUS RT-AC68U with the latest Merlin FW.
• My primary WAN is a Fiber Modem Router in "Bridge Mode"
• My secondary WAN is a 4G/LTE TP-Link Router with a LAN port (and I port forward SSH and HTTPS ports so that I can reach my ASUS router via the TP-Link)
• I have DUAL WAN enabled
• I am using Ethernet 2 as my secondary WAN on the ASUS router
• I have Failover and Failback enabled, and I am pinging 8.8.8.8
• On a fresh reboot, Primary WAN is "Connected" and Secondary WAN is in "Cold Standby"
• When I unplug Primary WAN, after a few minutes Secondary WAN shows "Connected" and Primary WAN shows "Disconnected"
• I have Internet access from devices in my house
• I observe that a new vlan3 is active on the ASUS router with a LAN IP address given by the TP-Link router
• I re-plug in the Primary WAN and after a few minutes it shows "Connected" and the Secondary WAN shows "Hot Standby" (not "Cold Standby" like at the beginning)
• Web browsers on my network are now using the Primary WAN, but my standalone VPN Gateway (a mini Linux PC running Wireguard plus GRETAP to create a high-performance virtual Ethernet switch) is still managing to send data through the 4G/LTE modem (the Secondary WAN).

Under the above scenario, I inadvertently used up all 45 GB of my monthly mobile data plan allotment just watching 1 UHD movie over the VPN. I believe this would not have occurred had the Secondary WAN on the ASUS Router been returned to "Cold Standby" after failback to the Primary WAN.

My questions to you are:

1. Would your failover solution put the Secondary WAN into "Cold Standby" after failback?
2. Also, I want to look closely at how the Guest Network is handled by failover and failback. I didn't verify whether all networks work correctly during failover. But with your code do all networks still work after failover and failback? (all the IoT devices in my house are on my Guest Network).

I am going to repeat the whole above scenario to look more closely at what happens during failover and failback. What vlans get created and destroyed (or not)? What bridges are the vlans added to and removed from (or not) during failover and failback.

I would appreciate your reply to my two questions. Thanks!

-- Andrew

 

[Ranger802004]

Hello @Ranger802004 ,

Thank you for your very hard work. You have obviously put a huge amount of time into this project. I am wondering if you can tell me whether your WAN failover solution will solve my specific problem?

• I have an ASUS RT-AC68U with the latest Merlin FW.
• My primary WAN is a Fiber Modem Router in "Bridge Mode"
• My secondary WAN is a 4G/LTE TP-Link Router with a LAN port (and I port forward SSH and HTTPS ports so that I can reach my ASUS router via the TP-Link)
• I have DUAL WAN enabled
• I am using Ethernet 2 as my secondary WAN on the ASUS router
• I have Failover and Failback enabled, and I am pinging 8.8.8.8
• On a fresh reboot, Primary WAN is "Connected" and Secondary WAN is in "Cold Standby"
• When I unplug Primary WAN, after a few minutes Secondary WAN shows "Connected" and Primary WAN shows "Disconnected"
• I have Internet access from devices in my house
• I observe that a new vlan3 is active on the ASUS router with a LAN IP address given by the TP-Link router
• I re-plug in the Primary WAN and after a few minutes it shows "Connected" and the Secondary WAN shows "Hot Standby" (not "Cold Standby" like at the beginning)
• Web browsers on my network are now using the Primary WAN, but my standalone VPN Gateway (a mini Linux PC running Wireguard plus GRETAP to create a high-performance virtual Ethernet switch) is still managing to send data through the 4G/LTE modem (the Secondary WAN).

Under the above scenario, I inadvertently used up all 45 GB of my monthly mobile data plan allotment just watching 1 UHD movie over the VPN. I believe this would not have occurred had the Secondary WAN on the ASUS Router been returned to "Cold Standby" after failback to the Primary WAN.

My questions to you are:

1. Would your failover solution put the Secondary WAN into "Cold Standby" after failback?
2. Also, I want to look closely at how the Guest Network is handled by failover and failback. I didn't verify whether all networks work correctly during failover. But with your code do all networks still work after failover and failback? (all the IoT devices in my house are on my Guest Network).

I am going to repeat the whole above scenario to look more closely at what happens during failover and failback. What vlans get created and destroyed (or not)? What bridges are the vlans added to and removed from (or not) during failover and failback.

I would appreciate your reply to my two questions. Thanks!

-- Andrew

It sounds like your router was still using your secondary WAN as the primary somehow, my script will make both WANs Hot-Standby capable and actively ping both for connectivity but only use the Primary WAN in Failover mode. There would be minimal usage on the secondary for the ICMP Ping traffic which you can set the packet size really small to minimize the amount of data used.

 

[RandomUser777]

First, fantastic utility Ranger!

Second, I have a handful of lazy clients (FireTV 4k Stick is one of them) that for some reason almost always require a device restart or wifi disconnect/reconnect to sense network connectivity after a failover/failback. Not a huge deal, as the devices which do this are non-essential.

But, I was wondering if it makes sense to add a conntrack flush command after you switch WANs?

 

[Ranger802004]

First, fantastic utility Ranger!

Second, I have a handful of lazy clients (FireTV 4k Stick is one of them) that for some reason almost always require a device restart or wifi disconnect/reconnect to sense network connectivity after a failover/failback. Not a huge deal, as the devices which do this are non-essential.

But, I was wondering if it makes sense to add a conntrack flush command after you switch WANs?

Submit a request via GitHub and I’ll look into making it an option.

 

[Ranger802004]

***v2.1.1-beta3 Released***

Release Notes:
v2.1.1-beta3 - 02/02/2024
Enhancements:
- Added 388.5 to supported firmware list.
- Added 388.6 to supported firmware list.
- Added configuration option to perform a conntrack flush during failover.

Fixes:
- Updated logic for IPv6 Address data collection.
- The default rules created by the firmware will be deleted if a custom load balancing rule priority is configured.
- OpenVPN Clients will be restarted during failover events.
- Null values for WAN Web GUI IP Addresses are now valid.

Note:
To update to beta release you must enable Dev Mode in the Configuration.

 

[DougA]

@Ranger802004 Any idea why I keep getting these messages in the log? My pings to 1.1.1.1 and 8.8.8.8 are fast when I ping normally.

Feb 2 20:26:13 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 40ms
Feb 2 20:26:35 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN0 Ping Time: 262ms
Feb 2 20:26:43 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN0 Ping Time: 17ms
Feb 2 20:26:43 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 109ms
Feb 2 20:26:46 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 59ms
Feb 2 20:26:51 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 114ms
Feb 2 20:26:53 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 46ms
Feb 2 20:26:58 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 113ms
Feb 2 20:27:01 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 67ms
Feb 2 20:27:08 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN0 Ping Time: 89ms
Feb 2 20:27:13 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN0 Ping Time: 34ms
Feb 2 20:27:24 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN0 Ping Time: 387ms
Feb 2 20:27:24 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 114ms
Feb 2 20:27:26 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 44ms
Feb 2 20:27:37 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 120ms
Feb 2 20:27:39 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN0 Ping Time: 18ms
Feb 2 20:27:39 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 46ms
Feb 2 20:27:52 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 110ms
Feb 2 20:27:54 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 69ms
Feb 2 20:28:09 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 99ms
Feb 2 20:28:11 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 39ms
Feb 2 20:28:16 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 125ms
Feb 2 20:28:19 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 54ms
Feb 2 20:28:24 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 110ms
Feb 2 20:28:26 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 62ms
Feb 2 20:28:43 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 123ms
Feb 2 20:28:46 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 53ms
Feb 2 20:28:56 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 123ms
Feb 2 20:28:58 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 45ms
Feb 2 20:29:00 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 94ms
Feb 2 20:29:03 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 41ms
Feb 2 20:29:20 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 115ms
Feb 2 20:29:23 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN0 Ping Time: 356ms
Feb 2 20:29:23 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 61ms
Feb 2 20:29:25 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN0 Ping Time: 18ms
Feb 2 20:29:28 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN0 Ping Time: 279ms
Feb 2 20:29:28 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 122ms
Feb 2 20:29:30 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 48ms
Feb 2 20:29:35 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN0 Ping Time: 59ms
Feb 2 20:29:53 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 113ms
Feb 2 20:29:56 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 41ms
Feb 2 20:30:15 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 107ms
Feb 2 20:30:18 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 42ms
Feb 2 20:31:19 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 109ms
Feb 2 20:31:22 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 40ms
Feb 2 20:31:29 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 104ms

 

[Ranger802004]

@Ranger802004 Any idea why I keep getting these messages in the log? My pings to 1.1.1.1 and 8.8.8.8 are fast when I ping normally.

Feb 2 20:26:13 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 40ms
Feb 2 20:26:35 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN0 Ping Time: 262ms
Feb 2 20:26:43 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN0 Ping Time: 17ms
Feb 2 20:26:43 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 109ms
Feb 2 20:26:46 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 59ms
Feb 2 20:26:51 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 114ms
Feb 2 20:26:53 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 46ms
Feb 2 20:26:58 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 113ms
Feb 2 20:27:01 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 67ms
Feb 2 20:27:08 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN0 Ping Time: 89ms
Feb 2 20:27:13 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN0 Ping Time: 34ms
Feb 2 20:27:24 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN0 Ping Time: 387ms
Feb 2 20:27:24 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 114ms
Feb 2 20:27:26 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 44ms
Feb 2 20:27:37 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 120ms
Feb 2 20:27:39 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN0 Ping Time: 18ms
Feb 2 20:27:39 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 46ms
Feb 2 20:27:52 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 110ms
Feb 2 20:27:54 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 69ms
Feb 2 20:28:09 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 99ms
Feb 2 20:28:11 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 39ms
Feb 2 20:28:16 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 125ms
Feb 2 20:28:19 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 54ms
Feb 2 20:28:24 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 110ms
Feb 2 20:28:26 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 62ms
Feb 2 20:28:43 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 123ms
Feb 2 20:28:46 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 53ms
Feb 2 20:28:56 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 123ms
Feb 2 20:28:58 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 45ms
Feb 2 20:29:00 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 94ms
Feb 2 20:29:03 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 41ms
Feb 2 20:29:20 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 115ms
Feb 2 20:29:23 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN0 Ping Time: 356ms
Feb 2 20:29:23 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 61ms
Feb 2 20:29:25 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN0 Ping Time: 18ms
Feb 2 20:29:28 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN0 Ping Time: 279ms
Feb 2 20:29:28 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 122ms
Feb 2 20:29:30 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 48ms
Feb 2 20:29:35 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN0 Ping Time: 59ms
Feb 2 20:29:53 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 113ms
Feb 2 20:29:56 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 41ms
Feb 2 20:30:15 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 107ms
Feb 2 20:30:18 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 42ms
Feb 2 20:31:19 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 109ms
Feb 2 20:31:22 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 40ms
Feb 2 20:31:29 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 104ms

Maybe something on your router taking up resources. I doubt both of your interfaces are getting that same amount of latency at the same time.

 

[DougA]

Maybe something on your router taking up resources. I doubt both of your interfaces are getting that same amount of latency at the same time.

Nothing looks out of the ordinary. Not too much traffic, cpu usage is low, internet seems to be working fine. When it gives me the ping times for each WAN, what is it pinging? Can I try pinging it through the command prompt and see if I am getting the same results?

 

[brummygit]

@Ranger802004 Any idea why I keep getting these messages in the log? My pings to 1.1.1.1 and 8.8.8.8 are fast when I ping normally.

Feb 2 20:26:13 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 40ms
Feb 2 20:26:35 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN0 Ping Time: 262ms
Feb 2 20:26:43 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN0 Ping Time: 17ms
Feb 2 20:26:43 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 109ms
Feb 2 20:26:46 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 59ms
Feb 2 20:26:51 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 114ms
Feb 2 20:26:53 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 46ms
Feb 2 20:26:58 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 113ms
Feb 2 20:27:01 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 67ms
Feb 2 20:27:08 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN0 Ping Time: 89ms
Feb 2 20:27:13 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN0 Ping Time: 34ms
Feb 2 20:27:24 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN0 Ping Time: 387ms
Feb 2 20:27:24 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 114ms
Feb 2 20:27:26 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 44ms
Feb 2 20:27:37 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 120ms
Feb 2 20:27:39 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN0 Ping Time: 18ms
Feb 2 20:27:39 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 46ms
Feb 2 20:27:52 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 110ms
Feb 2 20:27:54 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 69ms
Feb 2 20:28:09 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 99ms
Feb 2 20:28:11 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 39ms
Feb 2 20:28:16 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 125ms
Feb 2 20:28:19 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 54ms
Feb 2 20:28:24 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 110ms
Feb 2 20:28:26 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 62ms
Feb 2 20:28:43 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 123ms
Feb 2 20:28:46 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 53ms
Feb 2 20:28:56 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 123ms
Feb 2 20:28:58 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 45ms
Feb 2 20:29:00 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 94ms
Feb 2 20:29:03 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 41ms
Feb 2 20:29:20 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 115ms
Feb 2 20:29:23 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN0 Ping Time: 356ms
Feb 2 20:29:23 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 61ms
Feb 2 20:29:25 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN0 Ping Time: 18ms
Feb 2 20:29:28 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN0 Ping Time: 279ms
Feb 2 20:29:28 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 122ms
Feb 2 20:29:30 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 48ms
Feb 2 20:29:35 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN0 Ping Time: 59ms
Feb 2 20:29:53 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 113ms
Feb 2 20:29:56 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 41ms
Feb 2 20:30:15 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 107ms
Feb 2 20:30:18 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 42ms
Feb 2 20:31:19 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 109ms
Feb 2 20:31:22 wan-failover: Ping Time Below Maximum Threshold: 80ms - WAN1 Ping Time: 40ms
Feb 2 20:31:29 wan-failover: Ping Time Above Maximum Threshold: 80ms - WAN1 Ping Time: 104ms

I've been seeing the same issue and eventually my router decided to start trying to failover. I'm overseas currently and got a report from home that there was no internet. A reboot fixed it temporarily but I was starting to get the same log errors so I have temporarily removed your script until I'm home.

I haven't done much digging, but for a while it has felt as though running the script for more than a few days starts to cause issues, and then eventually if I do get a failover after a long period of running it doesn't always cutover to my secondary line smoothly and requires a reboot.

I will be home in a week when I can try to do some more diagnostics, but wanted to confirm this is not only a 1 user issue.

 

[Ranger802004]

Nothing looks out of the ordinary. Not too much traffic, cpu usage is low, internet seems to be working fine. When it gives me the ping times for each WAN, what is it pinging? Can I try pinging it through the command prompt and see if I am getting the same results?

I personally see these sometimes too and clear up periodically or sometimes it’s indicative of a resource issue on the router. It’s just the router pinging from the loop back interface to the specified wan interface and target IP using the ping timeout and count parameters you specify, the number is an average so you could have all of your pings be normal and one slow packet respond and it spike your latency reported by the script.

 

[Ranger802004]

I've been seeing the same issue and eventually my router decided to start trying to failover. I'm overseas currently and got a report from home that there was no internet. A reboot fixed it temporarily but I was starting to get the same log errors so I have temporarily removed your script until I'm home.

I haven't done much digging, but for a while it has felt as though running the script for more than a few days starts to cause issues, and then eventually if I do get a failover after a long period of running it doesn't always cutover to my secondary line smoothly and requires a reboot.

I will be home in a week when I can try to do some more diagnostics, but wanted to confirm this is not only a 1 user issue.

Make sure you collect debug logs, there are a lot of factors at play including features and scripts you are using. For example I have seen firewall service restart not finish everything because of something in the firewall-start script that was not allowing the script to complete, this is just one example I have seen.

 

[Ranger802004]

***v2.1.1 Released***

Release Notes:
Enhancements:
- Added 388.5 to supported firmware list.
- Added 388.6 to supported firmware list.
- Added configuration option to perform a conntrack flush during failover.

Fixes:
- Updated logic for IPv6 Address data collection.
- The default rules created by the firmware will be deleted if a custom load balancing rule priority is configured.
- OpenVPN Clients will be restarted during failover events.
- Null values for WAN Web GUI IP Addresses are now valid.

 

[tarzan2000]

How to switch from beta to release?