VPNMON VPNMON-R3 v1.4.1 -Jul 2, 2025- Monitor WAN/Dual-WAN/OpenVPN Health & Reset Multiple OpenVPN Connections (Now available in AMTM!) Wireguard Alpha!

[Viktor Jaep]

I think the ping method is fine for most cases. Besides, regardless how you force data over the tunnel you will face issues anyway.
Other issues are with site2site (limited AllowedIPs) peer or when ping target are also used for dns which means It may get its own route to WAN which means you may not get the result you want.

The only thing the ping -I does is that the ping packet get the stated source address or interface so you need to make sure this packet gets properly routed to the interface as @SomeWhereOverTheRainBow showed.

Example on both these workaround are in my watchdog script: https://github.com/ZebMcKayhan/Asus-merlin-Wireguard-Watchdog

IF_IP=$(nvram get "$IF"_addr | cut -d '/' -f1)
ip rule add from $IF_IP lookup $IF prio 10

...

ip rule del prio 10

Ahhh OK, I was wondering why you were making things complicated with these ip rules! Thanks!

 

[Viktor Jaep]

@Viktor Jaep glad to hear your OCD is healthy and happy - I think you know we share a common bond there!

Based on some extra emails I'm getting from wan-failover (since re-installing vpnmon-r3) on a reboot, where it senses WAN0 is disconnected and then reconnects shortly after, I think there may be some kind of "tussle" going on but it's maybe a startup timing issue between the two scripts?

I might try playing with the respective delays of starting up VPNMON-R3 and WAN-FAILOVER and see if I can make it play nice, or do you have any other thoughts?
Your script doesn't restart the WAN interface does it? Trying to work out which should "settle" first ...

I have your "Provide additional WAN/Dual WAN monitoring" option enabled but what exactly does that do? Could that be playing into it?

Cheers and hope you are well!

StephenH

VPNMON-R3 just sits in the background and keeps an eye on the WAN itself. It doesn't restart anything... it just waits for the WAN to come back up so that it can re-establish the vpn connections. Even if timing doesn't work, VPNMON would just check again at the end of it's 5min cycle, and see if it's safe to resume. It shouldn't interfere with anything dealing with the WAN.

The "Provide additional WAN..." option just enables this functionality of showing the WAN interfaces in the UI, and provides for monitoring and falls-back when it goes out. If it's not on, VPNMON will just constantly keep retrying connecting the vpn connections.

Thanks for testing!!

 

[CaptainSTX]

So that's a problem I'm still trying to work out. With OVPN, VPNMON actually starts those up, so I can get an accurate start time. WG, on the other hand, starts when the router reboots. The only time you get a more accurate start time is if you reset the WG connection within VPNMON, then I can start its own timer.

OK. Thanks for the update. Minor issue for me really. WG connections seem to be more stable than OpenVPN client which seems to need restarting every two - three days when it exceeds a PING of 500 ms. Just handy to see that both the open and WG clients are running when you open VPMON.