29

I'm using nordvpn CLI on Ubuntu for quite a while but, since a few days, when I'm trying to reach any other client in my local network, I'm getting e.g. the following problem:

$ ping 192.168.178.1
PING 192.168.178.1 (192.168.178.1) 56(84) bytes of data.
ping: sendmsg: Operation not permitted

where 192.168.178.1 is my router. When I disconnect from NordVPN I can reach other clients again.

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.

As it might be helpful, here my nordvpn settings:

$ nordvpn settings
Technology: OpenVPN
Protocol: UDP
Kill Switch: disabled
CyberSec: disabled
Obfuscate: disabled
Notify: enabled
Auto-connect: disabled
DNS: disabled

Might be that it's something quite stupid or easy to resolve, but I'm struggling with that for a few days now.

cocomac
  • 3,894
ShEepCr3eper
  • 393

3 Answers3

68

Same same. I thought maybe it was a bug in the app, but 3.8.5 is the same.

My settings (which worked several nordvpn app versions ago):

Technology: NordLynx
Kill Switch: disabled
CyberSec: disabled
Notify: enabled
Auto-connect: enabled
DNS: 1.0.0.1, 1.1.1.1

Resolution (Later)

Hahaha! Got it! Whitelist your internal. Mine is 192.168.2.xxx, adjust yours accordingly.

nordvpn whitelist add subnet 192.168.2.0/24
Thomas Vincent
  • 123
kmassner
  • 696
  • 1
    Great, that really worked! Thank you.

    Though I'm wondering that it worked before and they changed it without saying something...

     – ShEepCr3eper Sep 26 '20 at 08:53
  • 1
    wow so much nonsense about this on searches and only 2 upvotes on the correct answer! not many people running nord and sshing around on linux eh :(

    Thanks so much!! Wish they did this automatically since its kind of expected ..

     – Leathan Nov 30 '20 at 02:39
  • Thank you, you're the man! – BugSquanch Apr 12 '22 at 11:03
  • 1
    nordvpn does not make this obvious or easy. First, the whitelist command is buried in a set of recommended provisioning steps in the installation guide. Second it provides the "allowlisting" function and the "whitelist" token is not found in the nordvpn help section. Anyway, this provides the functionality I need. – dturvene Sep 07 '23 at 12:28
  • worked like a charm. this should be accepted, one-liner answer. – FlyingZebra1 Oct 01 '23 at 00:39
  • for years this worked for me, until today, since latest update this doesn't work as expected. Instead I do the following: $ nordvpn set lan-discovery on – FrankyHollywood May 12 '24 at 20:16
  • whitelisting stopped working for me with the linux deb pkg, so I purged the installation, then reinstalled using the nordvpn snap, and enabled lan-discovery and it started working again (but it could just be the reinstall fixed a bad config) – michael Oct 18 '24 at 06:07
10

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 command nordvpn set dns 192.168.50.1

lazzerruss
  • 101
0

The other answers did not work for atahualpa. They posted an answer inside their question. I am copying it below:

You need to enable "LAN discovery". So at the command line type this:

nordvpn set lan-discovery enable

And afterword nordvpn settings will show the following line:

LAN Discovery: enabled

This worked for me.

user68186
  • 37,795