VPNMON VPNMON-R2 v2.0 -Jul 10, 2022- Monitor your VPN connection's Health (Thread locked/closed)

[Viktor Jaep]

Full log in case you want to take a closer look: vpnmon-r2.log


Don't know why the log dates are jumbled

View attachment 42681

The log is written to sequentially. I think you might be having some kind of time issue on your end?

It looks like it happened when one of your wan connections went down... Perhaps a failover isp issue?

 

[JAX1337]

The log is written to sequentially. I think you might be having some kind of time issue on your end?

Yes there was an issue with my DNS server, saw it in syslog as well, got corrected after a successful NTP sync

 

[Kal1975]

Hi all.

Just updated amtm to latest and tried update of vpnmon through it...an error occurred. I was running vpnmon v1.5 No big deal. ran vpnmon from command line to update from there.

OK. Went through config update using existing config file. Error popped up at the very end when going to save configuration:

./vpnmon-r2.sh: line 1308: syntax error: unexpected "(" (expecting "fi")

Keep up the great work!

UPDATE: Just tried it again and it worked. Odd. Nothing to see here...carry on...

 

[JAX1337]

Full Syslog shows a better picture :

Jul 11 21:38:15 GT-AX11000-6A10 openvpn-routing: Clearing routing table for VPN - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

 

[Kal1975]

Me again...I just accidentally started vpnmon using screen and a second session was started.

Then when trying to reconnect it showed there were two sessions.

Is this something that should be handled? I'm not sure if running multiple will cause issues...I think it might. Thoughts:

• checking if there is an already running screen and then preventing running another?
• killing the old one and starting a new one?
• asking what to do?
• other? haha

I had to lookup how to switch to each session individually or to kill the running sessions. The following is for those looking for the info quickly:

When there's more than one, something like this is listed:

24759.vpnmon-r2 (Detached)
29450.vpnmon-r2 (Detached)

Then, you can switch to either using the number in front with "screen -r 24759", for example.

You can list all screen sessions with "screen -ls"

 

[Kal1975]

I'm on a roll

When I run vpnmon, I see my 5 VPN slots. I'm connected to one of them, 3 show a time in ms, which I think are the ping times. The last one shows "OFFLINE" in red. I checked and my VPN Provider changed the servers. I changed the assignment for slot 4 and noticed this:

• while I was messing with the settings for slot 4, vpnmon showed ping error or something like that...good
• I was wondering if the new settings would be picked up or vpnmon would need to be restarted. on the next cycle, it was picked up...great

Question: when randomly selecting the next slot, does it avoid choosing the OFFLINE slot or does it keep randomly selecting a slot until a connection is made?

 

[Stephen Harrington]

Stuck on this screen, last log entry is from 12hrs prior, Whats wrong ?

Yes, I have wan fail over, 2 separate connections, its courtesy of Dual Wan monitor script by @Ranger802004

@Viktor Jaep just chiming in to say I also saw that screen when I tried to have a quick play with the Dual WAN Monitor script the other day ... I didn't have time to troubleshoot and had to roll back to a saved Config/JFFS pair ... so no logs saved unfortunately.

I had plugged in my 4G USB stick (which is my backup if main broadband goes down), switched on Dual WAN mode and installed the @Ranger802004 script, then rebooted.

So just confirming what @JAX1337 saw and that there may be a clash with that script and/or dual WAN mode perhaps?

Was going to have another play when I had more time and try and document it a lot better but @JAX1337 beat me to it

 

[Viktor Jaep]

Me again...I just accidentally started vpnmon using screen and a second session was started.

Then when trying to reconnect it showed there were two sessions.

Is this something that should be handled? I'm not sure if running multiple will cause issues...I think it might. Thoughts:

• checking if there is an already running screen and then preventing running another?
• killing the old one and starting a new one?
• asking what to do?
• other? haha

I had to lookup how to switch to each session individually or to kill the running sessions. The following is for those looking for the info quickly:

When there's more than one, something like this is listed:

24759.vpnmon-r2 (Detached)
29450.vpnmon-r2 (Detached)

Then, you can switch to either using the number in front with "screen -r 24759", for example.

You can list all screen sessions with "screen -ls"

Definitely a good idea... to see if another screen session already exists out there with the tag "vpnmon-r2"... can't help it if people start and name their own though. I'll definitely look into it, and glad you figured out how to connect to one of your detached screens.

 

[Viktor Jaep]

I'm on a roll

When I run vpnmon, I see my 5 VPN slots. I'm connected to one of them, 3 show a time in ms, which I think are the ping times. The last one shows "OFFLINE" in red. I checked and my VPN Provider changed the servers. I changed the assignment for slot 4 and noticed this:

• while I was messing with the settings for slot 4, vpnmon showed ping error or something like that...good
• I was wondering if the new settings would be picked up or vpnmon would need to be restarted. on the next cycle, it was picked up...great

Question: when randomly selecting the next slot, does it avoid choosing the OFFLINE slot or does it keep randomly selecting a slot until a connection is made?

So at this point, its not smart enough to not choose the offline slot. That's more of a visual heads-up for you to be aware that one of your servers isn't there. vpnmon-r2 will try to connect to it, fail, and when it sees it was unsuccessful, reconnect randomly to a slot that will actually work.

 

[Viktor Jaep]

@Viktor Jaep just chiming in to say I also saw that screen when I tried to have a quick play with the Dual WAN Monitor script the other day ... I didn't have time to troubleshoot and had to roll back to a saved Config/JFFS pair ... so no logs saved unfortunately.

I had plugged in my 4G USB stick (which is my backup if main broadband goes down), switched on Dual WAN mode and installed the @Ranger802004 script, then rebooted.

So just confirming what @JAX1337 saw and that there may be a clash with that script and/or dual WAN mode perhaps?

Was going to have another play when I had more time and try and document it a lot better but @JAX1337 beat me to it

Thanks for the heads-up, @Stephen Harrington... I've been going through my wancheck code, and it's definitely not written to handle a situation where 2 WAN connections are running at the same time. It's made for having one or the other up, while the other is down. I'll need to rework this piece a bit, and hopefully make it a little more compliant with the dual-wan script functionality. You dual-wan guys, always throwing sticks in my spokes! If you have any screenshots to share, feel free... or if it looks exactly like @JAX1337's issue, no worries.

 

[Viktor Jaep]

For all my dual-wan/failover friends (@JAX1337 @Stephen Harrington)... could you please try this beta, and let me know if this clears up your dual-wan display issues? If you wouldn't mind putting it through the ringer, and failing over, failing back, and seeing if everything looks right? I wish I could test this, but I don't have a secondary wan to play with.

VPNMON-R2 v2.01b

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R2/master/vpnmon-r2-2.01b.sh" -o "/jffs/scripts/vpnmon-r2.sh" && chmod a+rx "/jffs/scripts/vpnmon-r2.sh"

Revert back to v2.0 release (incase you need to)

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R2/master/vpnmon-r2-2.0.sh" -o "/jffs/scripts/vpnmon-r2.sh" && chmod a+rx "/jffs/scripts/vpnmon-r2.sh"

 

[Viktor Jaep]

Me again...I just accidentally started vpnmon using screen and a second session was started.

Then when trying to reconnect it showed there were two sessions.

Is this something that should be handled? I'm not sure if running multiple will cause issues...I think it might. Thoughts:

• checking if there is an already running screen and then preventing running another?
• killing the old one and starting a new one?
• asking what to do?
• other? haha

I had to lookup how to switch to each session individually or to kill the running sessions. The following is for those looking for the info quickly:

When there's more than one, something like this is listed:

24759.vpnmon-r2 (Detached)
29450.vpnmon-r2 (Detached)

Then, you can switch to either using the number in front with "screen -r 24759", for example.

You can list all screen sessions with "screen -ls"

@Kal1975 ... just wanted to let you know of another screen trick (shortcut). If you only have one screen window running, it will default to opening up your only screen window by typing:

screen -r

 

[Ranger802004]

Thanks for the heads-up, @Stephen Harrington... I've been going through my wancheck code, and it's definitely not written to handle a situation where 2 WAN connections are running at the same time. It's made for having one or the other up, while the other is down. I'll need to rework this piece a bit, and hopefully make it a little more compliant with the dual-wan script functionality. You dual-wan guys, always throwing sticks in my spokes! If you have any screenshots to share, feel free... or if it looks exactly like @JAX1337's issue, no worries.

If you need help on this portion just let me know, you already know I’m willing to help.

 

[Viktor Jaep]

If you need help on this portion just let me know, you already know I’m willing to help.

Many thanks @Ranger802004! Let's see if this fix works... I have a good feeling.

 

[JAX1337]

For all my dual-wan/failover friends (@JAX1337 @Stephen Harrington)... could you please try this beta, and let me know if this clears up your dual-wan display issues? If you wouldn't mind putting it through the ringer, and failing over, failing back, and seeing if everything looks right? I wish I could test this, but I don't have a secondary wan to play with.

VPNMON-R2 v2.01b

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R2/master/vpnmon-r2-2.01b.sh" -o "/jffs/scripts/vpnmon-r2.sh" && chmod a+rx "/jffs/scripts/vpnmon-r2.sh"

Revert back to v2.0 release (incase you need to)

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R2/master/vpnmon-r2-2.0.sh" -o "/jffs/scripts/vpnmon-r2.sh" && chmod a+rx "/jffs/scripts/vpnmon-r2.sh"

Testing it, will let you know


edit

Still seeing those weird messages

 

[Viktor Jaep]

Testing it, will let you know


edit

Still seeing those weird messages

View attachment 42706

Getting there. At least it assigned the correct interface and attempted a ping... Thanks! I'll send another try shortly.

 

[JAX1337]

Getting there. At least it assigned the correct interface and attempted a ping... Thanks! I'll send another try shortly.

The message starts displaying from the second WAN check, don't know if it helps

 

[Viktor Jaep]

The message starts displaying from the second WAN check, don't know if it helps

OK let's give this one a shot please!

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R2/master/vpnmon-r2-2.01b2.sh" -o "/jffs/scripts/vpnmon-r2.sh" && chmod a+rx "/jffs/scripts/vpnmon-r2.sh"

 

[JAX1337]

OK let's give this one a shot please!

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R2/master/vpnmon-r2-2.01b2.sh" -o "/jffs/scripts/vpnmon-r2.sh" && chmod a+rx "/jffs/scripts/vpnmon-r2.sh"

This time error messages seem to have disappeared, but the script takes atleast 10 sec to show WAN1 everytime there is check
and WAN 1 ping seems off

 

[Viktor Jaep]

This time error messages seem to have disappeared, but the script takes atleast 10 sec to show WAN1 everytime there is check
and WAN 1 ping seems offView attachment 42712

Yey, that's good news... OK, yeah, when the ping=1, then that means it's failing.... Is your dual-wan set up for load balancing or failover?