VPNMON VPNMON-R3 v1.8.2 -Nov 23, 2025- Monitor OpenVPN/Wireguard WAN/Dual-WAN Health & Random Reset Multiple Connections (Available in AMTM!) - v1.8.3Beta6

[Viktor Jaep]

One final beta of VPNMON-R3 1.8.3b3 before the end of the year... mostly addressing timer tracking, which has been bugging me for a while now. This should hopefully provide some more Tx/Rx accuracy if you venture off the main UI into the config menus, and then come back.

What's new?
- PATCH: Improved the tracking of the timer, plus any time spent in other menus outside of the regular timer, to provide a more accurate view of the Tx/Rx stats.

Download link:

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R3/develop/vpnmon-r3.sh" -o "/jffs/scripts/vpnmon-r3.sh" && chmod 755 "/jffs/scripts/vpnmon-r3.sh"

Significant Screenshots:
None today!

 

[Ripshod]

One final beta of VPNMON-R3 1.8.3b3 before the end of the year... mostly addressing timer tracking, which has been bugging me for a while now. This should hopefully provide some more Tx/Rx accuracy if you venture off the main UI into the config menus, and then come back.

What's new?
- PATCH: Improved the tracking of the timer, plus any time spent in other menus outside of the regular timer, to provide a more accurate view of the Tx/Rx stats.

Download link:

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R3/develop/vpnmon-r3.sh" -o "/jffs/scripts/vpnmon-r3.sh" && chmod 755 "/jffs/scripts/vpnmon-r3.sh

Significant Screenshots:
None today!

You missed a " at the end

 

[Viktor Jaep]

You missed a " at the end

LOL thank you!

 

[ComputerSteve]

@Viktor Jaep I love this add-on & thanks for all the work on it !!.. However I'm having a problem with something - I am doing a two type vpn thing meaning I have 2 servers running on my home router and then on my remote router I'm connecting to these two servers. The issue I'm having is one of my servers isn't showing a public IP or it says unknown but it connects and is working.. Your add-on seems to get stuck meaning the add-on just stops doing anything in SSH I can't even press C to show configuration -- eventually I see retry or something -- is there a way you can have an option to ignore the public IP -- I'm just using your add-on to reconnect the server with port UDP 1194 if the vpn ever stops.

 

[Viktor Jaep]

@Viktor Jaep I love this add-on & thanks for all the work on it !!.. However I'm having a problem with something - I am doing a two type vpn thing meaning I have 2 servers running on my home router and then on my remote router I'm connecting to these two servers. The issue I'm having is one of my servers isn't showing a public IP or it says unknown but it connects and is working.. Your add-on seems to get stuck meaning the add-on just stops doing anything in SSH I can't even press C to show configuration -- eventually I see retry or something -- is there a way you can have an option to ignore the public IP -- I'm just using your add-on to reconnect the server with port UDP 1194 if the vpn ever stops.

Could you show me where things get stuck in VPNMON? Could you send a screenshot of that please? I'll see what can be done...

Another troubleshooting step... try "unmonitoring" that particular troublesome VPN slot in VPNMON. Make sure the green X is not active.

 

[ComputerSteve]

Could you show me where things get stuck in VPNMON? Could you send a screenshot of that please? I'll see what can be done...

Another troubleshooting step... try "unmonitoring" that particular troublesome VPN slot in VPNMON. Make sure the green X is not active.

I have sent you a direct message !

 

[Viktor Jaep]

So it looks like @ComputerSteve was able to come up with a workaround for anyone else using this particular DDNS setup that he's using through freemyip.com. Apparently each VPN connection points to the same host, but uses different ports, and believe that one or more tunnels somehow get bonded, preventing one or more of them from being able to pass traffic, or report on a public WAN IP. Looks like this keeps VPNMON fully functional, and is somehow able to get the problem tunnel to report a legit WAN IP.

Here's his fix:

Add this to your firewall-startfile (using the correct 10.x network for your problem tunnel):

# NAT OpenVPN Server 1 subnet (dual-WAN safe)
iptables -t nat -C POSTROUTING -s 10.20.0.0/24 -j MASQUERADE 2>/dev/null \
|| iptables -t nat -A POSTROUTING -s 10.20.0.0/24 -j MASQUERADE

 

[Viktor Jaep]

Beta 4 is out based on a small improvement brought up by @ComputerSteve's issue he was experiencing today. Let's see if this helps improve performance on those occasions the tunnel experiences connectivity issues!

What's new?
- PATCH: Based on some feedback that @ComputerSteve was experiencing, I've optimized both the VPN and WG connectivity tests to fail the curl test if the ping test fails. It seems the ping test will fail pretty quickly, while the curl test could hang in there for quite some time before indicating a fail. This should help resolve some of the sluggishness you would see if any of your tunnels are misbehaving.

Download link:

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R3/develop/vpnmon-r3.sh" -o "/jffs/scripts/vpnmon-r3.sh" && chmod 755 "/jffs/scripts/vpnmon-r3.sh"

Significant Screenshots:
None today!

 

[Viktor Jaep]

Skipping beta 5 right to v1.8.3 beta 6... added capabilities for a secondary PING host to cut down on resets and provide some more redundancy should one DNS have an issue pinging.

What's new!?
- PATCH: Built in the capability to now use redundant Pinghosts under the configuration menu, using option #2 "Custom Ping Hosts for Connectivity Checks". By default, Pinghost 1 uses 8.8.8.8 and Pinghost 2 uses 1.1.1.1. Pinging these hosts through the VPN/WG tunnel is used to determine if the tunnel is healthy. This now also provides some redundancy, should Pinghost 1 not respond, but Pinghost 2 does, then the tunnel will not get reset, and should help with those dealing with more frequent resets.

Download Link:

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R3/develop/vpnmon-r3.sh" -o "/jffs/scripts/vpnmon-r3.sh" && chmod 755 "/jffs/scripts/vpnmon-r3.sh"

Significant Screenshots:

Showing Primary and Secondary PING hosts:

 

[scootertramp]

Skipping beta 5 right to v1.8.3 beta 6... added capabilities for a secondary PING host to cut down on resets and provide some more redundancy should one DNS have an issue pinging.

What's new!?
- PATCH: Built in the capability to now use redundant Pinghosts under the configuration menu, using option #2 "Custom Ping Hosts for Connectivity Checks". By default, Pinghost 1 uses 8.8.8.8 and Pinghost 2 uses 1.1.1.1. Pinging these hosts through the VPN/WG tunnel is used to determine if the tunnel is healthy. This now also provides some redundancy, should Pinghost 1 not respond, but Pinghost 2 does, then the tunnel will not get reset, and should help with those dealing with more frequent resets.

Download Link:

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R3/develop/vpnmon-r3.sh" -o "/jffs/scripts/vpnmon-r3.sh" && chmod 755 "/jffs/scripts/vpnmon-r3.sh"

Significant Screenshots:

Showing Primary and Secondary PING hosts:
View attachment 69925

Woo Hoo..

Got a question. Wondering why I seem to be seeing only 1 connection attempt?
Here are the log entries from the last two incidents.

Jan 06 2026 10:25:40 rt-be88u VPNMON-R3[1354] - WARNING: VPN2 received invalid PING information. Contents: Null
743 Jan 06 2026 10:48:10 rt-be88u VPNMON-R3[1354] - WARNING: VPN2 failed to respond
744 Jan 06 2026 10:48:10 rt-be88u VPNMON-R3[1354] - WARNING: VPN2 attempt 1 of 4 to allow connection to recover
745 Jan 06 2026 10:52:10 rt-be88u VPNMON-R3[1354] - WARNING: VPN2 is in an error state and being reconnected
746 Jan 06 2026 10:52:26 rt-be88u VPNMON-R3[1354] - INFO: VPN2 Connection Restarted [SEQ] - New Server: yyy.yyy.yyy.yyy
747 Jan 06 2026 10:52:42 rt-be88u VPNMON-R3[1354] - INFO: Email notification was sent successfully [FAILURE: VPN Slot 2 in Error State]
748 Jan 06 2026 10:52:47 rt-be88u VPNMON-R3[1354] - INFO: VPN Director Routing Service Restarted
749 Jan 06 2026 10:52:53 rt-be88u VPNMON-R3[1354] - INFO: spdMerlin Interfaces Reset

Jan 12 2026 10:19:35 rt-be88u VPNMON-R3[1354] - WARNING: VPN1 failed to respond
792 Jan 12 2026 10:19:35 rt-be88u VPNMON-R3[1354] - WARNING: VPN1 attempt 1 of 4 to allow connection to recover
793 Jan 12 2026 10:23:34 rt-be88u VPNMON-R3[1354] - WARNING: VPN1 is in an error state and being reconnected
794 Jan 12 2026 10:23:50 rt-be88u VPNMON-R3[1354] - INFO: VPN1 Connection Restarted [SEQ] - New Server: xxx.xxx.xxx.xxx
795 Jan 12 2026 10:24:06 rt-be88u VPNMON-R3[1354] - INFO: Email notification was sent successfully [FAILURE: VPN Slot 1 in Error State]
796 Jan 12 2026 10:24:11 rt-be88u VPNMON-R3[1354] - INFO: VPN Director Routing Service Restarted
797 Jan 12 2026 10:24:17 rt-be88u VPNMON-R3[1354] - INFO: spdMerlin Interfaces Reset