Anyone running Protonvpn under networkmanager?
I'm on current, and trying to run Protonvpn. I weaned myself off network setup via init scripts, because the vpn would drop out sporadically. Restarting the vpn would fix it. But it was an irritation.
So now I have Networkmanager, grabbed the deb2tgz script, ran the slackbuild, The pkg only contains a file in /etc/apt/sources.list.d/, one in /usr/share/doc/ & /usr/share/keyrings/. Should I go back to the init scripts? Did I grab the wrong file? |
Not with the Proton VPN client, but yes you can use NetworkManager if you download the OpenVPN configuration file from your Proton account and then import that file into NetworkManager. I did this on my last computer. The downside is every different Proton VPN server has its own configuration file. That is, you don't get the auto-selection feature that the ProtonVPN client has.
Which Proton VPN client are you using? The one on SlackBuilds.org (https://slackbuilds.org/repository/1...=protonvpn-cli) uses the old community version. It appears to me the official client requires systemd. |
Quote:
I have a wireguard conf that works fine But the downloaded file cannot be included as is, I have to complete a new configuration in NM by hands |
Thanks for the reply
Well, it transpires the maintainer of the Protonvpn Slackbuild has an @protonvpn.com email, so I've sent him a query. I'll post what I get back. The more I think about importing things into networkmanager, the more unwell I feel. Init scripts are nice. I'll post the gist of what comes back (if anything). I have a backup of the old system which I can't restore, but I can pinch 'known good' stuff from. I've been doing that. /etc/rc.d/ stuff is all known good. |
Quote:
|
Quote:
But thanks for that, you have made up my mind for me. RC scripts it is for me. I had an alias for the community app where I could simply put 'vp <country code> and I would be logged on to the server of choice, It was useful for getting around outages, or deceiving geo-ip :D. EDIT: @drumz: Thanks for spotting that. The email actually was sent to @protonmail.com. |
I use a couple of wireguard configs under NM which work fine. Downside is I lose access to full list of servers.
The community build works as well, however something has recently broken the status switch (protonvpn s) on my system. I don't know whether it is the recent upgrade or some other python module or other. Does anyone else experience this breakage, and if so any insight would be appreciated. |
wireguard will work with NM and should not drop connections
Quote:
|
Feel free to carry on chatting about NM, but I have the linux-community-cli back running, and NM is not being used any more. Protonvpn issues copious error messages but version 2.2.12 works, whereas 2.2.11 does not. I have an issue raised on github, and we'll see what comes of it.
|
@business_kid interesting I just get python spaghetti error code when I use the status switch. Will be interesting to see if anything happens there.
|
Quote:
Code:
# protonvpn init Code:
2024-03-28 14:55:09,908 — protonvpn-cli — DEBUG — cli:89 — ########################### |
In the download linux-coomunity-cli directory, there is a file called requirements.txt. I ran (as root)
Code:
pip3 install -r requirements.txt I also found that it only accepted my encrypted password, not what I had entered. I got that from the protonvpn site, IIRC. Protonvpn also only works as root, and doesn't work using sudo. Perhaps that's a config error. I get piles of crap from version 2.2.12, but it works, and I have an open issue about it. Lastly, if you're on the free plan, and you error out after a check of that website, it's possible that you're connecting to the wrong server. I think there's only 3 countries offering free servers, of which I can remember only 2: NL & JP. So Code:
protonvpn connect --cc nl EDIT: UDP works fine - no need to change it. It's smarter. |
All times are GMT -5. The time now is 07:30 PM. |