Hi all, just updated to F35 from F34 and had some connectivity issues while using the ProtonVPN killswitch. I tried searching for a solution, but ended up discovering one with some investigation.
I had the permanent killswitch enabled, updated to the new Fedora 35 and it removed my Proton packages but somehow left the killswitch active on my machine, which took some time to figure out. I thought I’d document it here for anyone who may be looking for a solution to the same problem.
Looking at the network manager, you can see full connectivity/connected state, but a ping yields no result.
root@jfed joel]# nmcli g STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN connected full enabled enabled enabled enabled [root@jfed joel]# ping 22.214.171.124 PING 126.96.36.199 (188.8.131.52) 56(84) bytes of data. ^C --- 184.108.40.206 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3106ms
Below, I ran
nmcli c to see what may be active and to my surprise, the ProtonVPN killswitch was still there, blocking my connection, even when I didn’t have
protonvpn-cli or the GUI packages installed, which meant I could not intuitively turn it off.
[root@jfed joel]# nmcli c NAME UUID TYPE DEVICE pvpn-killswitch [redacted] dummy pvpnksintrf0
The solution - mark the protocol as down, like below:
[root@jfed joel]# nmcli c down pvpn-killswitch Connection 'pvpn-killswitch' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/1) [root@jfed joel]# ping 220.127.116.11 PING 18.104.22.168 (22.214.171.124) 56(84) bytes of data. 64 bytes from 126.96.36.199: icmp_seq=1 ttl=118 time=18.5 ms 64 bytes from 188.8.131.52: icmp_seq=2 ttl=118 time=24.8 ms 64 bytes from 184.108.40.206: icmp_seq=3 ttl=118 time=19.8 ms 64 bytes from 220.127.116.11: icmp_seq=4 ttl=118 time=18.0 ms ^C --- 18.104.22.168 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3005ms rtt min/avg/max/mdev = 18.042/20.294/24.807/2.682 ms
As you can now see, ping yields results and now I can reinstall the ProtonVPN client and use the killswitch as it’s intended.
Hope this helps someone else!