Arch Linux User Repository

"Please, do not flag this package as out-of-date until there's the official release on Github page."

"Maybe the announcement is delayed, but wait for some other possible forward release, which is patching the previous one before the actual publishing."

Note from 3.17.4v:

The previous bug exposing DNS servers is fixed.

Note from 3.17.3v:

Caution! This version needs heed while using it and should be avoided. I strongly advice downgrading to 3.17.2 and wait for a new version or patching. Some big problems are:

• There's DNS leak present. Your original ISP servers can be exposed, as reported already on #343 issue.

• Unable to connect on nordvpn servers. Your journal might show the follow output: networker setting dns: setting dns with resolvectl: setting dns with resolvectl: Failed to set DNS configuration: Could not activate remote peer: activation request failed: unknown unit.: exit status 1

  After restarting resolve with systemctl restart systemd-resolved.service you may get it working again, enough for connecting normally, as reported, but not exclusively an ARM platform issue, on #342.

Also huge thanks for the community warnings in prior comments before I could've noticed all.

Note from 3.16.2v:

As the published note from the version above has mentioned on Github's page:

• Logging in with a username and password is no longer available in the terminal.

Please, consider using a token to logging in from now on.

Note from 3.16.0v:

The 'countries.dat' may differ between versions. Be aware to remove the file before upgrading the package.

If you're seeing the message "Daemon is unreachable, is systemd running?", then one of two things is probably happening.

The nordvpn daemon might not be started
Start it using:
sudo systemctl enable --now nordvpnd

You might not have been added to the nordvpn group
Add yourself:
sudo gpasswd -a USERNAME nordvpn
And then restart in order for the group to be created:
reboot

@tito480 Try: nordvpn set obfuscate enable

I think Obfuscate is not working:

nordvpn set obfuscate 1 Command 'obfuscate 1' doesn't exist.

@alogim The kill-switch only works after you are connected to a server. After you connect to a server it will apply the iptables, and only then if you lose internet, will it be blocked.

@alogim The package is a repack of the official app. As nordvpn is a paid service - you should use their bugtracker/forum/issues platform to report it.

I noticed that even though KillSwitch is enabled, still I can browse the Internet without problems when NordVPN is not connected. My current settings: Technology: OpenVPN Protocol: TCP Kill Switch: enabled CyberSec: disabled Obfuscate: disabled Notify: enabled Auto-connect: enabled DNS: disabled

Is there any fix?

@Martoko / @erkexzcx, thank you for collaborating together to help improve this package. Well done!

@Martoko here is the list:

amd64 = x86_64
arm64 = aarch64
armel = arm & armv6h
armhf = armv7h
i386 = i686

Also feel free to use my written in Go app to generate PKGBUILD: https://pastebin.com/t1VY1AWe

sudo pacman -S go
go get github.com/PuerkitoBio/goquery
wget https://pastebin.com/raw/t1VY1AWe -O app.go
go build app.go
./app

Also, I would like to share my computing power to schedule automated script to update this AUR package. Let me know if needed.

EDIT: My bad, in the golang code I accidentally left nordvpn-cli rather than nordvpn-bin. Change before compiling.

I have updated the package.

The mapping between how Debian names arm architectures and how Arch Linux names arm architectures does not seem to be documented anywhere, so I made a few qualified guesses here:

armel -> armv6h
armhf -> armv7h
arm64 -> aarch64

If anyone can confirm or deny the above mappings, it would be most appreciated.

Is it possible to update this to 1.0.0? Thank you!

@erkexzcx For the moment, no options. If the package is actually unmaintained, adopting it. If the maintainer updates and somehow outright refuses to include armv6, MAYBE nordvpn-armv6 but I'm not a TU and have little to none knowledge about a case like this, so I would discuss it with a TU beforehand ESPECIALLY given your past. In most cases you'd probably just live with it and makepkg -A but I know it doesn't work for this exact package. Using a local PKGBUILD is always an option.