ComputerSteve
Senior Member
I notice that the script only works when I run it manually ? Is this supposed to monitor the connection automatically at reboot? Meaning do I always have to do Launch VPNMON-R2 into Normal Monitoring Mode?
Hey @ComputerSteve ...That's by design... I don't have any options to auto-start the script on router reboot, but I do have some guidance listed under this section if you want to implement it like I did?I notice that the script only works when I run it manually ? Is this supposed to monitor the connection automatically at reboot? Meaning do I always have to do Launch VPNMON-R2 into Normal Monitoring Mode?
Moving this discussion over to this thread, since we're probably way off-topic in the main Merlin threads. So there's not much I can do within the AMTM screen to show status/enabled/disabled... but I can very likely have the -pause command work on autostart. I could even provide some kind of status feedback command, like "vpnmon-r2 -status", and it kicks back some sort of status indicator... but it would be all inside an SSH window outside of amtm.I mean that would be great ! I just hope you can make the command vpnmonr2 -pause / resume work with the auto start thing at boot. Maybe also a status thing of what is happening inside the amtm script screen. Meaning so you can see if the script is active or disabled running / not running.
So basically it would just be if I have to edit a vpn config id pause it. Right now with the auto start on boot script the only way I can tell your script is working is after I reboot I notice it automatically starts a vpn client. I’m assuming it’s starting the best one based on ping since that’s what I have it set to. I just notice that with the script automatically started I can’t edit a client it isn’t picking without removing that auto start code then rebooting. If I try to edit it stops all the clients then again picks the one with the right ping. That doesn’t allow me to see if the server I just edited is working.Moving this discussion over to this thread, since we're probably way off-topic in the main Merlin threads. So there's not much I can do within the AMTM screen to show status/enabled/disabled... but I can very likely have the -pause command work on autostart. I could even provide some kind of status feedback command, like "vpnmon-r2 -status", and it kicks back some sort of status indicator... but it would be all inside an SSH window outside of amtm.
So how do you foresee this working?
1. You reboot your router
2. vpnmon-r2 is executed with a -pause command with auto start, and sits in the background
3. what will cause it to resume? will you run a vpnmon-r2 -resume command, and at what point? or will you automate this? or will you hit a key on the pause screen inside vpnmon-r2?
4. where do you foresee needing to see the status?
The other was you can tell if the script is running is by making a connection to it...So basically it would just be if I have to edit a vpn config id pause it. Right now with the auto start on boot script the only way I can tell your script is working is after I reboot I notice it automatically starts a vpn client. I’m assuming it’s starting the best one based on ping since that’s what I have it set to. I just notice that with the script automatically started I can’t edit a client it isn’t picking without removing that auto start code then rebooting. If I try to edit it stops all the clients then again picks the one with the right ping. That doesn’t allow me to see if the server I just edited is working.
vpnmon-r2 -screen
or,
screen -r vpnmon-r2
Mon Oct 17 07:29:14 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN
Mon Oct 17 07:30:18 CEST 2022 - VPNMON-R2 - Executing VPN Reset
Mon Oct 17 07:30:28 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections
Mon Oct 17 07:30:29 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED
Mon Oct 17 07:30:29 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED.
Mon Oct 17 07:30:35 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN
Mon Oct 17 07:31:39 CEST 2022 - VPNMON-R2 - Executing VPN Reset
Mon Oct 17 07:31:48 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections
Mon Oct 17 07:31:49 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED
Mon Oct 17 07:31:49 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED.
Mon Oct 17 07:31:55 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN
Mon Oct 17 07:33:00 CEST 2022 - VPNMON-R2 - Executing VPN Reset
Mon Oct 17 07:33:09 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections
Mon Oct 17 07:33:10 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED
Mon Oct 17 07:33:10 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED.
Mon Oct 17 07:33:16 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN
Mon Oct 17 07:34:20 CEST 2022 - VPNMON-R2 - Executing VPN Reset
Mon Oct 17 07:34:30 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections
Mon Oct 17 07:34:31 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED
Mon Oct 17 07:34:31 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED.
Mon Oct 17 07:34:37 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN
Mon Oct 17 07:35:41 CEST 2022 - VPNMON-R2 - Executing VPN Reset
Mon Oct 17 07:35:50 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections
Mon Oct 17 07:35:51 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED
Mon Oct 17 07:35:51 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED.
Mon Oct 17 07:35:57 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN
Mon Oct 17 07:37:02 CEST 2022 - VPNMON-R2 - Executing VPN Reset
Mon Oct 17 07:37:11 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections
Mon Oct 17 07:37:12 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED
Mon Oct 17 07:37:12 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED.
Mon Oct 17 07:37:18 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN
Mon Oct 17 07:38:22 CEST 2022 - VPNMON-R2 - Executing VPN Reset
Mon Oct 17 07:38:31 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections
Mon Oct 17 07:38:32 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED
Mon Oct 17 07:38:32 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED.
Mon Oct 17 07:38:38 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN
Mon Oct 17 07:39:43 CEST 2022 - VPNMON-R2 - Executing VPN Reset
Mon Oct 17 07:39:52 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections
Mon Oct 17 07:39:53 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED
Mon Oct 17 07:39:53 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED.
Mon Oct 17 07:39:59 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN
Mon Oct 17 07:41:03 CEST 2022 - VPNMON-R2 - Executing VPN Reset
Mon Oct 17 07:41:13 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections
Mon Oct 17 07:41:31 CEST 2022 - VPNMON-R2 - Refreshed VPN Slots 1 - 5 from 5 Recommended NordVPN Server Locations
Mon Oct 17 07:41:33 CEST 2022 - VPNMON-R2 - Randomly selected VPN2 Client ON
Mon Oct 17 07:41:37 CEST 2022 - VPNMON-R2 - VPN Reset Finished
Mon Oct 17 07:41:39 CEST 2022 - VPNMON-R2 - Trimmed the log file down to 1000 lines
Mon Oct 17 07:41:53 CEST 2022 - VPNMON-R2 - API call made to update WAN0 city to Boskovice
Mon Oct 17 07:41:53 CEST 2022 - VPNMON-R2 - API call made to update VPN city to Prague
That's a pretty interesting observation, @salvo! When it does a WAN connectivity check, it does a pretty intense couple of bundled commands using netcat and openssl to connect to and establish an SSL connection... I have a feeling your 100% bandwidth utilization was probably enough to make it timeout, and think that the WAN was down, since it couldn't make that connection. It will then loop and wait 60 seconds before trying again. I'll see if I can play with timeout values at all to give it a better chance at verifying the WAN connection during heavy loads like this. Thanks!Hello,
First of all, thanks for developping this tool which i found very interesting and helpfull. I started using in last 3 days VPNMON-R2 V2.26 and I wanted to share my findings.
Based on the logs below seems there are dropped connection, it started closely at 1:00AM and finish 7:40AM. Every minute there is a WAN issue detected.
….
Code:Mon Oct 17 07:29:14 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN Mon Oct 17 07:30:18 CEST 2022 - VPNMON-R2 - Executing VPN Reset Mon Oct 17 07:30:28 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections Mon Oct 17 07:30:29 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED Mon Oct 17 07:30:29 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED. Mon Oct 17 07:30:35 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN Mon Oct 17 07:31:39 CEST 2022 - VPNMON-R2 - Executing VPN Reset Mon Oct 17 07:31:48 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections Mon Oct 17 07:31:49 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED Mon Oct 17 07:31:49 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED. Mon Oct 17 07:31:55 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN Mon Oct 17 07:33:00 CEST 2022 - VPNMON-R2 - Executing VPN Reset Mon Oct 17 07:33:09 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections Mon Oct 17 07:33:10 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED Mon Oct 17 07:33:10 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED. Mon Oct 17 07:33:16 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN Mon Oct 17 07:34:20 CEST 2022 - VPNMON-R2 - Executing VPN Reset Mon Oct 17 07:34:30 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections Mon Oct 17 07:34:31 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED Mon Oct 17 07:34:31 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED. Mon Oct 17 07:34:37 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN Mon Oct 17 07:35:41 CEST 2022 - VPNMON-R2 - Executing VPN Reset Mon Oct 17 07:35:50 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections Mon Oct 17 07:35:51 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED Mon Oct 17 07:35:51 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED. Mon Oct 17 07:35:57 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN Mon Oct 17 07:37:02 CEST 2022 - VPNMON-R2 - Executing VPN Reset Mon Oct 17 07:37:11 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections Mon Oct 17 07:37:12 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED Mon Oct 17 07:37:12 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED. Mon Oct 17 07:37:18 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN Mon Oct 17 07:38:22 CEST 2022 - VPNMON-R2 - Executing VPN Reset Mon Oct 17 07:38:31 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections Mon Oct 17 07:38:32 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED Mon Oct 17 07:38:32 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED. Mon Oct 17 07:38:38 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN Mon Oct 17 07:39:43 CEST 2022 - VPNMON-R2 - Executing VPN Reset Mon Oct 17 07:39:52 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections Mon Oct 17 07:39:53 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED Mon Oct 17 07:39:53 CEST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED. Mon Oct 17 07:39:59 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN Mon Oct 17 07:41:03 CEST 2022 - VPNMON-R2 - Executing VPN Reset Mon Oct 17 07:41:13 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections Mon Oct 17 07:41:31 CEST 2022 - VPNMON-R2 - Refreshed VPN Slots 1 - 5 from 5 Recommended NordVPN Server Locations Mon Oct 17 07:41:33 CEST 2022 - VPNMON-R2 - Randomly selected VPN2 Client ON Mon Oct 17 07:41:37 CEST 2022 - VPNMON-R2 - VPN Reset Finished Mon Oct 17 07:41:39 CEST 2022 - VPNMON-R2 - Trimmed the log file down to 1000 lines Mon Oct 17 07:41:53 CEST 2022 - VPNMON-R2 - API call made to update WAN0 city to Boskovice Mon Oct 17 07:41:53 CEST 2022 - VPNMON-R2 - API call made to update VPN city to Prague
But as you can see by picture (avg ping for google dns, check every 60s) there are no dropped connection (and I also have not encountered any dropped connections personally).
View attachment 44866
From 1:00AM till 7:40AM it was running upload job to cloud which is intensive and utilize close to 100% bandwidth. The local server which uploads the data is not using VPN tunel (the IP is excluded from VPN tunel, set via VPN director).
Why the log shows dropped connections ? I do think connection was active and running well.
Thanks
It's got a debug mode, but it's messy, and typically use it to solve hard-to-solve programming issues... but don't have anything that would increase/decrease log verbosity. If you have any good ideas on what you would like to see, I could look into making this a possibility?Sure, will do once released.
Anyway, in the meantime, do you have debug mode built in to increase verbose level ?
curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R2/master/vpnmon-r2-2.32.sh" -o "/jffs/scripts/vpnmon-r2.sh" && chmod a+rx "/jffs/scripts/vpnmon-r2.sh"
Tue Oct 18 10:19:45 CEST 2022 - VPNMON-R2 ----------> WARNING: AVG PING across VPN tunnel > 100 ms - Executing VPN Reset
Mon Oct 17 07:26:33 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN
Great suggestions, @salvo... I'll consider adding your requests in an upcoming revision.Some input from me to consider future developments
1.) Add detected ping value, which VPN tunel has been reseted and what was WAN link ping to logging file
Code:Tue Oct 18 10:19:45 CEST 2022 - VPNMON-R2 ----------> WARNING: AVG PING across VPN tunnel > 100 ms - Executing VPN Reset
2.) Add detected ping value to WAN link to logging file
Code:Mon Oct 17 07:26:33 CEST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN
3.) Scheduling the start & stop screening i.e. auto cron list management
More question than feature:
Not sure so asking does the logic consider WAN ping vs. VPN ping. I am asking myself, why to reset the connection when WAN ping and VPN pings are similar ?
My opinion on WAN ping vs VPN ping is as follows: when WAN ping is close to 120ms and VPN ping is 130ms (for whatever reason, ie heavy upload/download )... why reset VPN, not sure what is expected here to happen ?There is a combo of WAN vs VPN pinging going on in the background, but a ping across the tunnel is especially important to determine if the tunnel connection is still viable, meaning the VPN provider is having issues, but your WAN connection is not experiencing any issues.
Tue Oct 18 13:33:58 CEST 2022 - VPNMON-R2 - API call made to update VPN city to Prague
Tue Oct 18 13:59:55 CEST 2022 - VPNMON-R2 ----------> WARNING: Switching to faster VPN2 Client - Executing VPN Reset
Tue Oct 18 13:59:55 CEST 2022 - VPNMON-R2 - Executing VPN Reset to Slot with Lowest PING
Tue Oct 18 14:00:06 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections
Tue Oct 18 14:00:17 CEST 2022 - VPNMON-R2 - VPN2 Client ON - Lowest PING of 5 VPN slots
_ ______ _ ____ _______ _ __ ____ ___
| | / / __ \/ | / / |/ / __ \/ | / / / __ \__ \ v2.31
| | / / /_/ / |/ / /|_/ / / / / |/ /_____/ /_/ /_/ /
| |/ / ____/ /| / / / / /_/ / /| /_____/ _, _/ __/
|___/_/ /_/ |_/_/ /_/\____/_/ |_/ /_/ |_/____/
----------------------------------------------------------------
Configuration Utility Options
----------------------------------------------------------------
1 : Ping Retries Before Reset? :3
2 : Timer Interval to Check VPN? :60
3 : Host IP to PING against? :8.8.8.8
4 : Update VPNMGR? :No
5 : How VPN Slots are Chosen? :Lowest PING
|-- Chances before Reset? :5
6 : Current VPN Provider? :NordVPN
|-- Enable SuperRandom? :No
|-- VPN Country (Multi?) :Czech Republic
|-- % Server Load Threshold? :50
|-- Update Skynet? :No
|-- Use Recommended Server(s)? :Yes
7 : Perform Daily VPN Reset? :Yes
|-- Daily Reset Time? :02:00
8 : Minimum PING Before Reset? :100
9 : VPN Client Slots Configured? :5
10 : Show Near-Realtime Stats? :Yes
11 : Delay Script Startup? :0
12 : Trim Logs Daily? :Yes
|-- Max Log File Size? :1000
13 : Sync Current VPN with Yazfi? :No
|-- YazFi Slots 1-9 Synced :Disabled
|
s : Save & Exit
e : Exit & Discard Changes
----------------------------------------------------------------
Selection:
Nope, the "Minimum Ping" of 100ms is a completely different qualifier to reset your VPN connection, aside from the "Lowest Ping" method on how VPN Client slots are chosen. Here's a brief explanation:After testing v2.31 for several hours, see my observation about switching to faster VPN.
Does the switching to faster VPN2 client happen after reaching > 100ms ? From the log, it is not visible i.e. I do not have visibility what was the condition(s) to switch.
Thanks, understand, so why did it trigger the switch to faster VPN at first place ? What triggered the reset ? You can see below it switches but not sure why.Nope, the "Minimum Ping" of 100ms is a completely different qualifier to reset your VPN connection, aside from the "Lowest Ping" method on how VPN Client slots are chosen. Here's a brief explanation:
Tue Oct 18 18:44:43 CEST 2022 - VPNMON-R2 - A new update (v2.32) is available to download
Tue Oct 18 18:52:13 CEST 2022 - VPNMON-R2 ----------> WARNING: Switching to faster VPN3 Client - Executing VPN Reset
Tue Oct 18 18:52:13 CEST 2022 - VPNMON-R2 - Executing VPN Reset to Slot with Lowest PING
Tue Oct 18 18:52:23 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections
Tue Oct 18 18:52:34 CEST 2022 - VPNMON-R2 - VPN3 Client ON - Lowest PING of 5 VPN slots
Tue Oct 18 18:52:38 CEST 2022 - VPNMON-R2 - VPN Reset Finished
Tue Oct 18 18:52:41 CEST 2022 - VPNMON-R2 - A new update (v2.32) is available to download
Tue Oct 18 18:52:41 CEST 2022 - VPNMON-R2 - Trimmed the log file down to 1000 lines
Tue Oct 18 18:52:41 CEST 2022 - VPNMON-R2 - Resuming normal operations
Tue Oct 18 18:52:53 CEST 2022 - VPNMON-R2 - API call made to update WAN0 city to Boskovice
Tue Oct 18 18:52:53 CEST 2022 - VPNMON-R2 - API call made to update VPN city to Prague
Tue Oct 18 19:00:47 CEST 2022 - VPNMON-R2 ----------> WARNING: Switching to faster VPN1 Client - Executing VPN Reset
Tue Oct 18 19:00:47 CEST 2022 - VPNMON-R2 - Executing VPN Reset to Slot with Lowest PING
Tue Oct 18 19:00:58 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections
Tue Oct 18 19:01:09 CEST 2022 - VPNMON-R2 - VPN1 Client ON - Lowest PING of 5 VPN slots
Tue Oct 18 19:01:13 CEST 2022 - VPNMON-R2 - VPN Reset Finished
You've chosen to use recommended servers, so they're all close and have similar ping values. VPN 3 might be 18.034ms, VPN 1 might be 17.234ms, so it's going to choose VPN 1 after 5 chances (60sec intervals) if it still is considered the fastest server. Watching the UI gives you a lot of insight on what's happening and encourage you to take a look at that instead of the logs.Thanks, understand, so why did it trigger the switch to faster VPN at first place ? What triggered the reset ? You can see below it switches but not sure why.
Code:Tue Oct 18 18:44:43 CEST 2022 - VPNMON-R2 - A new update (v2.32) is available to download Tue Oct 18 18:52:13 CEST 2022 - VPNMON-R2 ----------> WARNING: Switching to faster VPN3 Client - Executing VPN Reset Tue Oct 18 18:52:13 CEST 2022 - VPNMON-R2 - Executing VPN Reset to Slot with Lowest PING Tue Oct 18 18:52:23 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections Tue Oct 18 18:52:34 CEST 2022 - VPNMON-R2 - VPN3 Client ON - Lowest PING of 5 VPN slots Tue Oct 18 18:52:38 CEST 2022 - VPNMON-R2 - VPN Reset Finished Tue Oct 18 18:52:41 CEST 2022 - VPNMON-R2 - A new update (v2.32) is available to download Tue Oct 18 18:52:41 CEST 2022 - VPNMON-R2 - Trimmed the log file down to 1000 lines Tue Oct 18 18:52:41 CEST 2022 - VPNMON-R2 - Resuming normal operations Tue Oct 18 18:52:53 CEST 2022 - VPNMON-R2 - API call made to update WAN0 city to Boskovice Tue Oct 18 18:52:53 CEST 2022 - VPNMON-R2 - API call made to update VPN city to Prague Tue Oct 18 19:00:47 CEST 2022 - VPNMON-R2 ----------> WARNING: Switching to faster VPN1 Client - Executing VPN Reset Tue Oct 18 19:00:47 CEST 2022 - VPNMON-R2 - Executing VPN Reset to Slot with Lowest PING Tue Oct 18 19:00:58 CEST 2022 - VPNMON-R2 - Killed all VPN Client Connections Tue Oct 18 19:01:09 CEST 2022 - VPNMON-R2 - VPN1 Client ON - Lowest PING of 5 VPN slots Tue Oct 18 19:01:13 CEST 2022 - VPNMON-R2 - VPN Reset Finished
Yes... the Lowest PING method looks at all 5 of your VPN slots:So given the settings below, if the connection is less than < 100ms continuously, can the VPN still be changed to a faster one ?
Code:5 : How VPN Slots are Chosen? :Lowest PING |-- Chances before Reset? :5 8 : Minimum PING Before Reset? :100
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!