Menu
What's new
By:
Filters Better Search

WANFailover Dual WAN Failover Script

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

lbtboy said:
Hello. Version: v1.4.6 . The problem is that after restarting the router, the connection is always on the secondary wan, and the primary wan is in constant hot-stanbay and does not switch to connected. It is solved simply by disconnecting the secondary wan cable and connecting it back. What could be the problem?
Click to expand...

What is your setup as in the type of ISP service ( cable, fiber, USB cell, etc. ) and which service is on which interface?

Try the v1.5.0-beta and see if it corrects the issue. It is working great for me.
 
Smokey613 said:
What is your setup as in the type of ISP service ( cable, fiber, USB cell, etc. ) and which service is on which interface?

Try the v1.5.0-beta and see if it corrects the issue. It is working great for me.
Click to expand...
The primary WAN - Internet provider cable with MAC authorization is connected to the WAN. The secondary WAN - LTE modem is connected by cable to the third port of the router. How do I upgrade to the beta version for verification and back if nothing changes?
 

Attachments

  • Port.png
    Port.png
    12.5 KB · Views: 64
  • wan.jpg
    wan.jpg
    102.6 KB · Views: 63
  • eth_lan.jpg
    eth_lan.jpg
    95.5 KB · Views: 65
lbtboy said:
The primary WAN - Internet provider cable with MAC authorization is connected to the WAN. The secondary WAN - LTE modem is connected by cable to the third port of the router. How do I upgrade to the beta version for verification and back if nothing changes?
Click to expand...

Do you have logs you can send? There are others that have issues that were similar that I have worked on in the latest beta releases.
 
Ranger802004 said:
Do you have logs you can send? There are others that have issues that were similar that I have worked on in the latest beta releases.
Click to expand...
It will probably be easier for me to delete this script and use the built-in one, because I do not know what logs you need, I do not see the point in sending everything, there is a lot of confidential information there. Judging by the logs, the script does not run, and when running manually, for some reason, the wan provider is constantly reconnected.

@router:/tmp/home/root# /jffs/scripts/wan-failover.sh run
wan-failover.sh - Run Mode
Switching to wan0
sed: can't move '/tmp/resolv.confThnzCj' to '/tmp/resolv.conf': Device or resource busy
 
lbtboy said:
It will probably be easier for me to delete this script and use the built-in one, because I do not know what logs you need, I do not see the point in sending everything, there is a lot of confidential information there. Judging by the logs, the script does not run, and when running manually, for some reason, the wan provider is constantly reconnected.

@router:/tmp/home/root# /jffs/scripts/wan-failover.sh run
wan-failover.sh - Run Mode
Switching to wan0
sed: can't move '/tmp/resolv.confThnzCj' to '/tmp/resolv.conf': Device or resource busy
Click to expand...

Because the logs help diagnose the issue and you can remove private info if necessary. If you read through the thread we have had several people do this to help patch the script to resolve issues. The ASUS built in failover is not good and that’s why the script exists.

V1.4.9-beta is the current version that seems reliable for the most part but still in testing on that one. V1.5.0-beta has issues and I have v1.5.1-beta being tested before posting in here.
 
Ranger802004 said:
Because the logs help diagnose the issue and you can remove private info if necessary. If you read through the thread we have had several people do this to help patch the script to resolve issues. The ASUS built in failover is not good and that’s why the script exists.

V1.4.9-beta is the current version that seems reliable for the most part but still in testing on that one. V1.5.0-beta has issues and I have v1.5.1-beta being tested before posting in here.
Click to expand...
I understand you perfectly well, which helps diagnose the problem. But I repeat once again there is no mention in the logs that the script is running and there is no task in cron "*/1 * * * * /jffs/scripts/wan-failover.sh run". So I honestly just don't understand what I can send you, a log of 100,000 lines? Now I have installed version 1.5.0, nothing has changed. I cleared the logs and rebooted, the log is full, but for some reason the .txt file does not attach.
 
Last edited:
lbtboy said:
I understand you perfectly well, which helps diagnose the problem. But I repeat once again there is no mention in the logs that the script is running and there is no task in cron "*/1 * * * * /jffs/scripts/wan-failover.sh run". So I honestly just don't understand what I can send you, a log of 100,000 lines? Now I have installed version 1.5.0, nothing has changed. I cleared the logs and rebooted, the log is full, but for some reason the .txt file does not attach.
Click to expand...

Does your wan-event script exist and if so did it properly add the line for creating cron job?
 
Ranger802004 said:
Because the logs help diagnose the issue and you can remove private info if necessary. If you read through the thread we have had several people do this to help patch the script to resolve issues. The ASUS built in failover is not good and that’s why the script exists.

V1.4.9-beta is the current version that seems reliable for the most part but still in testing on that one. V1.5.0-beta has issues and I have v1.5.1-beta being tested before posting in here.
Click to expand...

To correct my earlier post, I am running V1.4.9-beta without any issues. I have not looked at any of the later versions.
 
Smokey613 said:
To correct my earlier post, I am running V1.4.9-beta without any issues. I have not looked at any of the later versions.
Click to expand...
Yea don’t upgrade to v1.5.0-beta, not that it will break but I already have an identified issue I’m waiting to confirm the fix (it happens when you add new code….) and confirming v1.5.1-beta resolves it before posting.
 
Ranger802004 said:
Because the logs help diagnose the issue and you can remove private info if necessary. If you read through the thread we have had several people do this to help patch the script to resolve issues. The ASUS built in failover is not good and that’s why the script exists.

V1.4.9-beta is the current version that seems reliable for the most part but still in testing on that one. V1.5.0-beta has issues and I have v1.5.1-beta being tested before posting in here.
Click to expand...
This gives out after the launch "/jffs/scripts/wan-failover.sh run". I collected the log after the reboot, but it is not attached to the post in the format.txt

Jun 24 23:32:33 router wan-failover.sh: WAN Status - wan0 enabled
Jun 24 23:32:33 router wan-failover.sh: WAN Status - Creating route 9.9.9.9 via 178.249.55.30 dev eth0
Jun 24 23:32:33 router wan-failover.sh: WAN Status - Created route 9.9.9.9 via 178.249.55.30 dev eth0
Jun 24 23:32:36 router wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 24 23:32:36 router wan-failover.sh: WAN Status - wan1 enabled
Jun 24 23:32:36 router wan-failover.sh: WAN Status - Default route already exists via 192.168.199.1 dev eth2
Jun 24 23:32:39 router wan-failover.sh: WAN Status - wan1 has 0% packet loss
Jun 24 23:32:39 router wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 24 23:32:39 router wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 9.9.9.9 for Failure
Ranger802004 said:
Does your wan-event script exist and if so did it properly add the line for creating cron job?
Click to expand...
It exists, but it doesn't add a line.
 
lbtboy said:
This gives out after the launch "/jffs/scripts/wan-failover.sh run". I collected the log after the reboot, but it is not attached to the post in the format.txt

Jun 24 23:32:33 router wan-failover.sh: WAN Status - wan0 enabled
Jun 24 23:32:33 router wan-failover.sh: WAN Status - Creating route 9.9.9.9 via 178.249.55.30 dev eth0
Jun 24 23:32:33 router wan-failover.sh: WAN Status - Created route 9.9.9.9 via 178.249.55.30 dev eth0
Jun 24 23:32:36 router wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 24 23:32:36 router wan-failover.sh: WAN Status - wan1 enabled
Jun 24 23:32:36 router wan-failover.sh: WAN Status - Default route already exists via 192.168.199.1 dev eth2
Jun 24 23:32:39 router wan-failover.sh: WAN Status - wan1 has 0% packet loss
Jun 24 23:32:39 router wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 24 23:32:39 router wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 9.9.9.9 for Failure

It exists, but it doesn't add a line.
Click to expand...

The logs indicate the script is working and monitoring properly, your issue appears to be during the install phase the cron job wasn’t added to wan-event for some reason. Do you have a special script format in wan-event or permissions that deny modifying?
 
Ranger802004 said:
The logs indicate the script is working and monitoring properly, your issue appears to be during the install phase the cron job wasn’t added to wan-event for some reason. Do you have a special script format in wan-event or permissions that deny modifying?
Click to expand...
There are no forbidding scenarios.
 
Last edited:
Ranger802004 said:
Rerun the install function and capture logs and see what it says when it goes to add it to wan-event.

EDIT: You can run a separate console in monitor mode or capture them from the System Log to capture logs.

You can upgrade to v1.4.9-beta using instructions here: https://www.snbforums.com/threads/dual-wan-failover-script.78978/post-770561
Click to expand...
In my opinion, he won by rolling back to version 1.4.6, by adding to cron "*/1 * * * * /jffs/scripts/wan-failover.sh run" via cru and settings

PINGCOUNT=4
PINGTIMEOUT=1
WANDISABLEDSLEEPTIMER=1

It was:

PINGCOUNT=4
PINGTIMEOUT=4
WANDISABLEDSLEEPTIMER=3
 
lbtboy said:
In my opinion, he won by rolling back to version 1.4.6, by adding to cron "*/1 * * * * /jffs/scripts/wan-failover.sh run" via cru and settings

PINGCOUNT=4
PINGTIMEOUT=1
WANDISABLEDSLEEPTIMER=1

It was:

PINGCOUNT=4
PINGTIMEOUT=4
WANDISABLEDSLEEPTIMER=3
Click to expand...
Between 1.4.6 and 1.5.1-beta, there is no difference on the install functionality for that portion. This is all operational changes but doesn't change anything on how the script installs/uninstalls. You may have had a strange issue going on with writing to your wan-event script at the time of install. I did notice one of your logs had trouble writing to /tmp/resolv.conf at one point. Also I'd only set the Ping timeout that high if you are on a high latency WAN link such as satellite, it's basically waiting 4 seconds to fail a ping if there is no response. Typically 1 (1000ms) is good for that.
v1.5.1-beta
- Added delay in WAN Status for when NVRAM is inaccessible.
- Added support for Load Balance Mode
- Changed from using NVRAM Variables: wan0_ifname & wan1_ifname to using NVRAM Variables: wan0_gw_ifname & wan1_gw_ifname.
- Improved DNS Settings detection during Switch WAN function.
- Improved Switch WAN Logic to verify NVRAM Variables: wan_gateway, wan_gw_ifname, and wan_ipaddr are properly updated.
- Added warning message when attempting to execute Run or Manual Mode if the script is already running.
- IP Routes are now given a value of metric 1 when created during WAN Status checks.
- Improved detection of existing routes for WAN Target IP Addresses.
 
1.5.1-beta don't work for me on all routers

Code: 
Jun 25 11:37:17 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:37:17 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:37:17 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:37:17 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:37:17 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:37:21 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:37:21 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:37:21 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:37:27 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:37:27 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:37:27 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:37:28 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:37:28 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:37:32 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:37:32 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:37:32 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:37:38 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:37:38 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:37:38 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:37:38 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:37:38 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:37:42 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:37:42 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:37:42 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:37:48 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:37:48 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:37:48 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:37:48 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:37:48 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:37:52 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:37:52 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:37:52 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:37:58 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:37:58 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:37:58 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:37:58 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:37:58 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:02 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:38:02 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:38:02 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:08 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:38:08 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:38:08 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:38:08 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:38:08 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:12 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:38:12 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:38:13 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:19 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:38:19 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:38:19 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:38:19 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:38:19 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:23 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:38:23 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:38:23 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:29 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:38:29 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:38:29 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:38:29 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:38:29 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:33 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:38:33 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:38:33 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:39 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:38:39 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:38:39 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:38:39 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:38:39 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:43 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:38:43 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:38:43 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:49 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:38:49 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:38:49 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:38:49 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:38:49 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:53 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:38:53 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:38:53 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:59 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:38:59 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:38:59 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:39:00 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:39:00 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:39:04 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:39:04 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:39:04 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:39:10 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:39:10 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:39:10 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:39:10 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:39:10 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:39:14 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:39:14 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:39:14 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:39:20 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:39:20 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:39:20 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:39:20 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:39:20 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:39:24 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:39:24 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:39:24 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:39:30 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:39:30 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:39:30 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:39:30 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:39:30 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:39:34 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:39:34 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:39:34 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
 
VIper_Rus said:
1.5.1-beta don't work for me on all routers

Code: 
Jun 25 11:37:17 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:37:17 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:37:17 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:37:17 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:37:17 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:37:21 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:37:21 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:37:21 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:37:27 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:37:27 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:37:27 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:37:28 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:37:28 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:37:32 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:37:32 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:37:32 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:37:38 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:37:38 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:37:38 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:37:38 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:37:38 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:37:42 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:37:42 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:37:42 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:37:48 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:37:48 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:37:48 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:37:48 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:37:48 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:37:52 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:37:52 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:37:52 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:37:58 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:37:58 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:37:58 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:37:58 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:37:58 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:02 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:38:02 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:38:02 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:08 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:38:08 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:38:08 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:38:08 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:38:08 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:12 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:38:12 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:38:13 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:19 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:38:19 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:38:19 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:38:19 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:38:19 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:23 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:38:23 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:38:23 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:29 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:38:29 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:38:29 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:38:29 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:38:29 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:33 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:38:33 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:38:33 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:39 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:38:39 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:38:39 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:38:39 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:38:39 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:43 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:38:43 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:38:43 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:49 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:38:49 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:38:49 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:38:49 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:38:49 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:53 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:38:53 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:38:53 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:38:59 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:38:59 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:38:59 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:39:00 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:39:00 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:39:04 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:39:04 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:39:04 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:39:10 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:39:10 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:39:10 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:39:10 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:39:10 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:39:14 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:39:14 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:39:14 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:39:20 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:39:20 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:39:20 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:39:20 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:39:20 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:39:24 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:39:24 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:39:24 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:39:30 wan-failover.sh: WAN Status - wan1 has 100% packet loss ***Verify 1.0.0.1 is a valid server for ICMP Echo Requests***
Jun 25 11:39:30 wan-failover.sh: WAN0 Active - Verifying WAN0
Jun 25 11:39:30 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
Jun 25 11:39:30 wan-failover.sh: WAN Status - wan0 enabled
Jun 25 11:39:30 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Jun 25 11:39:34 wan-failover.sh: WAN Status - wan0 has 0% packet loss
Jun 25 11:39:34 wan-failover.sh: WAN Status - wan1 enabled
Jun 25 11:39:34 wan-failover.sh: WAN Status - Route already exists for incorrect Gateway or Interface:
Click to expand...
1.5.1-beta is uploaded but haven't advertised to publicly test it because of known issue, I'm working on it now actually.

EDIT: I've performed an overwrite of the 1.5.1-beta release to a patched version, try it now.
 
Last edited:
v1.5.1-beta Release:
Manually upgrade to this beta by running the following command" ***Allow for cronjob to relaunch the script***
Code: 
/usr/sbin/curl -s "https://raw.githubusercontent.com/Ranger802004/asusmerlin/main/wan-failover_v1.5.1-beta.sh" -o "/jffs/scripts/wan-failover.sh" && chmod 755 /jffs/scripts/wan-failover.sh && sh /jffs/scripts/wan-failover.sh kill

To revert back to Production Release:
Code: 
/jffs/scripts/wan-failover.sh update

Release Notes:
v1.5.1-beta
- Added delay in WAN Status for when NVRAM is inaccessible.
- Added support for Load Balance Mode
- Changed from using NVRAM Variables: wan0_ifname & wan1_ifname to using NVRAM Variables: wan0_gw_ifname & wan1_gw_ifname.
- Improved DNS Settings detection during Switch WAN function.
- Improved Switch WAN Logic to verify NVRAM Variables: wan_gateway, wan_gw_ifname, and wan_ipaddr are properly updated.
- Added warning message when attempting to execute Run or Manual Mode if the script is already running.
- IP Routes are now given a value of metric 1 when created during WAN Status checks.
- Improved detection of existing routes for WAN Target IP Addresses to identify potential misconfiguration.
Example: WAN0 Target IP Address is a DNS Server for WAN1 and the route already exists for WAN1 Interface.
 
Yes, everything is ok now.

Well, not quite OK, just as it was, OK on two routers, and on one 5 minutes after rebooting switches WAN0 and WAN1 without interruption and eventually gets into normal mode

Code: 
     193: Jun 25 13:49:00 wan-failover.sh: WAN Status - wan0 enabled
     194: Jun 25 13:49:00 wan-failover.sh: WAN Status - Creating route 1.1.1.1 via 10.128.131.254 dev eth0
     195: Jun 25 13:49:00 wan-failover.sh: WAN Status - Created route 1.1.1.1 via 10.128.131.254 dev eth0
     196: Jun 25 13:49:04 wan-failover.sh: WAN Status - wan0 has 0% packet loss
     197: Jun 25 13:49:04 wan-failover.sh: WAN Status - wan1 enabled
     198: Jun 25 13:49:04 wan-failover.sh: WAN Status - Restarting WAN1: eth5
     200: Jun 25 13:49:04 custom_script: Running /jffs/scripts/wan-event (args: 1 stopping)
     229: Jun 25 13:49:05 custom_script: Running /jffs/scripts/wan-event (args: 1 stopped)
     230: Jun 25 13:49:05 custom_script: Running /jffs/scripts/wan-event (args: 1 init)
     232: Jun 25 13:49:05 custom_script: Running /jffs/scripts/wan-event (args: 1 connecting)
     233: Jun 25 13:49:05 custom_script: Running /jffs/scripts/wan-event (args: 1 disconnected)
     234: Jun 25 13:49:05 custom_script: Running /jffs/scripts/wan-event (args: 1 stopped)
     235: Jun 25 13:49:05 custom_script: Running /jffs/scripts/wan-event (args: 1 connected)
     244: Jun 25 13:49:05 wan-failover.sh: WAN Status - Restarted WAN1: eth5
     394: Jun 25 13:50:00 wan-failover.sh: WAN Status - wan0 enabled
     395: Jun 25 13:50:00 wan-failover.sh: WAN Status - Route already exists: 1.1.1.1 via 10.128.131.254 dev eth0 metric 1
     396: Jun 25 13:50:06 wan-failover.sh: WAN Status - wan0 has 100% packet loss ***Verify 1.1.1.1 is a valid server for ICMP Echo Requests***
     397: Jun 25 13:50:06 wan-failover.sh: WAN Status - wan1 enabled
     398: Jun 25 13:50:06 wan-failover.sh: WAN Status - Creating route 1.0.0.1 via 10.1.0.1 dev eth5
     399: Jun 25 13:50:06 wan-failover.sh: WAN Status - Created route 1.0.0.1 via 10.1.0.1 dev eth5
     400: Jun 25 13:50:10 wan-failover.sh: WAN Status - wan1 has 0% packet loss
     401: Jun 25 13:50:10 wan-failover.sh: WAN1 Active - Verifying WAN1
     402: Jun 25 13:50:10 wan-failover.sh: WAN Switch - Switching wan1 to Primary WAN
     403: Jun 25 13:50:10 wan-failover.sh: WAN Switch - WAN IP Address: 10.1.0.2
     404: Jun 25 13:50:10 wan-failover.sh: WAN Switch - WAN Gateway: 10.1.0.1
     405: Jun 25 13:50:10 wan-failover.sh: WAN Switch - WAN Interface: eth5
     406: Jun 25 13:50:10 wan-failover.sh: WAN Switch - WAN Interface: eth5
     407: Jun 25 13:50:10 wan-failover.sh: WAN Switch - /tmp/resolv.conf already updated for wan1 DNS1 Server
     408: Jun 25 13:50:10 wan-failover.sh: WAN Switch - /tmp/resolv.conf already updated for wan1 DNS2 Server
     409: Jun 25 13:50:10 wan-failover.sh: WAN Switch - Deleting default route via 10.128.131.254 dev eth0
     410: Jun 25 13:50:10 wan-failover.sh: WAN Switch - Adding default route via 10.1.0.1 dev eth5
     411: Jun 25 13:50:10 wan-failover.sh: WAN Switch - QoS is Disabled
     412: Jun 25 13:50:11 wan-failover.sh: WAN Switch - Switched wan1 to Primary WAN
     413: Jun 25 13:50:11 wan-failover.sh: Service Restart - Restarting qos service
     415: Jun 25 13:50:11 wan-failover.sh: Service Restart - Restarted qos service
     416: Jun 25 13:50:11 wan-failover.sh: Service Restart - Restarting leds service
     427: Jun 25 13:50:12 wan-failover.sh: Service Restart - Restarted leds service
     428: Jun 25 13:50:12 wan-failover.sh: Service Restart - Restarting dnsmasq service
     432: Jun 25 13:50:13 wan-failover.sh: Service Restart - Restarted dnsmasq service
     433: Jun 25 13:50:13 wan-failover.sh: Service Restart - Restarting firewall service
     437: Jun 25 13:50:14 wan-failover.sh: Service Restart - Restarted firewall service
     438: Jun 25 13:50:14 wan-failover.sh: Email Notification - Email Notifications are not configured
     439: Jun 25 13:50:14 wan-failover.sh: WAN Status - wan0 enabled
     440: Jun 25 13:50:15 wan-failover.sh: WAN Status - Route already exists: 1.1.1.1 via 10.128.131.254 dev eth0 metric 1
     447: Jun 25 13:50:21 wan-failover.sh: WAN Status - wan0 has 100% packet loss ***Verify 1.1.1.1 is a valid server for ICMP Echo Requests***
     448: Jun 25 13:50:21 wan-failover.sh: WAN Status - wan1 enabled
     449: Jun 25 13:50:21 wan-failover.sh: WAN Status - Route already exists: 1.0.0.1 via 10.1.0.1 dev eth5 metric 1
     450: Jun 25 13:50:25 wan-failover.sh: WAN Status - wan1 has 0% packet loss
     451: Jun 25 13:50:25 wan-failover.sh: WAN1 Active - Verifying WAN1
     452: Jun 25 13:50:25 wan-failover.sh: WAN0 Failback Monitor - Monitoring WAN0 via 1.1.1.1 for Failback
     453: Jun 25 13:50:36 wan-failover.sh: WAN0 Failback Monitor - Packet Loss Detected - WAN0 Packet Loss: 40%
     454: Jun 25 13:50:40 wan-failover.sh: WAN0 Failback Monitor - Connection Detected - WAN0 Packet Loss: 0%
     455: Jun 25 13:50:40 wan-failover.sh: WAN Switch - Switching wan0 to Primary WAN
     456: Jun 25 13:50:40 wan-failover.sh: WAN Switch - WAN IP Address: 10.128.131.80
     457: Jun 25 13:50:40 wan-failover.sh: WAN Switch - WAN Gateway: 10.128.131.254
     458: Jun 25 13:50:40 wan-failover.sh: WAN Switch - WAN Interface: eth0
     459: Jun 25 13:50:40 wan-failover.sh: WAN Switch - WAN Interface: eth0
     460: Jun 25 13:50:40 wan-failover.sh: WAN Switch - /tmp/resolv.conf already updated for wan0 DNS1 Server
     461: Jun 25 13:50:40 wan-failover.sh: WAN Switch - /tmp/resolv.conf already updated for wan0 DNS2 Server
     462: Jun 25 13:50:40 wan-failover.sh: WAN Switch - Deleting default route via 10.1.0.1 dev eth5
     463: Jun 25 13:50:40 wan-failover.sh: WAN Switch - Adding default route via 10.128.131.254 dev eth0
     464: Jun 25 13:50:40 wan-failover.sh: WAN Switch - QoS is Disabled
     465: Jun 25 13:50:41 wan-failover.sh: WAN Switch - Switched wan0 to Primary WAN
     466: Jun 25 13:50:41 wan-failover.sh: Service Restart - Restarting qos service
     468: Jun 25 13:50:41 wan-failover.sh: Service Restart - Restarted qos service
     469: Jun 25 13:50:41 wan-failover.sh: Service Restart - Restarting leds service
     480: Jun 25 13:50:42 wan-failover.sh: Service Restart - Restarted leds service
     481: Jun 25 13:50:42 wan-failover.sh: Service Restart - Restarting dnsmasq service
     485: Jun 25 13:50:43 wan-failover.sh: Service Restart - Restarted dnsmasq service
     486: Jun 25 13:50:43 wan-failover.sh: Service Restart - Restarting firewall service
     489: Jun 25 13:50:44 wan-failover.sh: Service Restart - Restarted firewall service
     490: Jun 25 13:50:44 wan-failover.sh: Email Notification - Email Notifications are not configured
     491: Jun 25 13:50:44 wan-failover.sh: WAN Status - wan0 enabled
     492: Jun 25 13:50:44 wan-failover.sh: WAN Status - Route already exists: 1.1.1.1 via 10.128.131.254 dev eth0 metric 1
     494: Jun 25 13:50:49 wan-failover.sh: WAN Status - wan0 has 20% packet loss
     495: Jun 25 13:50:49 wan-failover.sh: WAN Status - wan1 enabled
     496: Jun 25 13:50:49 wan-failover.sh: WAN Status - Route already exists: 1.0.0.1 via 10.1.0.1 dev eth5 metric 1
     502: Jun 25 13:50:54 wan-failover.sh: WAN Status - wan1 has 0% packet loss
     503: Jun 25 13:50:54 wan-failover.sh: WAN1 Active - Verifying WAN1
     504: Jun 25 13:50:54 wan-failover.sh: WAN Switch - Switching wan1 to Primary WAN
     505: Jun 25 13:50:54 wan-failover.sh: WAN Switch - WAN IP Address: 10.1.0.2
     506: Jun 25 13:50:54 wan-failover.sh: WAN Switch - WAN Gateway: 10.1.0.1
     507: Jun 25 13:50:54 wan-failover.sh: WAN Switch - WAN Interface: eth5
     508: Jun 25 13:50:54 wan-failover.sh: WAN Switch - WAN Interface: eth5
     509: Jun 25 13:50:54 wan-failover.sh: WAN Switch - /tmp/resolv.conf already updated for wan1 DNS1 Server
     510: Jun 25 13:50:54 wan-failover.sh: WAN Switch - /tmp/resolv.conf already updated for wan1 DNS2 Server
     511: Jun 25 13:50:54 wan-failover.sh: WAN Switch - Deleting default route via 10.128.131.254 dev eth0
     512: Jun 25 13:50:54 wan-failover.sh: WAN Switch - Adding default route via 10.1.0.1 dev eth5
     513: Jun 25 13:50:54 wan-failover.sh: WAN Switch - QoS is Disabled
     514: Jun 25 13:50:55 wan-failover.sh: WAN Switch - Switched wan1 to Primary WAN
     515: Jun 25 13:50:55 wan-failover.sh: Service Restart - Restarting qos service
     517: Jun 25 13:50:55 wan-failover.sh: Service Restart - Restarted qos service
     518: Jun 25 13:50:55 wan-failover.sh: Service Restart - Restarting leds service
 
Last edited:
Code: 
     522: Jun 25 13:50:56 wan-failover.sh: Service Restart - Restarted leds service
     523: Jun 25 13:50:56 wan-failover.sh: Service Restart - Restarting dnsmasq service
     526: Jun 25 13:50:57 wan-failover.sh: Service Restart - Restarted dnsmasq service
     527: Jun 25 13:50:57 wan-failover.sh: Service Restart - Restarting firewall service
     530: Jun 25 13:50:58 wan-failover.sh: Service Restart - Restarted firewall service
     531: Jun 25 13:50:58 wan-failover.sh: Email Notification - Email Notifications are not configured
     532: Jun 25 13:50:58 wan-failover.sh: WAN Status - wan0 enabled
     533: Jun 25 13:50:58 wan-failover.sh: WAN Status - Route already exists: 1.1.1.1 via 10.128.131.254 dev eth0 metric 1
     534: Jun 25 13:51:04 wan-failover.sh: WAN Status - wan0 has 100% packet loss ***Verify 1.1.1.1 is a valid server for ICMP Echo Requests***
     535: Jun 25 13:51:04 wan-failover.sh: WAN Status - wan1 enabled
     536: Jun 25 13:51:04 wan-failover.sh: WAN Status - Route already exists: 1.0.0.1 via 10.1.0.1 dev eth5 metric 1
     537: Jun 25 13:51:08 wan-failover.sh: WAN Status - wan1 has 0% packet loss
     538: Jun 25 13:51:08 wan-failover.sh: WAN1 Active - Verifying WAN1
     539: Jun 25 13:51:08 wan-failover.sh: WAN0 Failback Monitor - Monitoring WAN0 via 1.1.1.1 for Failback
     553: Jun 25 13:51:24 wan-failover.sh: WAN0 Failback Monitor - Connection Detected - WAN0 Packet Loss: 0%
     554: Jun 25 13:51:24 wan-failover.sh: WAN Switch - Switching wan0 to Primary WAN
     555: Jun 25 13:51:24 wan-failover.sh: WAN Switch - WAN IP Address: 10.128.131.80
     556: Jun 25 13:51:24 wan-failover.sh: WAN Switch - WAN Gateway: 10.128.131.254
     557: Jun 25 13:51:24 wan-failover.sh: WAN Switch - WAN Interface: eth0
     558: Jun 25 13:51:24 wan-failover.sh: WAN Switch - WAN Interface: eth0
     559: Jun 25 13:51:24 wan-failover.sh: WAN Switch - /tmp/resolv.conf already updated for wan0 DNS1 Server
     560: Jun 25 13:51:25 wan-failover.sh: WAN Switch - /tmp/resolv.conf already updated for wan0 DNS2 Server
     561: Jun 25 13:51:25 wan-failover.sh: WAN Switch - Deleting default route via 10.1.0.1 dev eth5
     562: Jun 25 13:51:25 wan-failover.sh: WAN Switch - Adding default route via 10.128.131.254 dev eth0
     563: Jun 25 13:51:25 wan-failover.sh: WAN Switch - QoS is Disabled
     564: Jun 25 13:51:26 wan-failover.sh: WAN Switch - Switched wan0 to Primary WAN
     565: Jun 25 13:51:26 wan-failover.sh: Service Restart - Restarting qos service
     567: Jun 25 13:51:26 wan-failover.sh: Service Restart - Restarted qos service
     568: Jun 25 13:51:26 wan-failover.sh: Service Restart - Restarting leds service
     572: Jun 25 13:51:27 wan-failover.sh: Service Restart - Restarted leds service
     573: Jun 25 13:51:27 wan-failover.sh: Service Restart - Restarting dnsmasq service
     576: Jun 25 13:51:28 wan-failover.sh: Service Restart - Restarted dnsmasq service
     577: Jun 25 13:51:28 wan-failover.sh: Service Restart - Restarting firewall service
     580: Jun 25 13:51:29 wan-failover.sh: Service Restart - Restarted firewall service
     581: Jun 25 13:51:29 wan-failover.sh: Email Notification - Email Notifications are not configured
     582: Jun 25 13:51:29 wan-failover.sh: WAN Status - wan0 enabled
     583: Jun 25 13:51:29 wan-failover.sh: WAN Status - Route already exists: 1.1.1.1 via 10.128.131.254 dev eth0 metric 1
     584: Jun 25 13:51:33 wan-failover.sh: WAN Status - wan0 has 0% packet loss
     585: Jun 25 13:51:33 wan-failover.sh: WAN Status - wan1 enabled
     586: Jun 25 13:51:33 wan-failover.sh: WAN Status - Route already exists: 1.0.0.1 via 10.1.0.1 dev eth5 metric 1
     587: Jun 25 13:51:37 wan-failover.sh: WAN Status - wan1 has 0% packet loss
     588: Jun 25 13:51:37 wan-failover.sh: WAN0 Active - Verifying WAN0
     589: Jun 25 13:51:37 wan-failover.sh: WAN0 Failover Monitor - Monitoring WAN0 via 1.1.1.1 for Failure
 
You must log in or register to reply here.

Similar threads

J
WANFailover Issue with WF and ax11000 pro?
Replies
3
Views
314
Ranger802004
R
D
Dual Wan Failover
Replies
4
Views
226
Ranger802004
R
R
DomainVPNRouting Domain VPN Routing v3.0.3 ***Release***
2 3
Replies
45
Views
3K
Ranger802004
R
R
Wan Failover Script is reported constant switching
Replies
5
Views
383
routersecskisthedude
R
R
WANFailover Dual WAN Failover ***v2 Release***
23 24 25
Replies
499
Views
51K
JGodfrey82
J
Similar threads
Thread starter Title Forum Replies Date
D Dual Wan Failover Asuswrt-Merlin AddOns 4
D DUAL WAN Failover version v2.1.2 and router RT-AX88U_PRO Asuswrt-Merlin AddOns 0
Maverickcdn Detect Dual WAN in use Asuswrt-Merlin AddOns 4
Viktor Jaep VPNMON VPNMON-R3 v1.3.7 -Oct 20, 2024- Monitor WAN/Dual-WAN/OpenVPN Health & Reset Multiple OpenVPN Connections (Now available in AMTM!) Asuswrt-Merlin AddOns 278
R Wan Failover Script is reported constant switching Asuswrt-Merlin AddOns 5
D amtm The amtm update command does not work when using 2x WAN. Asuswrt-Merlin AddOns 3
B amtm WAN service schedule off/on script ? Asuswrt-Merlin AddOns 14
S Unbound DHCP DNS same as WAN DNS based on merlin-dns-monitor.sh Asuswrt-Merlin AddOns 0
B Unbound unbound/WAN settings Asuswrt-Merlin AddOns 31

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 869 (members: 34, guests: 835)
Top