Warning: the iproute2 package has updated from version 6.4.0 to 6.5.0, and with it the default rt_tables location has changed from /etc/iproute2/rt_tables to /usr/lib/iproute2/rt_tables. I've rolled out a fix for this change in the latest version. When updating your package, please remove the package, and then reinstall it, so that everything in the piavpn-bin.install gets re-run. You will need to re-run 'sudo systemctl enable --now piavpn.service'
Search Criteria
Package Details: piavpn-bin 1:3.6.1-4
Package Actions
Git Clone URL: | https://aur.archlinux.org/piavpn-bin.git (read-only, click to copy) |
---|---|
Package Base: | piavpn-bin |
Description: | Private Internet Access client |
Upstream URL: | https://privateinternetaccess.com/ |
Keywords: | private-internet-access vpn |
Licenses: | custom |
Conflicts: | pia-launch, pia-manager, pia-tools, private-internet-access-vpn |
Provides: | piavpn |
Submitter: | solsticedhiver |
Maintainer: | lobroc (solsticedhiver) |
Last Packager: | lobroc |
Votes: | 24 |
Popularity: | 0.118638 |
First Submitted: | 2020-04-14 15:32 (UTC) |
Last Updated: | 2024-11-24 23:42 (UTC) |
Dependencies (5)
- libnl (libnl-gitAUR)
- libxkbcommon-x11 (libxkbcommon-x11-gitAUR)
- zip (zip-natspecAUR)
- libcap (make)
- WIREGUARD-MODULE (linux-mainline-anbox-gitAUR, linux-sgxAUR, wireguard-dkmsAUR, linux-xanmod-rt510AUR, linux-yoga9AUR, linux-lts510-nvme-fixAUR, linux-zen-515ltsAUR, linux-ck-ltsAUR, linux-covolunablu-gamingAUR, linux-hdr-gitAUR, wireguard-module-gitAUR, linux-clear-binAUR, linux-lts-huawei-amd-audioAUR, linux-huawei-amd-audioAUR, linux-ranghoAUR, linux-clear-lts2021AUR, linux-clear-lts2020AUR, linux-clear-lts2019AUR, linux-clear-lts2018AUR, linux-lts-515-gitAUR, linux-intel-lts-sriovAUR, linux-kamakiriAUR, linux-hardened-gitAUR, linux-clear-ltscurrentAUR, linux-ath-dfsAUR, linux-jcoreAUR, linux-clear-cjkttyAUR, linux-echoAUR, linux-babyAUR, linux-clear-preempt-rtAUR, linux-manjaro-xanmodAUR, linux-zencjkAUR, linux-gitAUR, linux-amd-colorAUR, linux-clear-ltsprevAUR, linux-rt-lts61AUR, linux-intelAUR, linux-amdAUR, linux-amdvcnfixAUR, linux-sched-ext-gitAUR, linux-tip-gitAUR, linux-zen-pdsAUR, linux-zen-bmqAUR, linux-multimediaAUR, linux-rcAUR, linux-boreAUR, linux-llvmAUR, linux-eevdfAUR, linux-intel-alderlakeAUR, linux-amd-znver2AUR, linux-lts-amd-bc250AUR, linux-xanmod-gitAUR, linux-ckAUR, linux-hardened-ltsAUR, linux-bnx2x-2.5gAUR, linux-cachyos-serverAUR, linux-shmileeAUR, linux-cachyos-bmqAUR, linux-lts-bnx2x-2.5gAUR, linux-rustAUR, linux-clear-cjktty-zfsAUR, linux-neptune-65AUR, linux-flowx13AUR, linux-amd-drm-nextAUR, linux-mainline-um5606AUR, linux-g14AUR, linux-vfioAUR, linux-lts510AUR, linux-lts61AUR, linux-lts66AUR, linux-xanmod-boreAUR, linux-cachyosAUR, linux-cachyos-boreAUR, linux-cachyos-eevdfAUR, linux-cachyos-hardenedAUR, linux-cachyos-ltsAUR, linux-xanmod-binAUR, linux-mainlineAUR, linux-clearAUR, linux-next-gitAUR, linux-cachyos-rcAUR, linux-fsync-nobara-binAUR, linux6.13.1.arch1-1-binAUR, linux6.12.12-1-lts-binAUR, linux6.13.1.zen1-1-zen-binAUR, linux6.12.10.hardened1-2-hardened-binAUR, linux-pfAUR, linux-lts515AUR, linux-amd-staging-drm-next-gitAUR, linux-drm-next-gitAUR, linux-drm-intel-next-gitAUR, linux-lqxAUR, linux-nitrousAUR, linux-xanmodAUR, linux-xanmod-edgeAUR, linux-xanmod-ltsAUR, linux-xanmod-rtAUR, linux-amd-drm-fixesAUR, linux-bcachefs-gitAUR, linux-amd-gitAUR, linux-drm-tip-gitAUR, linux-xanmod-anboxAUR, linux-vfio-ltsAUR, linux-gaokun3AUR, linux-libreAUR, linux, linux-hardened, linux-lts, linux-rt, linux-rt-lts, linux-zen) (optional) – to use the wireguard kernel module instead
Required by (0)
Sources (2)
lobroc commented on 2023-09-20 15:26 (UTC) (edited on 2023-09-20 15:30 (UTC) by lobroc)
lobroc commented on 2023-09-05 20:21 (UTC)
You are not supposed to directly write into or change /etc/resolv.conf, as it's frequently overwritten by running programs, as mentioned before. This is widely-used practise by many tools on Linux. When you've ssh'ed into a machine, you can start the client at the location stated in @Arvid's comment from 18/02/23. Good luck!
genji commented on 2023-09-04 16:27 (UTC)
I tried doing 'chattr +i /etc/resolv.conf' as per the instructions on the ArchLinux BBS, but that actually broke piactl altogether. When it can't overwrite your /etc/resolv.conf it decides it will not even attempt to start! Just crazy
I just installed Xorg, which is the graphical client I should be trying to load? Is it a seperate package somewhere, or is it already on my machine ready to be launched?
Thanks again
lobroc commented on 2023-09-04 15:16 (UTC)
All of the settings you are referring to are unfortunately only able to be changed via the graphical client, but they can be.
If you are using the command line only because you are connecting to a remote server, you can use ssh -X user@host
to forward the GUI and change your settings that way.
Also, /etc/resolv.conf is often automatically generated / overwritten by programs (see NetworkManager for example), and so it's no surprise that PIA does this too.
genji commented on 2023-09-04 14:57 (UTC)
Thank you @lobroc I made a mistake by enabling the service at first and not explicitly starting it, appreciate the response.
I am here with one new remaining problem though. 'piactl connect' is overwriting /etc/resolv.conf with it's own nameserver, and I cannot figure out how to change this setting! The 'piactl' client itself is one of the worst of any VPN provider I've ever used - missing all the most common features like kill switches, auto-connect, and DNS servers.
Even when I manually change /etc/resolv.conf as long as piactl is running, it overwrites it again less than 5 seconds later!
Hideous!
lobroc commented on 2023-09-04 14:12 (UTC)
Have you, by chance, @genji, forgotten to enable the daemon's service, as per the pinned comment?
genji commented on 2023-09-04 03:10 (UTC)
I need help with this!
I managed to get it installed using yay, but piactl commands just seem to freeze and then exit with "Timed out after 5 seconds"
I increased timeout to 120 seconds, and it just hangs for 120 seconds and exits with the same error.
What gives? I have no outstanding network problems that I'm aware of. Internet connectivity is working perfectly on the machine - yet piactl stalls out.
Is this some problem with a hidden daemon somewhere?
Help!
BWildered01 commented on 2023-07-15 18:35 (UTC)
Thank you for the fix. I did mention that issue here, and my specific use case doesn't require me to update too often, so only seeing yours changes now. https://aur.archlinux.org/packages/piavpn-bin?O=10#comment-835193
solsticedhiver commented on 2023-03-02 23:21 (UTC)
We just pushed a new build to fix the aarch64 package. It was finally discovered that it was the x86_64 binaries that were packaged instead of the aarch64 ones (oops)
Arvid commented on 2023-02-18 00:39 (UTC) (edited on 2023-02-18 01:07 (UTC) by Arvid)
The client is here:
/opt/piavpn/bin/pia-client
Pinned Comments
lobroc commented on 2023-09-20 15:26 (UTC) (edited on 2023-09-20 15:30 (UTC) by lobroc)
Warning: the iproute2 package has updated from version 6.4.0 to 6.5.0, and with it the default rt_tables location has changed from /etc/iproute2/rt_tables to /usr/lib/iproute2/rt_tables. I've rolled out a fix for this change in the latest version. When updating your package, please remove the package, and then reinstall it, so that everything in the piavpn-bin.install gets re-run. You will need to re-run 'sudo systemctl enable --now piavpn.service'
Arvid commented on 2023-02-18 00:39 (UTC) (edited on 2023-02-18 01:07 (UTC) by Arvid)
The client is here:
/opt/piavpn/bin/pia-client
solsticedhiver commented on 2023-02-17 19:16 (UTC) (edited on 2023-02-17 19:41 (UTC) by solsticedhiver)
You need to enable and start piavpn.service. Run
sudo systemctl enable --now piavpn.service
Then pia-client will complete the quick tour guide, and let you login.