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

[SomeWhereOverTheRainBow]

You mean the API? Yeah I'm pretty bummed about it too. Right now, I'm just using 4 WG servers in a slot to get by.

and right now he says-- "I'm just using 4 WG servers in a slot to get by." Only 4?

 

[Viktor Jaep]

I can hear a quiet roar in the crowd slowly getting louder and louder----Jaep Jaep Jaep! Don't let a little stage fright keep you from demonstrating your best works! keep it up!

Thanks for the vote of confidence @SomeWhereOverTheRainBow!!

 

[Viktor Jaep]

and right now he says-- "I'm just using 4 WG servers in a slot to get by." Only 4?

It used to be lots more, sadly. But they shut down their API.

 

[SomeWhereOverTheRainBow]

Thanks for the vote of confidence @SomeWhereOverTheRainBow!!

Hey, we are all here, and we are cheering for you!

It used to be lots more, sadly. But they shut down their API.

Yea that blows. You were their number 1 customer. You would think with all your user base, they would have kept it going.

 

[Viktor Jaep]

Hey, we are all here, and we are cheering for you!

Yea that blows. You were their number 1 customer. You would think with all your user base, they would have kept it going.

"Security concerns" or something of the like was the excuse. I call it poor management and customer service. And lazy engineering for a problem that could easily be solved.

 

[New2This]

Lol. You succeeded.

You mean the API? Yeah I'm pretty bummed about it too. Right now, I'm just using 4 WG servers in a slot to get by.

Yes the Api for proton, I have a few months left for surshark-using them for now

 

[New2This]

@Viktor Jaep - Your Unbound config are you just using the default permission, as I see you have same router- was just thinking up'n the number of threads used for Unbound (instead of "1" )

 

[Viktor Jaep]

@Viktor Jaep - Your Unbound config are you just using the default permission, as I see you have same router- was just thinking up'n the number of threads used for Unbound (instead of "1" )

Just using the defaults. I've not had any performance issues that would require any tweaks. What are you seeing?

 

[New2This]

Just using the defaults. I've not had any performance issues that would require any tweaks. What are you seeing?C

Coming from a setup of a raspberry pihole-unbound which it was using the 4 cores - I was just wondering if it would make any difference with the unbound setup on the router- but I am noticing it does seem snappy on the router-quicker results
probably cause Im using just the large list on Diversion , compared to the pihole one..

 

[Stephen Harrington]

@Viktor Jaep any chance of an option to hide/ turn off displaying the entire OpenVPN monitoring section if one isn't using it please?
Guess you could also have the option to not display the Wireguard section as well for those so inclined?

StephenH

 

[Viktor Jaep]

@Viktor Jaep any chance of an option to hide/ turn off displaying the entire OpenVPN monitoring section if one isn't using it please?
Guess you could also have the option to not display the Wireguard section as well for those so inclined?

StephenH

I like that idea, @Stephen Harrington! Will make it so!

 

[Viktor Jaep]

New Beta 4 is out... incorporating this great idea that @Stephen Harrington came up with to allow you to enable/disable the view and monitoring of either the OVPN slots, or the WG slots, or both, or neither. Your choice! Enjoy!

What's new?
v1.5.05b - (TBA)
- PATCH: Added another option (#7) under the configuration menu that allows you to enable/disable the monitoring and view of either OVPN or WG slots on the main UI screen. This was inspired by none other than @Stephen Harrington, who does not want his screen cluttered up with slots that are not being used, and I can completely understand! Caveat: If you have tied unbound to one of your OVPN slots, you will not be able to disable the OVPN slot view and will be forced to monitor those slots.
- PATCH: After noticing some stuck processes around WG, some fixes went into place to help protect other 'nvram get' commands from getting stuck.

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:

Please let me know how it looks, @Stephen Harrington!

 

[Stephen Harrington]

enable/disable the monitoring and view of either OVPN or WG slots on the main UI screen

Works a treat, thank you @Viktor Jaep !

 

[salvo]

I've been testing the latest version with WG, and so far it's working well. However, I did encounter an issue that I couldn’t find similar here on the forum. After logging into the router and running screen, I found the following error:

wlcsm create nl socket:268: pid:1542 binding netlink socket error!!!

So I simply stopped the script and re-ran it using screen, and it continued without any issues. Could this behavior be related to my configuration? Has anyone else experienced something similar here? I assume script stops monitoring activity.

 

[Viktor Jaep]

I've been testing the latest version with WG, and so far it's working well. However, I did encounter an issue that I couldn’t find similar here on the forum. After logging into the router and running screen, I found the following error:

wlcsm create nl socket:268: pid:1542 binding netlink socket error!!!

So I simply stopped the script and re-ran it using screen, and it continued without any issues. Could this behavior be related to my configuration? Has anyone else experienced something similar here? I assume script stops monitoring activity.

View attachment 66920

View attachment 66921

View attachment 66922

Sadly, you're not the only one, @salvo. I was getting them as well. It's that age-old problem where doing simple "nvram get" lookups will result in a stuck process, causing errors like this.

Using @Martinski's CheckStuckProcCmds.sh utility over these last few days, I found the culprit:

Turns out I forgot to envelop that command with the 'timeout' command, which basically helps free it up if it does get stuck. In this case, simply getting the nvram value for my WG slot 1 address was causing a hang.

I had already made that change and uploaded it back to github yesterday, so if you want to just download the latest copy of beta 5, then that should cover it. I'm continuing to monitor it.

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"