WANFailover What advantages does this script offer over existing features?

[MarcoPolo]

Hello,

Sorry for this probably silly question, but what advantages does this script offer over existing features?

 

[Viktor Jaep]

Sorry for this probably silly question, but what advantages does this script offer over existing features?

It makes the built-in WAN failover functionality actually work, and gives you a lot more control.

 

[Tech9]

The most common issue with built-in dual WAN in Asuswrt is unreliable fail back/over up to the point it requires physical disconnection of Ethernet cables to WAN ports. Some folks report it works better with Ethernet + USB compared to Ethernet + Ethernet. Some folks report it works well for their use case and with their specific equipment. Perhaps the issue is hardware compatibility related as well.

 

[MarcoPolo]

I solved this problem with these commands:

cru a restart_wan1 “0 */6 * * * service ‘restart_wan_if 1’”
service “restart_wan_if 1”

in file /jffs/scripts/services-start.
(for the configuration shown in the screenshot in the 1st post)

The aim is to set the state to 2 for all Wan interfaces (which can be checked with this command):

nvram show | grep wan[0,1,2,3,4]_state_t

I don't know if what I've done represents a problem, but in any case the native failover works without a hitch with this.

(AX88U / 3004.388.8_4)

 

[visortgw]

I solved this problem with these commands:

cru a restart_wan1 “0 */6 * * * service ‘restart_wan_if 1’”
service “restart_wan_if 1”

in file /jffs/scripts/services-start.
(for the configuration shown in the screenshot in the 1st post)

The aim is to set the state to 2 for all Wan interfaces with this command:

nvram show | grep wan[0,1,2,3,4]_state_t

I don't know if what I've done represents a problem, but in any case the native failover works without a hitch with this.

(AX88U / 3004.388.8_4)

Try nvram show | grep wan | grep _state_t as a single command to view state for all WAN interfaces.