Dual WAN Failover ***v2 Release***

[Ranger802004]

Thanks again and sorry to be a pest but tried a clean terminal and also a fresh script install directly from SSH and again via amtm to no avail. I am stuck with 2.0.3 for some odd reason.

Try and perform the update again.

 

[Aiadi]

Try and perform the update again.

Honest to god, even formatting the whole USB drive and reinstalling script on a clean drive and still unable to update. I will give up for now but really appreciate your help again.

 

[Ranger802004]

Honest to god, even formatting the whole USB drive and reinstalling script on a clean drive and still unable to update. I will give up for now but really appreciate your help again.

That is very strange, did you open the script file and verify within it is being replaced with the newer version? Possibly some kind of file system issue with your router?

 

[Aiadi]

That is very strange, did you open the script file and verify within it is being replaced with the newer version? Possibly some kind of file system issue with your router?

Thank you @Ranger802004 . I ended up doing a full factory reset for my router and reinstalled the failover script with no other scripts or any fancy settings and I am still unable to upgrade to the beta version. I wonder if any other GT-AX6000 owner have tried this and can confirm whether it's working or not. BTW, still getting the dreaded "unresponsive" status of the script even after the factory reset and a fresh install.

 

[Ranger802004]

Thank you @Ranger802004 . I ended up doing a full factory reset for my router and reinstalled the failover script with no other scripts or any fancy settings and I am still unable to upgrade to the beta version. I wonder if any other GT-AX6000 owner have tried this and can confirm whether it's working or not. BTW, still getting the dreaded "unresponsive" status of the script even after the factory reset and a fresh install.

I would need debug logs to really determine what is going on

 

[Aiadi]

I would need debug logs to really determine what is going on

What is the best way to get these logs? Is it just a question of screenshotting the log capture? All repetitive looking with nothing interesting!

 

[JohnSmith]

Update from V2.0.3-Final to V2.0.4-beta1, appears to be working.

 

[Aiadi]

Update from V2.0.3-Final to V2.0.4-beta1, appears to be working.

GT-AX6000??

 

[Ranger802004]

What is the best way to get these logs? Is it just a question of screenshotting the log capture? All repetitive looking with nothing interesting!

Capture mode

 

[przemekwawa]

I am not sure, if thats the source problem with factory Failower - it restarts LAN connections when moves to second WAN (have to check it but have no possibility now as people are working on it). But, does this solution works the same - breaks LAN connections?
For people in small company that uses Asus router it is important to have backup gsm connection, but more important is to have no interruption with connection to servers that are in LAN.

 

[Ranger802004]

I am not sure, if thats the source problem with factory Failower - it restarts LAN connections when moves to second WAN (have to check it but have no possibility now as people are working on it). But, does this solution works the same - breaks LAN connections?
For people in small company that uses Asus router it is important to have backup gsm connection, but more important is to have no interruption with connection to servers that are in LAN.

It does not disrupt the LAN Connections

 

[Ranger802004]

***v2.0.4 has been published to production update channel***

v2.0.4 - 06/01/2023
Enhancements:
- Added 3rd DNS Server from Automatic Settings to be factored into WAN Failover events.
- The checkiprules function will now be checked at the beginning of WAN Status checks to ensure NAT rules are created if necessary prior to performing packet loss checks.
- Added 386.10 and 386.11 to supported firmware list
- Removed 386.5 and 386.7 from supported firmware list.

Fixes:
- Corrected issue during uninstall when logic was reversed for retaining configuration file or to delete.

 

[ColinJOnes]

Hi, I have tried to get your script to work on my XT12 router and not having much luck.

when I enable the Debug logging in the Router Admin page I then see constant mentions of the following

wan-failover: Debug - failed to set WAN0USBMODEMREADY
I'm wondering if this is because this Router doesn't have a USB port?

Also when I run the script through AMTM and try and view the Status nothing happens and I get the following in the log file

wan-failover: wan-failover is up to date - Version: v2.0.4

If I choose to restart WAN Failover the following is in the log

Jun 3 20:05:45 wan-failover: Restart - Restarting wan-failover ***This can take up to approximately 1 minute***
Jun 3 20:05:45 wan-failover: Restart - Killing wan-failover Process ID: 23444
Jun 3 20:05:45 wan-failover: Restart - Killed wan-failover Process ID: 23444
Jun 3 20:05:45 wan-failover: Restart - Killing wan-failover Process ID: 23445
Jun 3 20:05:45 wan-failover: Restart - Killed wan-failover Process ID: 23445
Jun 3 20:05:45 wan-failover: Cleanup - Deleting IP Rule for 8.8.8.8 to monitor wan0
Jun 3 20:05:45 wan-failover: Cleanup - Deleted IP Rule for 8.8.8.8 to monitor wan0
Jun 3 20:05:46 wan-failover: Cleanup - Deleting IP Rule for 8.8.4.4 to monitor wan1
Jun 3 20:05:46 wan-failover: Cleanup - Deleted IP Rule for 8.8.4.4 to monitor wan1
Jun 3 20:05:46 wan-failover: Cleanup - Deleting /var/lock/wan-failover.lock
Jun 3 20:05:46 wan-failover: Cleanup - Deleted /var/lock/wan-failover.lock
Jun 3 20:05:46 wan-failover: Cleanup - Deleting /var/run/wan-failover.pid
Jun 3 20:05:46 wan-failover: Cleanup - Deleted /var/run/wan-failover.pid
Jun 3 20:05:46 wan-failover: Cleanup - Deleting /tmp/wan0packetloss.tmp
Jun 3 20:05:46 wan-failover: Cleanup - Deleted /tmp/wan0packetloss.tmp
Jun 3 20:05:46 wan-failover: Cleanup - Deleting /tmp/wan1packetloss.tmp
Jun 3 20:05:46 wan-failover: Cleanup - Deleted /tmp/wan1packetloss.tmp
Jun 3 20:05:46 wan-failover: Restart - Waiting for wan-failover to restart from Cron Job
Jun 3 20:06:01 wan-failover: Restart - Successfully Restarted wan-failover Process ID(s): 31181 31187
Jun 3 20:06:03 wan-failover: System Check - Process ID: 31187
Jun 3 20:06:03 wan-failover: System Check - Version: v2.0.4
Jun 3 20:06:03 wan-failover: System Check - Checksum: 663eb976dc5bbde96b1c243234377929dcaa768d63799e8c7c9520fb0e825906
Jun 3 20:06:03 wan-failover: System Check - IP Version: 5.11.0
Jun 3 20:06:03 wan-failover: wan-failover is up to date - Version: v2.0.4
Jun 3 20:06:03 wan-failover: System Check - Process Priority: 0
Jun 3 20:06:11 wan-failover: WAN Status - wan0 enabled
Jun 3 20:06:14 wan-failover: WAN Status - Adding IP Rule for 8.8.8.8 to monitor wan0
Jun 3 20:06:14 wan-failover: WAN Status - Added IP Rule for 8.8.8.8 to monitor wan0
Jun 3 20:06:16 wan-failover: WAN Status - wan0 has 0% packet loss
Jun 3 20:06:16 wan-failover: WAN Status - wan0 has a 11ms ping time
Jun 3 20:06:17 wan-failover: WAN Status - wan1 enabled
Jun 3 20:06:20 wan-failover: WAN Status - Adding IP Rule for 8.8.4.4 to monitor wan1
Jun 3 20:06:20 wan-failover: WAN Status - Added IP Rule for 8.8.4.4 to monitor wan1
Jun 3 20:06:22 wan-failover: WAN Status - wan1 has 0% packet loss
Jun 3 20:06:22 wan-failover: WAN Status - wan1 has a 6ms ping time
Jun 3 20:06:30 wan-failover: Check IP Rules - Adding IPTables - OUTPUT MANGLE match rule for eth1 marked with 0x90000000
Jun 3 20:06:30 wan-failover: Check IP Rules - Added IPTables - OUTPUT MANGLE match rule for eth1 marked with 0x90000000


Any help would be appreciated.

Regards,
Colin

 

[Ranger802004]

Hi, I have tried to get your script to work on my XT12 router and not having much luck.

when I enable the Debug logging in the Router Admin page I then see constant mentions of the following

wan-failover: Debug - failed to set WAN0USBMODEMREADY
I'm wondering if this is because this Router doesn't have a USB port?

Also when I run the script through AMTM and try and view the Status nothing happens and I get the following in the log file

wan-failover: wan-failover is up to date - Version: v2.0.4

If I choose to restart WAN Failover the following is in the log

Jun 3 20:05:45 wan-failover: Restart - Restarting wan-failover ***This can take up to approximately 1 minute***
Jun 3 20:05:45 wan-failover: Restart - Killing wan-failover Process ID: 23444
Jun 3 20:05:45 wan-failover: Restart - Killed wan-failover Process ID: 23444
Jun 3 20:05:45 wan-failover: Restart - Killing wan-failover Process ID: 23445
Jun 3 20:05:45 wan-failover: Restart - Killed wan-failover Process ID: 23445
Jun 3 20:05:45 wan-failover: Cleanup - Deleting IP Rule for 8.8.8.8 to monitor wan0
Jun 3 20:05:45 wan-failover: Cleanup - Deleted IP Rule for 8.8.8.8 to monitor wan0
Jun 3 20:05:46 wan-failover: Cleanup - Deleting IP Rule for 8.8.4.4 to monitor wan1
Jun 3 20:05:46 wan-failover: Cleanup - Deleted IP Rule for 8.8.4.4 to monitor wan1
Jun 3 20:05:46 wan-failover: Cleanup - Deleting /var/lock/wan-failover.lock
Jun 3 20:05:46 wan-failover: Cleanup - Deleted /var/lock/wan-failover.lock
Jun 3 20:05:46 wan-failover: Cleanup - Deleting /var/run/wan-failover.pid
Jun 3 20:05:46 wan-failover: Cleanup - Deleted /var/run/wan-failover.pid
Jun 3 20:05:46 wan-failover: Cleanup - Deleting /tmp/wan0packetloss.tmp
Jun 3 20:05:46 wan-failover: Cleanup - Deleted /tmp/wan0packetloss.tmp
Jun 3 20:05:46 wan-failover: Cleanup - Deleting /tmp/wan1packetloss.tmp
Jun 3 20:05:46 wan-failover: Cleanup - Deleted /tmp/wan1packetloss.tmp
Jun 3 20:05:46 wan-failover: Restart - Waiting for wan-failover to restart from Cron Job
Jun 3 20:06:01 wan-failover: Restart - Successfully Restarted wan-failover Process ID(s): 31181 31187
Jun 3 20:06:03 wan-failover: System Check - Process ID: 31187
Jun 3 20:06:03 wan-failover: System Check - Version: v2.0.4
Jun 3 20:06:03 wan-failover: System Check - Checksum: 663eb976dc5bbde96b1c243234377929dcaa768d63799e8c7c9520fb0e825906
Jun 3 20:06:03 wan-failover: System Check - IP Version: 5.11.0
Jun 3 20:06:03 wan-failover: wan-failover is up to date - Version: v2.0.4
Jun 3 20:06:03 wan-failover: System Check - Process Priority: 0
Jun 3 20:06:11 wan-failover: WAN Status - wan0 enabled
Jun 3 20:06:14 wan-failover: WAN Status - Adding IP Rule for 8.8.8.8 to monitor wan0
Jun 3 20:06:14 wan-failover: WAN Status - Added IP Rule for 8.8.8.8 to monitor wan0
Jun 3 20:06:16 wan-failover: WAN Status - wan0 has 0% packet loss
Jun 3 20:06:16 wan-failover: WAN Status - wan0 has a 11ms ping time
Jun 3 20:06:17 wan-failover: WAN Status - wan1 enabled
Jun 3 20:06:20 wan-failover: WAN Status - Adding IP Rule for 8.8.4.4 to monitor wan1
Jun 3 20:06:20 wan-failover: WAN Status - Added IP Rule for 8.8.4.4 to monitor wan1
Jun 3 20:06:22 wan-failover: WAN Status - wan1 has 0% packet loss
Jun 3 20:06:22 wan-failover: WAN Status - wan1 has a 6ms ping time
Jun 3 20:06:30 wan-failover: Check IP Rules - Adding IPTables - OUTPUT MANGLE match rule for eth1 marked with 0x90000000
Jun 3 20:06:30 wan-failover: Check IP Rules - Added IPTables - OUTPUT MANGLE match rule for eth1 marked with 0x90000000


Any help would be appreciated.

Regards,
Colin

Would you mind DMing me an output of your nvram? That may be the case and I need to verify, this can be easily fixed just need a little bit of info, thanks.

 

[Ranger802004]

Would you mind DMing me an output of your nvram? That may be the case and I need to verify, this can be easily fixed just need a little bit of info, thanks.

Disregard, I figured out the issue and released a beta release for you, go ahead and test v2.0.5-beta1 and let me know your results. Make sure WAN Failover is set to Dev Mode so it can access the Beta update channel.

v2.0.5-beta1 - 06/04/2023
Fixes:
- Corrected minor issue when retrieving WAN NVRAM Parameters
- Corrected issue if WAN Failover would be stuck in a continuous loop if a router didn't have WAN USB capability.

 

[Aiadi]

Disregard, I figured out the issue and released a beta release for you, go ahead and test v2.0.5-beta1 and let me know your results. Make sure WAN Failover is set to Dev Mode so it can access the Beta update channel.

v2.0.5-beta1 - 06/04/2023
Fixes:
- Corrected minor issue when retrieving WAN NVRAM Parameters
- Corrected issue if WAN Failover would be stuck in a continuous loop if a router didn't have WAN USB capability.

Would this possibly be a similar issue to why I have never been able to get the script working on my GT-AX6000? Is it anything to do with the fact that the GT-AX6000 does not use JFFS2, but uses UBIFS instead?

 

[Ranger802004]

Would this possibly be a similar issue to why I have never been able to get the script working on my GT-AX6000? Is it anything to do with the fact that the GT-AX6000 does not use JFFS2, but uses UBIFS instead?

That is a very highly likely scenario. Does the /jffs/scripts folder exist on your router?

 

[ColinJOnes]

Disregard, I figured out the issue and released a beta release for you, go ahead and test v2.0.5-beta1 and let me know your results. Make sure WAN Failover is set to Dev Mode so it can access the Beta update channel.

v2.0.5-beta1 - 06/04/2023
Fixes:
- Corrected minor issue when retrieving WAN NVRAM Parameters
- Corrected issue if WAN Failover would be stuck in a continuous loop if a router didn't have WAN USB capability.

Thank you for the speedy reply. I have installed the new beta build and it’s running now but I do have a couple of observations.

I have my dual wan configured in Load Balance Mode as I want to be able to choose which of my 2 links different devices use based on Routing Rules.

If I disconnect the WAN1 internet by unplugging the feed which goes into the Modem and leave a Network cable connected to the Asus Router (XT12) I notice the Status of WAN Failover changes as follows as It looks like its restarting:
Not Running
Initializing
Failover Monitoring

Once this happens devices that are configured via Routing Rule to use WAN1 failover to WAN0 as expected.

When I reconnect the internet feed the Status goes through the same Not Running, Initializing and Failover Monitoring stages but once again it seems to work as the devices revert back to WAN1 as desired which is great.

So my question is, should WAN Failover restart when status changes are detected or is this a bug?

 

[Ranger802004]

Thank you for the speedy reply. I have installed the new beta build and it’s running now but I do have a couple of observations.

I have my dual wan configured in Load Balance Mode as I want to be able to choose which of my 2 links different devices use based on Routing Rules.

If I disconnect the WAN1 internet by unplugging the feed which goes into the Modem and leave a Network cable connected to the Asus Router (XT12) I notice the Status of WAN Failover changes as follows as It looks like its restarting:
Not Running
Initializing
Failover Monitoring

Once this happens devices that are configured via Routing Rule to use WAN1 failover to WAN0 as expected.

When I reconnect the internet feed the Status goes through the same Not Running, Initializing and Failover Monitoring stages but once again it seems to work as the devices revert back to WAN1 as desired which is great.

So my question is, should WAN Failover restart when status changes are detected or is this a bug?

Hmmm interesting, sounds like a bug but debug logs would confirm that.

 

[Ranger802004]

Hmmm interesting, sounds like a bug but debug logs would confirm that.

Disregard, I went bug hunting this morning and figured out what is causing this problem. It's not a visual bug, it's a syntax issue that only effects Load Balance mode that causes WAN failover to close but relaunch from cron job, I will be releasing a patch shortly to resolve this problem.