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.

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.

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.

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.

Hi @genji, thanks for the comment. Indeed, I would use a systemd user (https://wiki.archlinux.org/title/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 :)

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!!

I've taken into consideration your comment, @saturn_knight. Now, all modifications are done in /etc/iproute2/rt_tables, which is copied from /usr/lib/iproute2/rt_tables at install time. When uninstalling, if the file is the same as the template, it is then removed. This should make the behaviour the same as that which is expected.

(You will still need to either move to rt_tables.pacsave to rt_tables, or uninstall and reinstall the package in order for the /etc/iproute2 folder to contain the file.)

While it's true that the rt_tables default location has moved to /usr/lib/iproute2, I don't think modifying the file in place is the best way to fix this problem. The rt_tables file in /etc/iproute2 will take precedence over one in /usr/lib/iproute2. According to the iproute2 documentation, the preferred method would be to copy rt_tables to /etc/iproute2 if it doesn't exist and then modify that copy.

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'

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!