i have look a this config file and at the handler, i don’t like how credential are managed,
passing a path for a plein txt , i don’t know if openvpn can make use of more secure tool to call the credential… Network manager is better on this aspect
1 Like
Apologies for the late response. I agree it seems like a clear vuln here. Do you have any suggestions? Maybe password securing the file and making it read and write only to user and no access to all other users might be a start?
Moved to User Support / Guides
Thanks for the link.
In that guide he’s using mulivad. He’s calling the service in the script using:
nmcli con up mullvad_ca
Anyone know what I would replace that command with with if I was using ProtonVPN?
I have used ProtonVPN with nmcli it works if you download the ovpn config file and add it using network manager taskbar icon. If you call the connection proton, you can use ‘nmcli con up id proton’ to select the connection.
Both the protonvpn and protonvpn-cli clients work out of the box, I think they are easier to use, and it makes it much easier to select a specific server or use random servers. If you use nmcli you need to download a new ovpn config file every time you want to change vpn server.
1 Like
I’m looking to get the auto-connect functionality every time the VM loads, and/or every time the vpn connect drops. Is there away to auto-connect using the CLI or GUI using bash?
The way I autostart protonvpn-cli is by using a .desktop shortcut in /home/user/.config/autostart, it automatically connects the vpn when the sys-vpn qube starts.
I tried to use systemd or rc.local, but it was given me some issues because the cli client needs access to the gnome keyring using dbus, I got it working by making a delay that waits for dbus to be ready, but the desktop shortcut just seems like an easier way to get the same result.
Both protonvpn and protonvpn-cli are just frontends for network manager, it’s very rarely I get disconnected, but if it happens I just use the nm taskbar icon to manually reconnect. You probably can make a script that does it automatically, it’s only during boot that protonvpn-cli is a little tricky to use.
Will this work for DNS leaks? Or will those route around the firewall?
I’m having a bit of trouble getting the GUI/CLI to work in 4.1. Are you on 4.0 or 4.1?
I’m using 4.1 with the debian 11 template
I did install network-manager-openvpn and network-manager-openvpn-gnome I’m not sure if they are needed.
I used this guide to install the vpn qube
And I used this guide to install protonvpn client
Were you able to get a Whonix → ProtonVPN to work?
I haven’t tried, but I assume you can change the netvm for sys-whonix to sys-vpn
Its likely Proton is blocking Tor exit nodes. I couldn’t get it to connect using whonix. Proton->Tor config works though.
I just tried to switch sys-whonix from sys-firewall to sys-vpn, it works for me. anon-whoinx uses sys-whonix, and it connects without any issues, tor check confirmed I’m using a tor exit node.
I’m using a paid protonvpn subscription, don’t know if that could make a difference.
Hello guys I tried to install mullvad with tasket VPN support but it fails connecting. Is there any tutorial for mullvad and tasket VPN Support, I used proton before and it worked without problems, I did all the same things with mullvad but it doesnt work. Im not on my computer right now so I cant give details. @tasket
I think there’s a bug regarding openvpn in recent versions of NetworkManger on Fedora. I’ve had to use OpenVPN client from the command line as a workaround for now.
There are a couple writeups about it on the fedora forums. Here’s a link to one of them: