Unexpected `pvpn-ipv6leak-protection` connection on system shutdown/reboot

[durierem]

When shutting down the system without manually stopping ProtonVPN, the connection pvpn-ipv6leak-protection stays active on next boot and prevents any outgoing connections before manually starting ProtonVPN first.

Output of nmcli connection show --active on system boot, before starting ProtonVPN:

NAME                      UUID                                  TYPE    DEVICE          
...
pvpn-ipv6leak-protection  bfdcc8cf-c3b2-424b-b2c7-46ef4ecd69c5  dummy   ipv6leakintrf0
...

I don't have killswitch enabled.

Could be linked to #13?

System specs:

• Arch Linux (kernel 5.12.15)
• Gnome 40.2.0
• ProtonVPN CLI 3.7.2

[durierem]

As a workaround, one can create a systemd service unit on shutdown such as this one (in /etc/systemd/system):

[Unit]
Description=Disconnect from ProtonVPN
DefaultDependencies=no
Conflicts=reboot.target
Before=poweroff.target halt.target shutdown.target
Requires=poweroff.target

[Service]
Type=oneshot
ExecStart=/usr/bin/protonvpn-cli disconnect
RemainAfterExit=yes

[Install]
WantedBy=shutdown.target

I'm not an expert on systemd unit files, don't hesitate to review/modify it.

[calexandru2018]

This is fixed with https://github.com/ProtonVPN/protonvpn-nm-lib/releases/tag/3.5.0

[osuka]

This is happening to me now with the latest version. Hadn't happened to me before. It's happened on two different PCs, both running Ubuntu 21.04 and 21.10.

Please consider this again, there may be some race condition that leaves the killswtich (which I never enabled) active. As an end user it's very hard to know it has anything to do with proton, let alone find the fix. All you see is your computer has no internet connection, and it doesn't recover it rebooting or uninstall protonvpn. Maybe proton could detect it and warn the user about what is going on? or do the disabling itself?

The fix is as explained in several places but of course one needs the internet to find what to do:

nmcli device delete ipv6leakintrf0

or

protonvpn-cli ks --off

Release

protonvpn/unknown,now 1.0.0-4 all [installed]
  ProtonVPN metapackage

protonvpn-cli/unknown,now 3.11.0-7 all [installed]
  ProtonVPN CLI (Python 3)

protonvpn-gui/unknown,now 1.7.0-11 all [installed,automatic]
  ProtonVPN GUI (Python 3)

protonvpn-stable-release/now 1.0.1-1 all [installed,local]
  Package to install ProtonVPN GPG key and stable repo

python3-proton-client/unknown,now 0.7.1-3 all [installed,automatic]
  Proton SRP (Python 3)

python3-protonvpn-nm-lib/unknown,now 3.7.0-6 all [installed,automatic]
  ProtonVPN NM library (Python 3)

[calexandru2018]

Hey @osuka

Actually it’s not a race condition but rather some issue with the distro as it does not seem to respect the inhibitor. This is something that we’re looking into currently as this behavior is very inconsistent and difficult to reproduce (sometimes it happens and sometimes it does not).

[STPKITT]

I just experienced this issue using Xubuntu 22.04.1 LTS. Therefor IMO this issue should be reopened, I mean it's not like the distro I'm using is rare, esoteric or bleeding edge. Btw I used the following command to make my machine being able to resolve hostnames again: nmcli connection delete pvpn-ipv6leak-protection Before that I fully removed ProtonVPN although I suspect that wasn't needed to at least temporarily solve the issue.

[hasalex]

Problem still exists

• Ubuntu 22.04
• ProtonVPN CLI 3.12.0

[it5myw0rld]

Try this:

• ip link delete \<device_name>

In my case ip link delete ipv6leakintrf0

[kavemang]

issue ongoing here:

• Endeavour OS
• Lenovo laptop
• CLI 3.14.0

[davidengithub]

Same problem with:

Sistema operativo: Manjaro Linux Versión de KDE Plasma: 5.27.4 Versión de KDE Frameworks: 5.105.0 Versión de Qt: 5.15.9 Versión del kernel: 6.1.29-1-MANJARO (64 bits) Plataforma gráfica: X11 Procesadores: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz Memoria: 7,7 GiB de RAM Procesador gráfico: GeForce GTS 450/PCIe/SSE2

[eguiraud]

Same problem on arch linux. This should be reopened.

[eguiraud]

On Arch the problem persisted even after removing the protonvpn and protonvpn-cli packages. I still had to run:

nmcli connection down pvpn-ipv6leak-protection
nmcli connection delete pvpn-ipv6leak-protection

[EirikDaude]

I'm having the same issue on Fedora / Gnome. I agree it should be reopened.

[igarca]

Same here. Linux Mint 21.1 CInnamon.

[aarangop]

Same here, Linux Mint 21.1 Cinnamon

[nbari]

Just had this problem (Debian - Bookworm), wasn't sure what was the problem, I just noticed that the /etc/resolv.conf was not changing and always was using nameserver ::1, until removed the connection:

nmcli connection delete pvpn-ipv6leak-protection

[GarlandKey]

This should be reopened. Same problem on Arch Linux as of August 31, 2023 with latest version.

[haakonn]

I almost always forget to manually disconnect from Proton VPN before closing the lid on my laptop. As a result, the laptop comes up with non-functional networking, and I have to manually disconnect from pvpn-ipv6leak-protection. Removing the requirement of manually disconnecting before putting the computer to sleep would be the number 1 most important thing to improve my Proton VPN experience. I hope you will consider it.

[kavemang]

This is also still happening in fedora 38 both kde and gnome spins

[Hyphaed]

I'm on Ubuntu 23.10 (Mantic Minotaur)

after I boot up the system if I execute

nmcli connection show --active

I get this output

pvpn-ipv6leak-protection 02d65d4e-2b5e-4ed0-b5a1-0e63b588b3db dummy ipv6leakintrf0
pvpn-killswitch 83153003-200a-4877-8575-4f65659ef93d dummy pvpnksintrf0
pvpn-routed-killswitch 151f7301-3ac8-493e-8f43-2694441712c4 dummy pvpnroutintrf0

I use next commands to delete the connections

sudo nmcli connection delete pvpn-ipv6leak-protection sudo nmcli connection delete pvpn-killswitch sudo nmcli connection delete pvpn-routed-killswitch

yet on every boot up those connections reappear

How can I permanently delete those connections?

I had this problem on the past, but only with pvpn-ipv6leak-protection and I was able to fix it

but this time those connections are just reappearing, even if I delete them

I've uninstalled protonvpn and removed the repository also. That does not solve it either

[mrwebfr]

@Hyphaed

I found the solution here: https://github.com/ProtonVPN/linux-app/issues/20#issuecomment-1751385092

I deleted all files starting with 90

nmcli connection show --active
nmcli connection show | awk '{ print $1 }' | grep pvpn | xargs nmcli connection delete
cd /etc/netplan
rm 90*
systemctl restart NetworkManager.service
nmcli connection show --active