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.

Hi @solsticedhiver, this whole problem has been somewhat unclear to me. You are right that I should have checked things with ldd myself before blindly applying your solution, and @coolreader18 was right about the fact that I should have double-checked the package before submitting. To prevent issues like this from occurring in the future, I have added you as co-maintainer, as you were the person which submitted this package anyway. If I am ever excessively slow at packaging a new version or submitting an appropriate patch, please feel free to help me out!

It's only me that is affected or what? because the fix does not work as it is now.

The symlink is in the wrong directory. It should be in /opt/piavpn/lib, and remove the library before making the symlink.

oops, my previous comment was incorrect /o\ sorry

Ah you're right. I had symlinked it manually before, so I didn't realise. Thanks for pointing it out!

The fix is a bit janky I think - you put the ln line in the heredoc for debug.txt, so it doesn't actually run, but the command is installed to the first few lines of /opt/piavpn/var/debug.txt :^)

Hi, thanks for your message @solsticedhiver. I've made a temporary, primitive fix for the problem, and will revert it when the root cause is addressed upstream.

pia couldn't connect this morning. I got an error about DNS.

I found that line in the daemon.log

[2024-11-16 11:26:21.698][5e3e][common.process.stderr][src/exec.cpp:109][warning] resolvectl: /opt/piavpn/lib/libcrypto.so.3: version `OPENSSL_3.4.0' not found (required by /usr/lib/systemd/libsystemd-shared-256.8-1.so)

And systemd has been updated yesterday here from 256.7-1 to 256.8-1

So to fix it, i copied /usr/lib/libcrypto.so.3 to /opt/piavpn/libcrypto.so.3 (made a backup first)

It works now.

Thanks @p2a, it seems you were right: the default location for rt_tables has moved from /usr/lib/iproute2/rt_tables to /usr/share/iproute2/rt_tables... The existing edit will now work post the adjustment that I made. Ty for the heads-up!

For your second point, maybe you can try piactl background enable and then setting the kill-switch and auto-connection from the GUI? On subsequent connections, I'm guessing that everything should work.

@lobroc I think your iproute2 edit might be working, but during install these still pop up which give the impression of it not working:

:: Processing package changes...
cp: cannot stat '/usr/lib/iproute2/rt_tables': No such file or directory
awk: fatal: cannot open file `/etc/iproute2/rt_tables' for reading: No such file or directory
grep: /etc/iproute2/rt_tables: No such file or directory
(1/1) installing piavpn-bin                                                                                                              [###################################################################################] 100%
You need to start the daemon with 'sudo systemctl start piavpn.service'
Also run 'sudo systemctl enable piavpn.service' to make it automatically start at boot
Optional dependencies for piavpn-bin
    WIREGUARD-MODULE: to use the wireguard kernel module instead [installed]
:: Running post-transaction hooks...
(1/2) Reloading system manager configuration...
(2/2) Arming ConditionNeedsUpdate...

It's also not clear how to ensure connection at system start. I'm going to test this more, but so far it's not actually connecting at start until I manually trigger piactl connect. My goal is to have the killswitch active and so no network traffic leaves the system when it's not connected, but this is all eluding me for some reason right now. I guess in part the wiki entry is just entirely unrelated to this, even though this package is the recommended option.

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

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 :(