Menu
What's new
By:
Filters Better Search

VPNMON VPNMON-R2 v2.52 -Mar 27, 2023- Monitor your VPN connection's Health (Thread locked/closed)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

iTyPsIDg said:
Also, separate note, but today VPNMON-R2 kept failing when it tested the configured VPN slot and would initiate a reset. It started overnight and continued after a reboot. However, the VPN is working fine for me. I had to kill the screen session so it wouldn't keep resetting my VPN. Is anyone else experiencing this?
Click to expand...
This is the error I keep getting:
Less: 
Fri Feb 10 09:00:32 BRT 2023 - VPNMON-R2 ----------> ERROR: VPN4 Ping/HTTP response failed
Fri Feb 10 09:00:35 BRT 2023 - VPNMON-R2 ----------> ERROR: VPN4 Connection failed - Executing VPN Reset
Fri Feb 10 09:00:35 BRT 2023 - VPNMON-R2 - Executing VPN Reset
Fri Feb 10 09:02:15 BRT 2023 - VPNMON-R2 - API call made to update WAN0 city to Florianópolis
Fri Feb 10 09:02:18 BRT 2023 - VPNMON-R2 ----------> ERROR: VPN0 Connection failed - Executing VPN Reset
Fri Feb 10 09:02:18 BRT 2023 - VPNMON-R2 - Executing VPN Reset
Fri Feb 10 09:02:27 BRT 2023 - VPNMON-R2 - Killed all VPN Client Connections
Fri Feb 10 09:02:59 BRT 2023 - VPNMON-R2 - Updated Skynet Whitelist
Fri Feb 10 09:03:12 BRT 2023 - VPNMON-R2 - Refreshed VPN Slots 1 - 4 from 5 Recommended NordVPN Server Locations
Fri Feb 10 09:03:13 BRT 2023 - VPNMON-R2 - Randomly selected VPN2 Client ON
Fri Feb 10 09:03:59 BRT 2023 - VPNMON-R2 - Successfully updated YazFi guest network(s) with the current VPN slot.
Fri Feb 10 09:03:59 BRT 2023 - VPNMON-R2 - VPN Reset Finished
Fri Feb 10 09:04:01 BRT 2023 - VPNMON-R2 - Trimmed the log file down to 1000 lines
Fri Feb 10 09:04:01 BRT 2023 - VPNMON-R2 - Resuming normal operations
Fri Feb 10 09:04:13 BRT 2023 - VPNMON-R2 - API call made to update WAN0 city to Florianópolis
Fri Feb 10 09:04:25 BRT 2023 - VPNMON-R2 ----------> ERROR: VPN2 Ping/HTTP response failed
Fri Feb 10 09:04:29 BRT 2023 - VPNMON-R2 ----------> ERROR: VPN2 Connection failed - Executing VPN Reset
Fri Feb 10 09:04:29 BRT 2023 - VPNMON-R2 - Executing VPN Reset
Fri Feb 10 09:04:37 BRT 2023 - VPNMON-R2 - Killed all VPN Client Connections
Fri Feb 10 09:05:10 BRT 2023 - VPNMON-R2 - Updated Skynet Whitelist
Fri Feb 10 09:05:18 BRT 2023 - VPNMON-R2 - Refreshed VPN Slots 1 - 4 from 5 Recommended NordVPN Server Locations
Fri Feb 10 09:05:19 BRT 2023 - VPNMON-R2 - Randomly selected VPN2 Client ON
Fri Feb 10 09:06:08 BRT 2023 - VPNMON-R2 - Successfully updated YazFi guest network(s) with the current VPN slot.
Fri Feb 10 09:06:08 BRT 2023 - VPNMON-R2 - VPN Reset Finished
Fri Feb 10 09:06:10 BRT 2023 - VPNMON-R2 - Trimmed the log file down to 1000 lines
Fri Feb 10 09:06:10 BRT 2023 - VPNMON-R2 - Resuming normal operations
Fri Feb 10 12:15:25 BRT 2023 - VPNMON-R2 - API call made to update WAN0 city to Florianópolis
Fri Feb 10 12:15:36 BRT 2023 - VPNMON-R2 ----------> ERROR: VPN2 Ping/HTTP response failed
Fri Feb 10 12:15:39 BRT 2023 - VPNMON-R2 ----------> ERROR: VPN0 Connection failed - Executing VPN Reset
Fri Feb 10 12:15:39 BRT 2023 - VPNMON-R2 - Executing VPN Reset
Fri Feb 10 12:15:46 BRT 2023 - VPNMON-R2 - Killed all VPN Client Connections
Fri Feb 10 12:16:20 BRT 2023 - VPNMON-R2 - Updated Skynet Whitelist
Fri Feb 10 12:16:28 BRT 2023 - VPNMON-R2 - Refreshed VPN Slots 1 - 4 from 5 Recommended NordVPN Server Locations
Fri Feb 10 12:16:29 BRT 2023 - VPNMON-R2 - Randomly selected VPN2 Client ON
Fri Feb 10 12:17:16 BRT 2023 - VPNMON-R2 - Successfully updated YazFi guest network(s) with the current VPN slot.
Fri Feb 10 12:17:16 BRT 2023 - VPNMON-R2 - VPN Reset Finished
Fri Feb 10 12:17:18 BRT 2023 - VPNMON-R2 - Trimmed the log file down to 1000 lines
Fri Feb 10 12:17:18 BRT 2023 - VPNMON-R2 - Resuming normal operations
Fri Feb 10 12:17:30 BRT 2023 - VPNMON-R2 - API call made to update WAN0 city to Florianópolis
 
iTyPsIDg said:
This is the error I keep getting:
Less: 
Fri Feb 10 09:00:32 BRT 2023 - VPNMON-R2 ----------> ERROR: VPN4 Ping/HTTP response failed
Fri Feb 10 09:00:35 BRT 2023 - VPNMON-R2 ----------> ERROR: VPN4 Connection failed - Executing VPN Reset
Fri Feb 10 09:00:35 BRT 2023 - VPNMON-R2 - Executing VPN Reset
Fri Feb 10 09:02:15 BRT 2023 - VPNMON-R2 - API call made to update WAN0 city to Florianópolis
Fri Feb 10 09:02:18 BRT 2023 - VPNMON-R2 ----------> ERROR: VPN0 Connection failed - Executing VPN Reset
Fri Feb 10 09:02:18 BRT 2023 - VPNMON-R2 - Executing VPN Reset
Fri Feb 10 09:02:27 BRT 2023 - VPNMON-R2 - Killed all VPN Client Connections
Fri Feb 10 09:02:59 BRT 2023 - VPNMON-R2 - Updated Skynet Whitelist
Fri Feb 10 09:03:12 BRT 2023 - VPNMON-R2 - Refreshed VPN Slots 1 - 4 from 5 Recommended NordVPN Server Locations
Fri Feb 10 09:03:13 BRT 2023 - VPNMON-R2 - Randomly selected VPN2 Client ON
Fri Feb 10 09:03:59 BRT 2023 - VPNMON-R2 - Successfully updated YazFi guest network(s) with the current VPN slot.
Fri Feb 10 09:03:59 BRT 2023 - VPNMON-R2 - VPN Reset Finished
Fri Feb 10 09:04:01 BRT 2023 - VPNMON-R2 - Trimmed the log file down to 1000 lines
Fri Feb 10 09:04:01 BRT 2023 - VPNMON-R2 - Resuming normal operations
Fri Feb 10 09:04:13 BRT 2023 - VPNMON-R2 - API call made to update WAN0 city to Florianópolis
Fri Feb 10 09:04:25 BRT 2023 - VPNMON-R2 ----------> ERROR: VPN2 Ping/HTTP response failed
Fri Feb 10 09:04:29 BRT 2023 - VPNMON-R2 ----------> ERROR: VPN2 Connection failed - Executing VPN Reset
Fri Feb 10 09:04:29 BRT 2023 - VPNMON-R2 - Executing VPN Reset
Fri Feb 10 09:04:37 BRT 2023 - VPNMON-R2 - Killed all VPN Client Connections
Fri Feb 10 09:05:10 BRT 2023 - VPNMON-R2 - Updated Skynet Whitelist
Fri Feb 10 09:05:18 BRT 2023 - VPNMON-R2 - Refreshed VPN Slots 1 - 4 from 5 Recommended NordVPN Server Locations
Fri Feb 10 09:05:19 BRT 2023 - VPNMON-R2 - Randomly selected VPN2 Client ON
Fri Feb 10 09:06:08 BRT 2023 - VPNMON-R2 - Successfully updated YazFi guest network(s) with the current VPN slot.
Fri Feb 10 09:06:08 BRT 2023 - VPNMON-R2 - VPN Reset Finished
Fri Feb 10 09:06:10 BRT 2023 - VPNMON-R2 - Trimmed the log file down to 1000 lines
Fri Feb 10 09:06:10 BRT 2023 - VPNMON-R2 - Resuming normal operations
Fri Feb 10 12:15:25 BRT 2023 - VPNMON-R2 - API call made to update WAN0 city to Florianópolis
Fri Feb 10 12:15:36 BRT 2023 - VPNMON-R2 ----------> ERROR: VPN2 Ping/HTTP response failed
Fri Feb 10 12:15:39 BRT 2023 - VPNMON-R2 ----------> ERROR: VPN0 Connection failed - Executing VPN Reset
Fri Feb 10 12:15:39 BRT 2023 - VPNMON-R2 - Executing VPN Reset
Fri Feb 10 12:15:46 BRT 2023 - VPNMON-R2 - Killed all VPN Client Connections
Fri Feb 10 12:16:20 BRT 2023 - VPNMON-R2 - Updated Skynet Whitelist
Fri Feb 10 12:16:28 BRT 2023 - VPNMON-R2 - Refreshed VPN Slots 1 - 4 from 5 Recommended NordVPN Server Locations
Fri Feb 10 12:16:29 BRT 2023 - VPNMON-R2 - Randomly selected VPN2 Client ON
Fri Feb 10 12:17:16 BRT 2023 - VPNMON-R2 - Successfully updated YazFi guest network(s) with the current VPN slot.
Fri Feb 10 12:17:16 BRT 2023 - VPNMON-R2 - VPN Reset Finished
Fri Feb 10 12:17:18 BRT 2023 - VPNMON-R2 - Trimmed the log file down to 1000 lines
Fri Feb 10 12:17:18 BRT 2023 - VPNMON-R2 - Resuming normal operations
Fri Feb 10 12:17:30 BRT 2023 - VPNMON-R2 - API call made to update WAN0 city to Florianópolis
Click to expand...
I too having problem with nordvpn. It appears icmp ping is blocked. Can you try
Code: 
 ping -I tun11 8.8.8.8
?

perhaps is my router problem. I cannot ping from router. But from client connected to nordvpn client over the router can ping.
 
Last edited:
chongnt said:
I too having problem with nordvpn. It appears icmp ping is blocked. Can you try
Code: 
 ping -I tun11 8.8.8.8
?

perhaps is my router problem. I cannot ping from router. But from client connected to nordvpn client over the router can ping.
Click to expand...
I'm not having any troubles on this end with VPNMON-R2 or NordVPN... I'm using target 8.8.8.8. I'm on 388.1 on the AX6000.

@iTyPsIDg ... this would definitely be happening if you can't ping for some reason. Perhaps try configuring a different host? Maybe like a NordVPN DNS server?
 
Viktor Jaep said:
I'm not having any troubles on this end with VPNMON-R2 or NordVPN... I'm using target 8.8.8.8. I'm on 388.1 on the AX6000.

@iTyPsIDg ... this would definitely be happening if you can't ping for some reason. Perhaps try configuring a different host? Maybe like a NordVPN DNS server?
Click to expand...
Same for me here, getting this error

Code: 
Fri Feb 10 16:51:08 CET 2023 - VPNMON-R2 - API call made to update WAN0 city to Hlusice
Fri Feb 10 16:51:24 CET 2023 - VPNMON-R2 ----------> ERROR: VPN1 Ping/HTTP response failed
Fri Feb 10 16:51:27 CET 2023 - VPNMON-R2 ----------> ERROR: VPN0 Connection failed - Executing VPN Reset
Fri Feb 10 16:51:27 CET 2023 - VPNMON-R2 - Executing VPN Reset
Fri Feb 10 16:51:37 CET 2023 - VPNMON-R2 - Killed all VPN Client Connections
Fri Feb 10 16:51:56 CET 2023 - VPNMON-R2 - Refreshed VPN Slots 1 - 5 from 5 Recommended NordVPN Server Locations
Fri Feb 10 16:51:56 CET 2023 - VPNMON-R2 - VPN2 Client ON - Lowest PING of 5 VPN slots
Fri Feb 10 16:52:00 CET 2023 - VPNMON-R2 - VPN Reset Finished
Fri Feb 10 16:52:02 CET 2023 - VPNMON-R2 - Trimmed the log file down to 1000 lines
Fri Feb 10 16:52:02 CET 2023 - VPNMON-R2 - Resuming normal operations
Fri Feb 10 16:52:14 CET 2023 - VPNMON-R2 - API call made to update WAN0 city to Hlusice
Fri Feb 10 16:52:30 CET 2023 - VPNMON-R2 ----------> ERROR: VPN2 Ping/HTTP response failed
Fri Feb 10 16:58:26 CET 2023 - VPNMON-R2 - API call made to update WAN0 city to Hlusice
Fri Feb 10 16:58:43 CET 2023 - VPNMON-R2 ----------> ERROR: VPN3 Ping/HTTP response failed
Fri Feb 10 16:58:46 CET 2023 - VPNMON-R2 ----------> ERROR: VPN0 Connection failed - Executing VPN Reset
Fri Feb 10 16:58:46 CET 2023 - VPNMON-R2 - Executing VPN Reset
Fri Feb 10 16:58:57 CET 2023 - VPNMON-R2 - Killed all VPN Client Connections
Fri Feb 10 16:59:15 CET 2023 - VPNMON-R2 - Refreshed VPN Slots 1 - 5 from 5 Recommended NordVPN Server Locations
Fri Feb 10 16:59:15 CET 2023 - VPNMON-R2 - VPN4 Client ON - Lowest PING of 5 VPN slots
Fri Feb 10 16:59:19 CET 2023 - VPNMON-R2 - VPN Reset Finished
Fri Feb 10 16:59:22 CET 2023 - VPNMON-R2 - Trimmed the log file down to 1000 lines
Fri Feb 10 16:59:22 CET 2023 - VPNMON-R2 - Resuming normal operations
Fri Feb 10 16:59:34 CET 2023 - VPNMON-R2 - API call made to update WAN0 city to Hlusice
Fri Feb 10 16:59:50 CET 2023 - VPNMON-R2 ----------> ERROR: VPN4 Ping/HTTP response failed

During I am connected ~ few seconds I do have a response, then disconnect (I do use killswitch when I am not connect to VPN) and it repeats all over again.

Code: 
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
{"coordinates":{"latitude":50.0883,"longitude":14.4124},"ip":"185.209.221.62","isp":"Tefincom S.A.","host":{"ip_address":"185.209.221.62","prefix_len":23},"status":true,"country":"Czechia","region":"Hlavni mesto Praha","city":"Prague","location":"Czechia, Hlavni mesto Praha, Prague","area_code":"110 00","country_code":"CZ"}CoreELEC:~ #
CoreELEC:~ #
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
curl: (7) Failed to connect to nordvpn.com port 443 after 5 ms: Connection refused
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
curl: (7) Failed to connect to nordvpn.com port 443 after 311 ms: Connection refused
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
curl: (7) Failed to connect to nordvpn.com port 443 after 6 ms: Connection refused
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
curl: (7) Failed to connect to nordvpn.com port 443 after 5 ms: Connection refused
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
curl: (7) Failed to connect to nordvpn.com port 443 after 5 ms: Connection refused
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
curl: (7) Failed to connect to nordvpn.com port 443 after 5 ms: Connection refused
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
curl: (7) Failed to connect to nordvpn.com port 443 after 5 ms: Connection refused
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
curl: (7) Failed to connect to nordvpn.com port 443 after 7 ms: Connection refused
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
curl: (7) Failed to connect to nordvpn.com port 443 after 7 ms: Connection refused
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
curl: (7) Failed to connect to nordvpn.com port 443 after 5 ms: Connection refused
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
curl: (7) Failed to connect to nordvpn.com port 443 after 5 ms: Connection refused
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
curl: (7) Failed to connect to nordvpn.com port 443 after 8 ms: Connection refused
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
curl: (7) Failed to connect to nordvpn.com port 443 after 7 ms: Connection refused
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
curl: (7) Failed to connect to nordvpn.com port 443 after 7 ms: Connection refused
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
curl: (7) Failed to connect to nordvpn.com port 443 after 8 ms: Connection refused
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
{"coordinates":{"latitude":50.0883,"longitude":14.4124},"ip":"2.56.253.26","isp":"DediPath","host":{"domain":"itemleaf.com","ip_address":"2.56.253.26","prefix_len":24},"status":true,"country":"Czechia","region":"Hlavni mesto Praha","city":"Prague","location":"Czechia, Hlavni mesto Praha, Prague","area_code":"110 00","country_code":"CZ"}CoreELEC:~ #

EDIT: there is some configuration issue at my end, I can not ping

Code: 
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
{"coordinates":{"latitude":50.0883,"longitude":14.4124},"ip":"2.56.253.26","isp":"DediPath","host":{"domain":"itemleaf.com","ip_address":"2.56.253.26","prefix_len":24},"status":true,"country":"Czechia","region":"Hlavni mesto Praha","city":"Prague","location":"Czechia, Hlavni mesto Praha, Prague","area_code":"110 00","country_code":"CZ"}CoreELEC:~ #
CoreELEC:~ #
CoreELEC:~ # ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
CoreELEC:~ # ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
CoreELEC:~ # curl https://nordvpn.com/wp-admin/admin-ajax.php?action=get_user_info_data
{"coordinates":{"latitude":50.0883,"longitude":14.4124},"ip":"2.56.253.26","isp":"DediPath","host":{"domain":"itemleaf.com","ip_address":"2.56.253.26","prefix_len":24},"status":true,"country":"Czechia","region":"Hlavni mesto Praha","city":"Prague","location":"Czechia, Hlavni mesto Praha, Prague","area_code":"110 00","country_code":"CZ"}CoreELEC:~ #
 
Last edited:
I just tried pinging 9.9.9.9 and 8.8.8.8 from the current tunnel, tun12, both have 100% packet loss. However, I'm currently on the VPN and working fine. I stopped the vpnmon-r2 script from running as soon as I saw the screen where it begins the ping test.
 
I also tried pinging Nord's SmartDNS server (103.86.96.103) and still had 100% packet loss.
 
Seems like ping is blocked in the VPN tunnel, I can not ping IPs either

Code: 
CoreELEC:~ # ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
^C
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
CoreELEC:~ # ping www.google.com
PING www.google.com (142.251.37.100): 56 data bytes
^C
--- www.google.com ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
CoreELEC:~ # ping 142.251.37.100
PING 142.251.37.100 (142.251.37.100): 56 data bytes
^C
--- 142.251.37.100 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
CoreELEC:~ #

Ping issue also when using windows PC with nordvpn app on and connected:

Code: 
C:\Users\rasti>ping 8.8.8.8


Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Request timed out.


Ping statistics for 8.8.8.8:
    Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C
^C
C:\Users\rasti>
 
Last edited:
salvo said:
Seems like ping is blocked in the VPN tunnel, I can not ping IPs either

Code: 
CoreELEC:~ # ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
^C
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
CoreELEC:~ # ping www.google.com
PING www.google.com (142.251.37.100): 56 data bytes
^C
--- www.google.com ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
CoreELEC:~ # ping 142.251.37.100
PING 142.251.37.100 (142.251.37.100): 56 data bytes
^C
--- 142.251.37.100 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
CoreELEC:~ #

Ping issue also when using windows PC with nordvpn app on and connected:

Code: 
C:\Users\rasti>ping 8.8.8.8


Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Request timed out.


Ping statistics for 8.8.8.8:
    Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C
^C
C:\Users\rasti>
Click to expand...
Interesting. I see the same thing, except when I ping Nord's SmartDNS server.

1676047519171.png
 
It is even worse here, seems like issue on NORDVPN side, I tried the online chat on nordvpn but it is not working :)

Code: 
CoreELEC:~ # ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
^C
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
CoreELEC:~ # ping 103.86.96.103
PING 103.86.96.103 (103.86.96.103): 56 data bytes
^C
--- 103.86.96.103 ping statistics ---
18 packets transmitted, 0 packets received, 100% packet loss
CoreELEC:~ #
 
iTyPsIDg said:
NordVPN needs to run their changes by @Viktor Jaep in the future. Don't they know we rely on his scripts?
Click to expand...
Lol! Well I'm really glad it wasn't me! I'm sure it was just someone flipping the wrong switch on their end... Hope it's resolved soon! I've been connected to Miami today and so far, all has been well.
 
iTyPsIDg said:
Correct. I'm hoping that if you can catch it quickly enough, you'll have cached DNS results to initiate the reset before all DNS fails. Once that happens, VPNMON-R2 keeps resetting.
Click to expand...
Hey @iTyPsIDg ... could you please explain to me why a VPN reset needs to happen relatively fast if your WAN IP changes, as you might lose DNS resolution capabilties?

iTyPsIDg said:
Putting things in the correct thread:

One issue I could see is what I run into from time to time: using the stated WAN IP rather than curling icanhazip.com. Some of my Airbnb's don't allow me to replace their router, so I have to plug mine into theirs which gives my WAN a private IP.
Click to expand...
This shouldn't be a problem - I could keep track of the internally assigned WAN IP instead of using the icanhazip one...
 
Last edited:
Viktor Jaep said:
Hey @iTyPsIDg ... could you please explain to me why a VPN reset needs to happen relatively fast if your WAN IP changes, as you might lose DNS resolution capabilties?
Click to expand...
DNS caching means it needs to happen relatively quickly. If the change to SmartDNS doesn't happen before the DNS result ages out, then you won't be able to reach Nord to make the change.
Viktor Jaep said:
This shouldn't be a problem - I could keep track of the internally assigned WAN IP instead of using the icanhazip one...
Click to expand...
Wait, do you use something like icanhazip.com? Nord would need the real value, not what the router thinks is its WAN IP.
 
iTyPsIDg said:
DNS caching means it needs to happen relatively quickly. If the change to SmartDNS doesn't happen before the DNS result ages out, then you won't be able to reach Nord to make the change.
Click to expand...
If it checks for a change every 60 seconds (by default), do you think that would be enough, or should it be checked every second? I'm not familiar (nor do I seem to have this issue) with dns caching timing out like this... And is there a process to "change to SmartDNS"? Or is it just a matter of killing the VPN, and re-establishing it?

iTyPsIDg said:
Wait, do you use something like icanhazip.com? Nord would need the real value, not what the router thinks is its WAN IP.
Click to expand...
I use icanhazip.com to report the public VPN IP on the main UI... it does differ slightly from the one that the router keeps track of... but shouldn't be a problem for the WAN IP.
 
Viktor Jaep said:
If it checks for a change every 60 seconds (by default), do you think that would be enough, or should it be checked every second? I'm not familiar (nor do I seem to have this issue) with dns caching timing out like this... And is there a process to "change to SmartDNS"? Or is it just a matter of killing the VPN, and re-establishing it?
Click to expand...
I'm certain that 60 seconds is fast enough. The second part is what I'm not sure of. I haven't found very good documentation on their API so that I could try to find what happens when changing the IP for SmartDNS. Here is the option in the GUI:
1676324498664.png

Viktor Jaep said:
I use icanhazip.com to report the public VPN IP on the main UI... it does differ slightly from the one that the router keeps track of... but shouldn't be a problem for the WAN IP.
Click to expand...
That's perfect then. When I wrote this, I was looking at RTRMON because of the Nord DNS issue that caused VPNMON to keep looping.
 
iTyPsIDg said:
I'm certain that 60 seconds is fast enough. The second part is what I'm not sure of. I haven't found very good documentation on their API so that I could try to find what happens when changing the IP for SmartDNS. Here is the option in the GUI:
Click to expand...
That might be a problem. I reached out to support to find out if there are any automated ways of updating this value.
 
iTyPsIDg said:
I'm certain that 60 seconds is fast enough. The second part is what I'm not sure of. I haven't found very good documentation on their API so that I could try to find what happens when changing the IP for SmartDNS. Here is the option in the GUI:
Click to expand...
Nordvpn support is acting dumb about this. There seems to be no way to manipulate this other than manually, after logging into your own account. :(
 
Ugh, well thanks for checking.
 
You must log in or register to reply here.

Similar threads

Viktor Jaep
VPNMON VPNMON-R2 v2.65 -Jan 27, 2024- DISCONTINUED - Upgrade to VPNMON-R3 Available! (#3)
6 7 8
Replies
144
Views
22K
Viktor Jaep
Viktor Jaep
Viktor Jaep
VPNMON VPNMON-R3 v1.3.8 -Nov 28, 2024- Monitor WAN/Dual-WAN/OpenVPN Health & Reset Multiple OpenVPN Connections (Now available in AMTM!)
13 14 15
Replies
292
Views
45K
Viktor Jaep
Viktor Jaep
Viktor Jaep
TAILMON TAILMON v1.0.20 -July 27, 2024- WireGuard-based Tailscale Installer, Configurator and Monitor (Now available in AMTM!)
Replies
5
Views
663
jksmurf
J
Viktor Jaep
TAILMON TAILMON v1.0.20 -July 27, 2024- WireGuard-based Tailscale Installer, Configurator and Monitor (THREAD #1 CLOSED)
26 27 28
Replies
556
Views
66K
XIII
XIII
Viktor Jaep
VPNMON VPNMON-R2 v2.0 -Jul 10, 2022- Monitor your VPN connection's Health (Thread locked/closed)
23 24 25
Replies
499
Views
57K
Viktor Jaep
Viktor Jaep
Similar threads
Thread starter Title Forum Replies Date
Ripshod (Not specifically) VPNMON-R3 1.11 failure domino effect Asuswrt-Merlin AddOns 20

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 628 (members: 13, guests: 615)
Top