Nordvpn 6.33.10 Download
Dibe Naro
I already read about similar problems being related to the nordvpn killswitch, but it is disabled and I also tried to enable and then to disable it.I also tried to disable the ufw, and reinstalled nordvpn but that didn't help either.
Whitelisting my subnets only allowed me to make connections using IP addresses. I'm lazy and prefer hostnames. So I had to add my DNS server (my router) to the Nordvpn configuration. My router is at 192.168.50.1. So I used the commandnordvpn set dns 192.168.50.1
I downloaded nordvpn-bin from AUR and I suspect this version is doing something that is messing with the ability to use a machine as a gateway, as I do with all my other VPN services. For some reason just Nord in particular isn't working as expected.
- Internet forwarding seems to be working fine - client phone for testing using 192.168.0.200 as a gateway working for all traffic
- # systemctl start nordvpn
- use nordvpn CLI to login and then connect
- Connectivity on the server itself is all good, opening IP check page shows the VPN IP and everything is all as intended
Yikes, yeah I wouldn't know where to begin here in trying to do this myself. This issue is still unresolved and I think it has something to do with however nordvpn is configuring itself, as I have multiple identical VM's here acting as gateways for other major providers and none have this issue - it's exclusive to the nord gateway sadly
So it's absolutely something that the software is doing. They changed something along the way and I forget where I read about it but there was just a one-off random comment in all of the research I was doing on reddit from a guy claiming he couldn't get some feature to work on the newest nordvpn release and had to downgrade. The second I dropped back to 3.15.0 it works absolutely perfectly, using it as we speak with zero problems, and zero frustration.
Strange stuff indeed. I think disabling routing in the newest version and issuing the proper set of commands would be great, just not sure how to begin really.. I wish there was a way to reach someone that mattered at nordvpn about this. I see their tool is on github.
I worked out that if I downgrade to an earlier nordvpn version the offending iptables command that is unsupported by the Microsoft WSL kernel is not issued and I can extract the credentials as in the guide.
My firewall is blocking all the sessions from nordvpn but it still consumes the data. The attached screenshot is of 24hr activity even my servers are shutdown but it is making sessions with my complete IP Pool.
1- check network setting in the nordvpn template, you need to click 'show more settings' to see this and remember if you access your router settings page on 192.168.100.1 then your network setting would be 192.168.100.0/24 (google CIDR notation for more)
4- The only setting to change on the nzbGET docker config page is the network, if nzbget worked before then just change the network settings. To do this, select Advanced View, select 'None' for network type and add only the following text to Extra Parameters '--net=container:nordvpn'
08ab062aa8