I didn't get any errors before, just when I hit the S key the screen reloaded but didn't display the menu
Are you able to reach https://ipv4.icanhazip.com from your router? If not, you may need to whitelist it? That's a necessary ingredient in determining tunnel health.
Yea sorry I thought I saved my edit earlier but I guess I didn't. I ended up solving it by upping the timeout to 6 instead of 3 for that curl to icanhazip.com. Over the VPN is just over 3 seconds for whatever reason.
Thanks for the info... I'll make a change in the next version to show this:
ICANHAZIP=$(curl --silent --retry 3 --connect-timeout 6 --max-time 6 --retry-delay 1 --retry-all-errors --fail --interface $TUN --request GET --url https://ipv4.icanhazip.com) # Grab the public IP of the VPN Connection
curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R3/main/vpnmon-r3-1.1.5.sh" -o "/jffs/scripts/vpnmon-r3.sh" && chmod 755 "/jffs/scripts/vpnmon-r3.sh"curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R3/main/vpnmon-r3.sh" -o "/jffs/scripts/vpnmon-r3.sh" && chmod 755 "/jffs/scripts/vpnmon-r3.sh"Sorry... OpenVPN only at this moment.
).
Yes it appears to be fine by itself.
Sure, just pop over the commands where req'd and I'll try them out (though I'm not super technical so might throw some questions back to take things forward
DNSResolver="$({ unbound-control flush whoami.akamai.net >/dev/null 2>&1; } && dig whoami.akamai.net +short @"$(netstat -nlp 2>/dev/null | awk '/.*(unbound){1}.*/{split($4, ip_addr, ":");if(substr($4,11) !~ /.*953.*/)print ip_addr[1];if(substr($4,11) !~ /.*953.*/)exit}')" -p "$(netstat -nlp 2>/dev/null | awk '/.*(unbound){1}.*/{if(substr($4,11) !~ /.*953.*/)print substr($4,11);if(substr($4,11) !~ /.*953.*/)exit}')" 2>/dev/null)"
echo $DNSResolver
dnscheck.tools
Just set everything back up with Unbound this afternoon... continuing to experience issues. I'm starting to wonder if NordVPN made a change.
I just got AirVPN running on my router, and will be testing this in a bit to see if it works there.
@Ventola EDIT: I've had success with the Unbound integration using AirVPN... so it must be a NordVPN issue. A few days ago, they made some major changes and did away with a bunch of public APIs in the name of security... it was around this time that my Unbound integration stopped working through NordVPN, and experienced the same kinds of issues you are facing. Unless something changes in the near future, it doesn't sound like Nord is going to be a viable option moving forward. ;( What a sad state of affairs... I have tried dealing with their support, but their support team is probably one of the VERY worst I've ever come across. They don't seem to have a clue what you're talking about or what to recommend for a fix. You're welcome to give it a shot, but I have a feeling they're just going to point you to some generic link on their website and brush you off like they always do.
.
DNSResolver="$({ unbound-control flush whoami.akamai.net >/dev/null 2>&1; } && dig whoami.akamai.net +short @"$(netstat -nlp 2>/dev/null | awk '/.*(unbound){1}.*/{split($4, ip_addr, ":");if(substr($4,11) !~ /.*953.*/)print ip_addr[1];if(substr($4,11) !~ /.*953.*/)exit}')" -p "$(netstat -nlp 2>/dev/null | awk '/.*(unbound){1}.*/{if(substr($4,11) !~ /.*953.*/)print substr($4,11);if(substr($4,11) !~ /.*953.*/)exit}')" 2>/dev/null)"
You could try adjusting the dig command to@dave14305 @Martineau @SomeWhereOverTheRainBow ... I was wondering if any of you would happen to know what NordVPN could have done on their end to prevent Unbound from acting as a resolver across a VPN tunnel? Up until a few days ago, this was working for years. They recently made a change that disabled the ability to utilize certain public APIs, and have a feeling that the deprecation of this feature was rolled into it as well.
I would like to go back to their support, yank their chains a bit, and ask them to consider reversing what they did here... I would love to know what I could use to go at them with... Like, could they be preventing certain port traffic from getting blocked at their VPN endpoint that prevents other services from determining what your DNS resolver is, like https://dnscheck.tools/ ? Unbound itself is no longer able to resolve anything for me in this configuration. I'm using this statement in my script (below with many thanks to @SomeWhereOverTheRainBow for his help on this) to check if the VPN endpoint IP matches the DNS Resolver, and like I said, worked for years... but neither of these tools function or show your VPN endpoint as your DNS resolver any longer when Unbound is used with NordVPN in this fashion. I just tried this on AirVPN, and it works just fine there.
Code:DNSResolver="$({ unbound-control flush whoami.akamai.net >/dev/null 2>&1; } && dig whoami.akamai.net +short @"$(netstat -nlp 2>/dev/null | awk '/.*(unbound){1}.*/{split($4, ip_addr, ":");if(substr($4,11) !~ /.*953.*/)print ip_addr[1];if(substr($4,11) !~ /.*953.*/)exit}')" -p "$(netstat -nlp 2>/dev/null | awk '/.*(unbound){1}.*/{if(substr($4,11) !~ /.*953.*/)print substr($4,11);if(substr($4,11) !~ /.*953.*/)exit}')" 2>/dev/null)"
If you have anything of substance that I can use to persuade them with, I'd love to hear your feedback on this!
dig +short A whoami.akamai.net @"$(netstat -nlp 2>/dev/null | awk '/.*(unbound){1}.*/{split($4, ip_addr, ":");if(substr($4,11) !~ /.*953.*/)print ip_addr[1];if(substr($4,11) !~ /.*953.*/)exit}')" -p "$(netstat -nlp 2>/dev/null | awk '/.*(unbound){1}.*/{if(substr($4,11) !~ /.*953.*/)print substr($4,11);if(substr($4,11) !~ /.*953.*/)exit}')" 2>/dev/null)"
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!
