Add missing armel architecture. It's for RPI1 and RPI zero devices (devices with armv6 architecture).
It's also provided by NordVPN: https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/
Git Clone URL: | https://aur.archlinux.org/nordvpn-bin.git (read-only, click to copy) |
---|---|
Package Base: | nordvpn-bin |
Description: | NordVPN CLI tool for Linux |
Upstream URL: | https://nordvpn.com/download/linux/ |
Keywords: | networking nordvpn openvpn security vpn |
Licenses: | GPL3 |
Conflicts: | openvpn-nordvpn |
Provides: | nordvpn |
Submitter: | metiis |
Maintainer: | Mxzcabel |
Last Packager: | Mxzcabel |
Votes: | 168 |
Popularity: | 0.96 |
First Submitted: | 2018-08-29 12:13 (UTC) |
Last Updated: | 2024-11-21 01:21 (UTC) |
« First ‹ Previous 1 .. 37 38 39 40 41 42 43 44 45 46 47 .. 54 Next › Last »
Add missing armel architecture. It's for RPI1 and RPI zero devices (devices with armv6 architecture).
It's also provided by NordVPN: https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/
Anyone else having problems with autoconnect? Any hint on how to solve this issue? Also, I suspect that the killswitch is not working as it should. For example, if I disconnect from nordvpn after a while my downloads resume.
@Martoko That link resolved my issue. If anyone else has the problem, I was needed to install linux headers and select my kernel.
sudo pacman -S linux-headers
Thanks!
@JRO012 I do not have Manjaro installation right now, but a quick Google search revealed the following pages of interest Arch Linux wiki on WireGuard, Blog post detailing how to install WireGuard for Manjaro
@erkexzcx "we" are not refusing anything. Metiis is the one with the power to make you a maintainer, and AFAIK he is not even aware of your comments.
We welcome any suggestions on how to update the PKGBUILD. Examples include jackhistoria's suggestion of adding WireGuard as a dependency and your suggestion of creating a script to automatically update. Both suggestions have been implemented.
In the future, please refrain from general statements, such as "they don't even know how to maintain this", and instead highlight specific issues, such as "why isn't wireguard added as a dependency".
@JRO012 they don't even know how to maintain this. It was described by NORDVPN about new requirwd dependencies of new release, but they refuse to help me update this PKGBUILD.
Very new to all this and I have an error. When I try to Nordvpn set technology NordLynx, I get "Missing NordLynx kernel module or configuration utility." I have wireguard-dkms and wireguard-tools installed. Any help is appreciated (also if this isn't the place to request help, let me know and I'll delete this post).
Dell XPS 13 9360 Operating System: Manjaro Linux Kernel: Linux 4.19.62-1-MANJARO Architecture: x86-64
@erkexzcx what I meant to say was that I am a co-maintainer. I have written a script like you talked about and I have set it to run daily. If I have missed anything in my script feel free to make a pull request, otherwise the problem of the package being constantly out of date because of minor changes should be fixed now. Thank you for offering your help.
@Martoko i am not doing anythink by now. First I would like to be a maintainer, otherwise spending time would be useless.
@erkexzcx I can't make you a maintainer (AFAIK only metiis can), but here is a script that I've written Martoko/maintain-nordvpn-bin, feel free to make a pull request with improvements or suggestions.
Thanks for the tip, jackhistoria.
FYI anyone curious about the wireguard stuff on previous post, see here: https://nordvpn.com/blog/nordlynx-protocol-wireguard/
Follow these steps to switch to NordLynx: Install WireGuard. Open the terminal and enter ‘nordvpn set technology NordLynx’. Enter ‘nordvpn c’ to connect to VPN.
Pinned Comments
Mxzcabel commented on 2023-03-23 20:37 (UTC) (edited on 2024-11-21 01:57 (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.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 1
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:
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 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