Arch Linux User Repository

The strace output shows that the nordlayer-resolvconf process is attempting to execute a setuid(0) system call and is failing with EPERM (Operation not permitted). This indicates that the process is trying to gain root privileges, but it's being denied.

I fixed with:

sudo setcap 'CAP_NET_ADMIN=+eip' /usr/libexec/nordlayer/nordlayer-charon
sudo setcap 'CAP_NET_ADMIN=+eip' /usr/libexec/nordlayer/nordlayer-ip
sudo setcap 'CAP_NET_ADMIN=+eip' /usr/libexec/nordlayer/nordlayer-openvpn
sudo setcap 'CAP_NET_ADMIN+eip CAP_DAC_OVERRIDE+eip CAP_SETUID+eip' /usr/libexec/nordlayer/nordlayer-resolvconf
sudo setcap 'CAP_NET_ADMIN=+eip' /usr/libexec/nordlayer/nordlayer-setcap
sudo setcap 'CAP_NET_ADMIN=+eip' /usr/bin/nordlayer

Remember to also run:

sudo usermod -a -G nordlayer $(whoami)

And then reboot.

PS: I have updated my fork to 3.1.0, and it can be found here: https://github.com/akumaburn/nordlayer-latest

Pull request is open here: https://github.com/Sidicer/nordlayer/pull/15

I wasn't able to connect using 3.0.0 at all - downgrading to 2.6.5 helped, and I was able to connect instantly.

Edit: I recommend to uninstall 3.0.0 and make sure the config files are deletedl, and then install 2.6.5.

I'm not really sure what causes it but if you run into troubles of connecting to your server, try restarting nordlayer.service before connecting. I disabled autostarting the service, start it in my custom connect script, and stop it in my disconnect script, same idea. I also had multiple (50+ actually) nlx network devices listed with ip addr. They were removed by restarting the service, and after that I was able to connect again.

As I will not be actively using nordlayer after November 3rd - I am looking for someone who would like to take ownership of this package.

Get in touch with me through https://github.com/Sidicer/nordlayer and I will provide all the details in forking, how to update the package and how to take ownership in AUR.

@netwalker yeah this happens when using non-standard drivers that cannot report an OpenState. (all drivers can report administrative state UP/DOWN but some can't and turns out it's actually optional). non-standard (=not so common network cards)

also happens when trying tethering because it won't go through a physical interface

Hi. After upgrading to version 2.6.5, I'm getting 'no active link' when trying to connect to any gateway. Already tried removing nordlayer.db an restarting the service, but no success. Am I missing something? Thanks for maintaining the package. :)

Hotfix (Version 2.6.5) released by Nordlayer

The new version should not break nordlayer.db

# Run this if you are unable to use nordlayer after upgrade to 2.6.5
rm /var/lib/nordlayer/nordlayer.db
systemctl restart nordlayer
nordlayer login

# Run this if you are unable to use nordlayer after upgrade to 2.6.4
rm /var/lib/nordlayer/nordlayer.db
systemctl restart nordlayer
nordlayer login

Hi @sidicer,
Thank you so much for taking this responsibility.
If anytime, I can be of help, then please do let me know.
Thanks a lot :)

Will be maintaining this package from now on. https://github.com/Sidicer/nordlayer Thank you, mearaj, for the work!