Package Details: piavpn-bin 1:3.5.3-1

Git Clone URL: (read-only, click to copy)
Package Base: piavpn-bin
Description: Private Internet Access client
Upstream URL:
Keywords: private-internet-access vpn
Licenses: custom
Conflicts: pia-launch, pia-manager, pia-tools, private-internet-access-vpn
Provides: piavpn
Submitter: solsticedhiver
Maintainer: lobroc
Last Packager: lobroc
Votes: 22
Popularity: 0.23
First Submitted: 2020-04-14 15:32 (UTC)
Last Updated: 2023-12-20 08:51 (UTC)

Dependencies (5)

Required by (0)

Sources (2)

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:


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.

Latest Comments

1 2 3 4 5 6 Next › Last »

lobroc commented on 2023-11-28 18:52 (UTC)

As a small note, broken split tunnelling with iproute2>=6.5.0 is now fixed as of client version 3.5.2!

lobroc commented on 2023-10-24 17:05 (UTC) (edited on 2023-10-24 17:11 (UTC) by lobroc)

Yeah, I agree, and had already considered this. This was just a way of avoiding incrementing the epoch, but sure, I'll make the change if it makes things clearer for everyone. Sorry for all the updates :(

navarroaxel commented on 2023-10-24 15:07 (UTC)

Actually you should use the version 3.5.1 instead of the build number. You can use epoch to "decrease" the version number to 3.5.1. The build number is not required to be part of the package version value.

lobroc commented on 2023-09-27 13:11 (UTC)

I pushed out the update, as I was able to reproduce the same problem on a fresh install from the .run file directly, within a brand new Arch VM (with iproute2==6.5.0-1). Feel free to double-check on your end.

The split tunnelling problem therefore isn't from how PIA is being installed by this AUR script.

I'm unfortunately not qualified enough to be able to diagnose / fix why this problem is occurring, as I believe this is on PIA's side, unless I'm mistaken. If anyone has a fix, feel free to share your thoughts. In the meantime, I'd recommend not using the split tunnelling feature. Thanks.

lobroc commented on 2023-09-26 08:50 (UTC)

I see that there's a problem @Cebtenzzre, and I'll get to it as soon as the 3.5 version is also released for arm64, as the 3.5 version possibly has fixes for this.

Cebtenzzre commented on 2023-09-26 00:22 (UTC) (edited on 2023-09-26 00:24 (UTC) by Cebtenzzre)

I'm having trouble getting the split tunnel working again after the iproute2 update. First I noticed that all traffic was bypassing the VPN. Then I reinstalled the piavpn-bin package, and now the VPN-enabled applications fail to connect to anything unless I switch the protocol to OpenVPN.

lobroc commented on 2023-09-25 15:28 (UTC) (edited on 2023-09-25 15:29 (UTC) by lobroc)

Hi @genji, thanks for the comment. Indeed, I would use a systemd user ( service which runs something like:

/bin/bash -c 'while true; do if [[ $(/opt/piavpn/bin/piactl get connectionstate) != "Connected" ]]; then /opt/piavpn/bin/piactl connect; fi; sleep 10; done' (with ExecStop being /opt/piaivpn/bin/piactl disconnect of course).

I'm not sure if there's a cleaner / easier way to do this. I'm all ears if someone else has an idea :)

genji commented on 2023-09-25 05:33 (UTC)

Hi there, thank you for this update, I have it working correctly in headless mode because I have no GUI configured on this Arch - just wondering is there a way to reliably make this auto-start or auto-reconnect without using the GUI ?

I know the GUI has the functions built in but is there some simple creative solution to even make it automatically just connect at startup? I'm guessing it's as simple as adding 'piactl connect' to a runtime script somewhere - but just wondering the correct way as I'm a new user. Thanks!!