WANFailover Dual WAN Failover ***v2 Release***

[Ranger802004]

Lower values = higher priority. Increase the value to lower the priority.

 

[nunu]

thanks ...
i had miss understood what you told me.

i made the priority modification (i set 11000 to LB priority) and get:

but it seems (after the reboot), that rules prio 150 are still set.

i need to manually delete 150 prio rules, and have access to 192.168.1.x.

regards

 

[Ranger802004]

thanks ...
i had miss understood what you told me.

i made the priority modification (i set 11000 to LB priority) and get:

View attachment 54841

but it seems (after the reboot), that rules prio 150 are still set.

i need to manually delete 150 prio rules, and have access to 192.168.1.x.

regards

Yea these are being created by the firmware, I'll have to add in logic to remove them properly (if non-default is configured) in a patch. In the meantime you can add the commands to your wan-event script to delete them as a workaround in the mean time.

 

[nunu]

thanks.
this morning (the router reboot at 3am),
access to 192.168.1.x worls even with fwmark at 150 ...

0: from all lookup local
100: from all to 8.8.8.8 iif lo oif eth0 lookup wan0
100: from all to 8.8.4.4 iif lo oif eth4 lookup wan1
100: from all to 82.67.33.113 lookup wan0
100: from all to 102.129.143.31 lookup wan0
100: from all to 89.149.22.75 lookup wan0
100: from all to 89.149.22.56 lookup wan0
100: from all to 89.149.22.39 lookup wan0
100: from all to 89.149.22.10 lookup wan0
150: from all fwmark 0x80000000/0xf0000000 lookup wan0
150: from all fwmark 0x90000000/0xf0000000 lookup wan1
200: from 192.168.3.2 lookup wan0
200: from 192.168.2.2 lookup wan1
200: from 9.9.9.11 lookup wan0
200: from 149.112.112.11 lookup wan0
200: from 9.9.9.11 lookup wan1
200: from 149.112.112.11 lookup wan1
200: from all to 82.67.33.113 lookup wan1
200: from all to 84.17.52.2 lookup wan1
200: from all to 102.129.143.36 lookup wan1
200: from all to 102.129.143.34 lookup wan1
200: from all to 84.17.52.35 lookup wan1
200: from all to 89.149.22.72 lookup wan1
200: from all to 89.149.22.34 lookup wan1
200: from all to 102.129.143.32 lookup wan1
400: from all to 192.168.3.1 lookup wan0
400: from all to 192.168.2.1 lookup wan1
400: from all to 9.9.9.11 lookup wan0
400: from all to 149.112.112.11 lookup wan0
400: from all to 9.9.9.11 lookup wan1
400: from all to 149.112.112.11 lookup wan1
10210: from all to 192.168.1.0/24 lookup ovpnc1
10410: from 192.168.10.162 lookup ovpnc2
11000: from all fwmark 0x90000000/0xf0000000 lookup wan1
11000: from all fwmark 0x80000000/0xf0000000 lookup wan0
32766: from all lookup main
32767: from all lookup default

i do not understand why ip table is different from one in my post from Yesterday at 9:57 PM...
btw, i will remove wan-event script to customize the ip table i will remove fwmark 150 prio from wan-event script

regards

 

[Ranger802004]

thanks.
this morning (the router reboot at 3am),
access to 192.168.1.x worls even with fwmark at 150 ...



i do not understand why ip table is different from one in my post from Yesterday at 9:57 PM...
btw, i will remove wan-event script to customize the ip table.

regards

Deleting wan-event script will prevent your WAN Failover from launching on boot up.

 

[nunu]

oups,

i make a mistake ... i meant : "i will delete fwmark prio 150 in wan-event script ..."

.....

 

[nunu]

Hi,

i'am close to what i want...

I guess the last point: the fallback of vpn connections.

So here the case (dual wan):
- WAN0 is the main one
- 3 ovpn connections established through WAN0 - traffic goes through
- WAN 1 OK

the WAN0 is cut => all cnx switch to WAN1, OVPN cnx are OK - traffic goes through

the WAN0 goes up => devices on networks go through WAN0, VPN connections seem to be stay established on WAN1, and no traffic go through (i guess, as WAN1 is OK, no need to reestablished cnx).

If i power off / on ovpn connexions, then there are all through WAN0, and traffic goes through.

My question, is there a way to force ovpn to reconnect through WAN0 on fallback ?

regards

 

[Ranger802004]

Hi,

i'am close to what i want...

I guess the last point: the fallback of vpn connections.

So here the case (dual wan):
- WAN0 is the main one
- 3 ovpn connections established through WAN0 - traffic goes through
- WAN 1 OK

the WAN0 is cut => all cnx switch to WAN1, OVPN cnx are OK - traffic goes through

the WAN0 goes up => devices on networks go through WAN0, VPN connections seem to be stay established on WAN1, and no traffic go through (i guess, as WAN1 is OK, no need to reestablished cnx).

If i power off / on ovpn connexions, then there are all through WAN0, and traffic goes through.

My question, is there a way to force ovpn to reconnect through WAN0 on fallback ?

regards

Yes, I will have a fix for this in the next patch. I am aware of the issue.

 

[nunu]

Great !!

i have checked the readme, but don't see information: on which event wan-event script is called ?

One dirty patch (very hugly dirty patch), will be to reboot the router when WAN0 goes from Fail to UP. (I don't need fast switch).

 

[Jannik]

Hi, thank you for the script. I have a question regarding how to configure it correctly matching my connections:

WAN0: DSL 100/40
Great ping (below 10)

WAN1: Cable 1000/50
Average Ping (20-25)

Question: Can I somehow use the script to set routing roules based just on the source? Then I would set my gaming-pc to WAN0 and my downloader/NAS to WAN1.

With the default asus roules which require also destination IPs its not working so well

 

[Ranger802004]

Great !!

i have checked the readme, but don't see information: on which event wan-event script is called ?

One dirty patch (very hugly dirty patch), will be to reboot the router when WAN0 goes from Fail to UP. (I don't need fast switch).

wan-event is called, that's the name.

 

[Ranger802004]

Having issues with wan-failover (2.1.0) on a new GT-AX6000 router with the latest merlin firmware (388.5). No issues installing it, but CPU usage is spiking and I can't get the wan-failover status page to show. It just hangs when I select 1 to show status.

I turned on debug logging and the same entry keeps repeating "wan-failover: Debug - failed to set WAN1GWIFNAME". I checked and this value is set to 'usb0'. I've also tried with NVRAM check both enabled and disabled, no change.

Looking for suggestions on what I need to change to get it working.

EDIT(12/9): I resolved the issue and it's working now. I terminated wan-failover, then manually disconnected the primary wan, so the ASUS router routine switched to the secondary. This populated all the NVRAM settings and when I restarted wan-failover it worked.

Do you have all of the proper factory settings disabled as required? The router should boot up with WAN1 as the primary allowing these values to be populated, only the factory failover will automatically switch it to WAN0.

 

[Ranger802004]

Hi, thank you for the script. I have a question regarding how to configure it correctly matching my connections:

WAN0: DSL 100/40
Great ping (below 10)

WAN1: Cable 1000/50
Average Ping (20-25)

Question: Can I somehow use the script to set routing roules based just on the source? Then I would set my gaming-pc to WAN0 and my downloader/NAS to WAN1.

With the default asus roules which require also destination IPs its not working so well

I don't have a source based solution for this but you can use my Domain VPN Routing script to achieve similar results on destination based routing via Domains. It allows you to configure rules for specifically for WAN0 / WAN1 / VPN Clients.

 

[Ranger802004]

***v2.1.1-beta1 Released***
Release Notes:
Enhancements:
- Added 388.5 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.

 

[livefeed]

I would like to try this beta (2.1.1) as I am having a few issue after the latest merlin update. What is the command to update to a beta?

 

[Ranger802004]

I would like to try this beta (2.1.1) as I am having a few issue after the latest merlin update. What is the command to update to a beta?

Enable Dev Mode and perform an update.

 

[nunu]

Hi,

i'am testing some failure cases.
I would like to know, if in case of 100% packet lost on a WAN, it is normal that WAN stays in "connected" status and wan-event script is not called - to simulate this case, i unplug the SIM card from my 4G router connected to port WAN of my asus router.

By disconnecting the cable, status is "disconnected" and wan-event script called (as expected)

regards

 

[Ranger802004]

Hi,

i'am testing some failure cases.
I would like to know, if in case of 100% packet lost on a WAN, it is normal that WAN stays in "connected" status and wan-event script is not called - to simulate this case, i unplug the SIM card from my 4G router connected to port WAN of my asus router.

By disconnecting the cable, status is "disconnected" and wan-event script called (as expected)

regards

For any kind of "testing" or validation I would need you to turn on debug logging and collect logs for me to see the exact behavior of what is occurring.

 

[nunu]

hi,
i have activated "debug" logs, and i see:
an-failover: Debug - WAN0 Status: DISCONNECTED
but in WAN failover Status, it is still connected:

wan-event still not called.

 

[Ranger802004]

hi,
i have activated "debug" logs, and i see:
an-failover: Debug - WAN0 Status: DISCONNECTED
but in WAN failover Status, it is still connected:

View attachment 55181

wan-event still not called.

Did your wan-event script already exist prior to install? Are the permissions set correct? Are there other things in there being called?