Arch Linux User Repository

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'

The client is here:

/opt/piavpn/bin/pia-client

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.

Most of the time, that dependency is provided by the kernel you have installed. You can check that with pacman.

If it is not, you have to install additionnial package from aur, like wireguard-dkms, or wiregard-module-git

You need the WIREGUARD-MODULE dependency if you want to use the module in the kernel, when you checked the 'Use kernel module' in piavn settings (which is by default I think ?)

Otherwise, this is not needed if you unchecked the checkbox.

Note: you can see what package provides 'WIREGUARD-MODULE' just above, in the dependencies box.

Apologies if this is an obvious question, but I cannot seem to find the answer to it (maybe because I do not know the right query terms).

How does one install the optional WIREGUARD-MODULE dependency?

Thank you very much in advance!

I am just repackaging the .run downloaded from privateinternetaccess.com. So it is the same and should be ok. It is working for me.

If you have any problem, please provide a pastebin link of your log with the problem visible.

Also, right now, the package is not compatible aarch64 (rpi4/archlinuxarm). I can make it but I will not be able to test it.

Same as WiLL-iAm. This package failed, but running ./pia-linux-3.1.2-06767.run worked just fine.

piavpn-bin installed fine but became stuck on "connecting" to any PIA server region I tried after providing the login credential file. Believe I was hitting the same bug as theriddick below. Like BWildered01, downloading and installing the .run file straight from privateinternetaccess.com did actually work.

Hello, I had to use 'https://installers.privateinternetaccess.com/download/pia-linux-arm64-3.1-06756.run' instead to install on the Rapserry pi 4. After that, it worked without a hitch.

@solstice Could you change /etc/NetworkManager/conf.d/wgpia.conf into something like 50-wgpia.conf? wgpia.conf sets unmanaged-devices, which will overwrite all user customization of the same variable. Renaming it 50-wgpia.conf will allow the user to set in something like 90-unmanaged.conf to override (in my case, to merge my customization with wgpia.conf). Ideally, NetworkManager should merge the unmanaged-devices, but we cannot hope it could happen in the near future.

@olimazi Did you check the comments below? You will see

Don't forget to start and enable the systemd service with sudo systemctl enable --now piavpn.service

I would request that that be added to the output when program is installed because it's not clear that a service needs to be enabled upon install

The package installed fine, however upon starting the client there are no settings options upon right click on the desktop icon, the only option is to double click the icon which immediately tries to "connect" to the VPN - it doesn't even ask me to enter my username/password credentials for my PIA account. The connection icon turns and never connects, this is where it's stuck.

@rwt13 yes previous version should have been named 2.6.0_05820 but I followed their scheme by simplicity/lazyness