VPNMON Time connected does not reset on a router reboot.

[scootertramp]

Shouldn't the time connected of the VPN/WG slots be reset on a router reboot? They get reset on a Reset/Reconnect
either done manually or automatically. Not a big deal, just curious.

Router was rebooted about 11 hours ago.

VPNMON-R3 - v1.7.0

Port | Mon | IFace | Health | WAN State | Public WAN IP | Ping-->WAN | City Exit / Uptime
-------|-----|--------|--------|--------------|-----------------|------------|---------------------------------
WAN0 | [X] | eth0 | [ OK ] | Active | xx.xxx.xxx.xxx | [ 11.526] | Salem: 0d 10h:58m
WAN1 | [X] | [n/a] | [n/a ] | Inactive | [n/a] | [n/a] | [n/a]
-------|-----|--------|--------|--------------|-----------------|------------|---------------------------------

OpenVPN

Slot | Mon | Svrs | Health | VPN State | Public VPN IP | Ping-->VPN | City Exit / Time Connected
-------|-----|--------|--------|--------------|-----------------|------------|---------------------------------
VPN1 | [X] | [ 8] | [ OK ] | Connected | xxx.xxx.xxx.xx | [ 28.468] | Edison: 4d 09h:24m
VPN2 | [X] | [ 8] | [ OK ] | Connected | xxx.xxx.xx.xxx | [ 22.684] | Boston: 5d 23h:37m
VPN3 | [ ] | [0000] | [n/a ] | Disconnected | [n/a] | [n/a] | [n/a]
VPN4 | [ ] | [0000] | [n/a ] | Disconnected | [n/a] | [n/a] | [n/a]
VPN5 | [ ] | [0000] | [n/a ] | Disconnected | [n/a] | [n/a] | [n/a]
-------|-----|--------|--------|--------------|-----------------|------------|---------------------------------

Wireguard

Slot | Mon | Svrs | Health | WG State | Public WG IP | Ping--->WG | City Exit / Time Connected
-------|-----|--------|--------|--------------|-----------------|------------|---------------------------------
WG1 | [X] | [ 2] | [ OK ] | Connected | xx.xxx.xxx.xxx | [ 21.862] | Boston: 1d 07h:54m

 

[Viktor Jaep]

Shouldn't the time connected of the VPN/WG slots be reset on a router reboot? They get reset on a Reset/Reconnect
either done manually or automatically. Not a big deal, just curious.

Router was rebooted about 11 hours ago.

VPNMON-R3 - v1.7.0

Port | Mon | IFace | Health | WAN State | Public WAN IP | Ping-->WAN | City Exit / Uptime
-------|-----|--------|--------|--------------|-----------------|------------|---------------------------------
WAN0 | [X] | eth0 | [ OK ] | Active | xx.xxx.xxx.xxx | [ 11.526] | Salem: 0d 10h:58m
WAN1 | [X] | [n/a] | [n/a ] | Inactive | [n/a] | [n/a] | [n/a]
-------|-----|--------|--------|--------------|-----------------|------------|---------------------------------

OpenVPN

Slot | Mon | Svrs | Health | VPN State | Public VPN IP | Ping-->VPN | City Exit / Time Connected
-------|-----|--------|--------|--------------|-----------------|------------|---------------------------------
VPN1 | [X] | [ 8] | [ OK ] | Connected | xxx.xxx.xxx.xx | [ 28.468] | Edison: 4d 09h:24m
VPN2 | [X] | [ 8] | [ OK ] | Connected | xxx.xxx.xx.xxx | [ 22.684] | Boston: 5d 23h:37m
VPN3 | [ ] | [0000] | [n/a ] | Disconnected | [n/a] | [n/a] | [n/a]
VPN4 | [ ] | [0000] | [n/a ] | Disconnected | [n/a] | [n/a] | [n/a]
VPN5 | [ ] | [0000] | [n/a ] | Disconnected | [n/a] | [n/a] | [n/a]
-------|-----|--------|--------|--------------|-----------------|------------|---------------------------------

Wireguard

Slot | Mon | Svrs | Health | WG State | Public WG IP | Ping--->WG | City Exit / Time Connected
-------|-----|--------|--------|--------------|-----------------|------------|---------------------------------
WG1 | [X] | [ 2] | [ OK ] | Connected | xx.xxx.xxx.xxx | [ 21.862] | Boston: 1d 07h:54m

Hey @scootertramp ... If you have these VPN/WG connections starting automatically (set to "Enabled" = Yes) so they restart when the router reboots, then VPNMON really has no way of knowing, as it starts after the router gets reset and connections get re-established. In other words, when VPNMON starts up, it sees the connections up, so it just continues doing the math on the time connected.

I've got my VPN slots all set to "No", which forces VPNMON to choose a new connection for me after the router reboots, and in doing so, would reset the timer. I also force a reset every 24hrs, so my stats are always < 24hrs old.

Wireguard, on the other hand, likes these to be set to "Enabled" = Yes, else its stats show all wonky in the UI, though it does seem to work.

Hope this helps!

 

[scootertramp]

Hey @scootertramp ... If you have these VPN/WG connections starting automatically (set to "Enabled" = Yes) so they restart when the router reboots, then VPNMON really has no way of knowing, as it starts after the router gets reset and connections get re-established. In other words, when VPNMON starts up, it sees the connections up, so it just continues doing the math on the time connected.

View attachment 68097

I've got my VPN slots all set to "No", which forces VPNMON to choose a new connection for me after the router reboots, and in doing so, would reset the timer. I also force a reset every 24hrs, so my stats are always < 24hrs old.

Wireguard, on the other hand, likes these to be set to "Enabled" = Yes, else its stats show all wonky in the UI, though it does seem to work.

Hope this helps!

@Viktor Jaep

Thank you.
Makes a world of sense. Currently I have all VPN/WG clients set to enable.
If I get an itch that needs scratching from the time I know how to reset.

I assume that forcing a daily reset is done using the cron time scheduler.

 

[Viktor Jaep]

@Viktor Jaep

Thank you.
Makes a world of sense. Currently I have all VPN/WG clients set to enable.
If I get an itch that needs scratching from the time I know how to reset.

Super impressed they are all running continuously that long! What VPN provider do you use?

I assume that forcing a daily reset is done using the cron time scheduler.

That's correct... just run the command sh /jffs/scripts/vpnmon-r3.sh -reset at the time(s) of your choosing!

 

[scootertramp]

Super impressed they are all running continuously that long! What VPN provider do you use?

Currently using expressvpn for vpn and proton for wireguard.