Answering my comment from 2023-10-07 14:20 (EDT) I found the culprit.
Some new "improvements" in 3.16.6 require using new kernel modules. Since I build my own kernel based off of modprobed-db I couldn't track this.
I found by making sure the following modules are built into the kernel everything works fine:
amdxcp
chacha_x86_64
curve25519_x86_64
drm_suballoc_helper
gf128mul
ip6table_filter
ip6table_mangle
ip6table_nat
ip6table_raw
ip6_tables
ip6table_security
ip6_udp_tunnel
libchacha
libchacha20poly1305
libcurve25519_generic
poly1305_x86_64
qrtr
rapl
snd_intel_sdw_acpi
udp_tunnel
wireguard
xt_conntrack
I will narrow this down to the exact specific ones but if I would have to take a guess, I would believe a smaller list could be:
ip6table_filter
ip6table_mangle
ip6table_nat
ip6table_raw
ip6_tables
ip6table_security
ip6_udp_tunnel
qrtr
udp_tunnel
wireguard
xt_conntrack
The last 3 have a very high probability to be required now and the last one a super high probability as it's mentioned in the systemd error. The IP6 ones I don't think so, my IPv6 is disabled so I can't imagine Nordvpn requiring these modules when IP6 is disabled, but you never know!
You learn everyday.... :)
Pinned Comments
Mxzcabel commented on 2023-03-23 20:37 (UTC) (edited on 2025-05-12 22:12 (UTC) by Mxzcabel)
"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.20.2-4
Dependency included as mandatory earlier as community request.
If you're late for the party and only had updated up to 3.20.2-2.1:
If you're coming from Manjaro or e.g another Arch-based distro with no stable libxml2-legacy package just yet:
Note from 3.20.2-3
There is now a new package from official repositories named libxml2-legacy and with it two fresh considerations:
Despite the fact libxml2-legacy was included as optional, it is actually a mandatory dependency. This will change on next NordVPN's release if the legacy support remains.
This release only removes the previous symbolic link and purges the file within NordVPN library directory, otherwise it would result in an error before installation/upgrade.
Note from 3.20.2-2.1
A patch have been implemented due the absence of libxml2.so.2 after package upgrade to 2.14.2. This fix is not useful if:
You plan to keep your system update to a specific date until NordVPN officially uses the new library.
You are from a different distribution, which is a Arch-based one with other repositories, and libxml2 is not yet upgraded.
Note from 3.19.1:
The repository's hierarchy has been updated and a slightly divergence comes with it. It was from:
/debian/pool/main
To now as:
/debian/pool/main/n/nordvpn
Any previous commits you may like to try in the future will need a manual mediation to replace old links in favor of the new ones.
Note from 3.19.0:
This version introduces new libraries being used by NordVPN. I have created symbolic links and committed a patch for it not interposing with already existing libraries (like sqlite3). Although this is not a big deal, If you, however, upgraded nordvpn-bin before the fix and noticed some library-related issue from sqlite lately, I suggest reinstalling the affected package.
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 1Also 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:
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.
martoko commented on 2020-12-20 09:10 (UTC) (edited on 2020-12-20 09:12 (UTC) by martoko)
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 nordvpndYou might not have been added to the nordvpn group
Add yourself:
sudo gpasswd -a USERNAME nordvpnAnd then restart in order for the group to be created:
reboot