Protonvpn connection issue
by business_kid from LinuxQuestions.org on (#6DD7B)
I'm using the protonvpn-cli-2.2.11, because I can and very much want to go around networkmanager. I'm a slackware64-15.0 user, so I don't have to suffer that <...sentence deteriorates into expletives:)>. I can take it or leave it.
I connect via the protonvpn script added to the init scripts (Yes, no systemd) and run the protonvpn-cli to connect. It modifies the route, & etc/resolv.conf. Protonvpn-cli has one short script in /usr/bin and is otherwise much like a python module with small scripts aplenty.
Occasionally, the vpn is liable to hang, In this state, I can't browse. Curiously, running downloads will complete. /etc/resolv.conf sometimes has gone back to it's 'no vpn' state. other times it looks connected. 'Route' throws up the headers, pauses 5-10 second and shows me connected to the vpn. But I'm not. The script has a 'status' option which shows me connected. But if I reconnect, my browsing is fine - until the next time, whenever that is. It might happen 3 times in a morning, the be ok for weeks. Suspending my pc does it reliably.
Any fixes, guesses as to the issue, or tests to narrow this down are welcome and will be tried.
I connect via the protonvpn script added to the init scripts (Yes, no systemd) and run the protonvpn-cli to connect. It modifies the route, & etc/resolv.conf. Protonvpn-cli has one short script in /usr/bin and is otherwise much like a python module with small scripts aplenty.
Occasionally, the vpn is liable to hang, In this state, I can't browse. Curiously, running downloads will complete. /etc/resolv.conf sometimes has gone back to it's 'no vpn' state. other times it looks connected. 'Route' throws up the headers, pauses 5-10 second and shows me connected to the vpn. But I'm not. The script has a 'status' option which shows me connected. But if I reconnect, my browsing is fine - until the next time, whenever that is. It might happen 3 times in a morning, the be ok for weeks. Suspending my pc does it reliably.
Any fixes, guesses as to the issue, or tests to narrow this down are welcome and will be tried.