Wireguard not switching from WAN2 back to WAN1

[cyrus104]

I have WAN1 connected to my ISP which sometimes goes down for a minute or two. I have WAN2 connected to an LTE Modem so one is igb0 and the other is ibg1.

WAN1 latency is around 90ms, WAN2 is around 170ms.

I have 2 VPNs setup, one is OpenVPN and the other is Wireguard, they are used to support different services.

When I have a failure, I can see that both VPNs route through WAN2 and their latency jumps up. A few minutes after WAN1 comes back up the OpenVPN VPN will switch back to WAN1 and you can see the latency creep down. However, the Wireguard VPN never switches back and the latency stays high and I can see the traffic on my LTE modem.

I wanted to check if there is a setting that I'm missing or a way to force it to restart the connection, I know Wireguard isn't an always on type of connection but not sure what is happening there.

I'm not skilled with Monit but I guess I could use something like that to restart the service if the latency of the OpenVPN and Wireguard aren't close but I would like to see if there is a setting in the configs that I'm missing.

Thanks

[cyrus104]

Any thoughts on this? it looks like there was a similar post as well but the solution was using an external VM.

Because I'm using the kernel wireguard, I can't use the dashboard service start/stop button. If I disable wireguard and start it in the VPN/Wireguard menu Wireguard automatically picks the current WAN to route of which is generally WAN1 when I'm looking at it.

[palillo]

Hi,

Don't know if this could help, but go to System->Settings->General and go to the botton and enable the option "Gateway Switching" which says:

Allow default gateway switching
If the link where the default gateway resides fails switch the default gateway to another available one.

Regards.