ProtonVPN spams "AEAD Decrypt error: bad packet ID"

General system Newbie
1

Hello,
as soon as I start using protonvpn, as in connect to a server, journalctl is spammed with the following error message:

Apr 05 14:30:54 username nm-openvpn[4037]: AEAD Decrypt error: bad packet ID (may be a replay): [ #2351046 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

Always the same message, only the number increasing.

Im using the AUR Version of “protovpn-gui” and “python-protonvpn-nm-lib” by protontechag.
However the nm-lib is flagged as out of date, with it being from august last year.
Is it likely that the error stems from some KDE6(wayland) changes to the network manager?

As a (possibly unrelated) side note, I startet looking at at journalctl because Ive occasionally been having total system freezes for 3 days(I think). Initially happening twice during gaming(different games) where I just figured it happening due to wine or something. But today my system froze twice already, once when I dragged an image into gimp(the systemmonitor widget in the taskbar showed a spike to 100% cpu usage then froze as well) and then just half an hour later when I wanted to move a larger file(45GB) between two ssds.
Ive since done a memtest86+ test via live usb, where everything passed, and I didnt change any hardware either.

Im unsure on how to proceed from here so I would kindly ask for guidance in terms of further steps I can take.
Thanks.

2

I don’t think that version is being updated anymore. I use the aur/proton-vpn-gtk-app and don’t see those messages in journalctl.

2 Likes
3

Hm, yesterday I installed

protonvpn 1.0.0-3
protonvpn-cli 3.13.0-2
protonvpn-gui 1.12.0-1
python-proton-client 0.7.1-2
python-protonvpn-nm-lib 3.16.0-1

and I don’t see such messages

4

Installing the proton-vpn-gtk-app worked, but now I dont have a proton0 interface anymore. Do you have any experience sharing linux isos with qbittorrent?

Also after a restart, port forwarding (https://protonvpn.com/support/port-forwarding-manual-setup/#how-to-use-port-forwarding) works without running the command?!

while true ; do date ; natpmpc -a 1 0 udp 60 -g 10.2.0.1 && natpmpc -a 1 0 tcp 60 -g 10.2.0.1 || { echo -e "ERROR with natpmpc command \a" ; break ; } ; sleep 45 ; done

The site explicitly says: “Port forwarding is now activated. Note that closing your terminal window will terminate the loop process . You will need to re-run this loop script each time you want to start a new port forwarding session or the port will only stay open for 60 seconds.”

Im quite confused.

5

I’ve never really looked at the port forwarding. I just connect, double check my IP has changed with a webpage, use a webpage to run a DNS leak test and go.

This is what I see in my network:
Screenshot_20240406_112606