I don’t mean to imply anything about OpenVPN/Wireguard, various scripts
etc. This post is meant to safe the so-called “non-technical” user or
the one that has other stuff to do but needs a VPN qube NOW a lot of
time an nerves. The above works.
I think sys-work will do for production then add network manager so they can connect to work vpn. Lastly, write a good doc for how to blacklist all ip except the one or some ip in the vpn or script to automatically adding firewall when connected to ovpn.
It doesn’t. I recommended it back then because I just needed something to work without spending days researching and this one did the trick.
Meanwhile I have become acquainted with an even simpler and better method based on the NetworkManager.
create a VPN qube
use NetworkManager to setup the OpenVPN connection
set the firewall rules of the VPN qube such that it can only connect to the VPN server(s) and nothing else
This works without any scripts and if the VPN connection fails/dies the Qubes firewall makes sure no other traffic is possible (sine the respective VPN qube can only connect to the VPN server).
And yes… you can do this entirely in the GUI and you have visual feedback. For bonus points you can add a simple script to automatically connect / reconnect.
Okay thank you. This is probably exactly what I need for right now. I’m sure I’ll become more acquainted like you are with firewall and and openvpn from terminal as I too continue my journey
Hi and thanks, ok I’m dummies but I didn’t think so much! Let’s assume that I have never installed a vpn in a linux environment! I follow this guide after several searches!
1 - install the debian-11 minimal template, update and clone it
2- in the clone where I open the terminal from qvm because I prefer not to have it passwordless, I add the qubes-contrib repo that have the expired key and make me waste hours to solve it but that’s another story …
3 I install the packages qubes-tunnel suggested in the guide, I create the vm and go to the services to add qubes-tunnel and there is no qubes-tunnel service to be activated in the machine, duoble check if it is installed yes it is … . stop … hours of research nothing … in the meantime my eyes burn because I have set Xft.dpi: 144 in x11-common of the template and but the characters are very small and I do not see anything, besides a problem of keyboard localization, which does not make me use the # character having accidentally activated the testing security repository precisely because I could not see it, my keyboard is not us however I know that on key three with shift it should exit but instead it inserts a space … oh well I will leave the security testing active
In any case, a happy Sunday everyone!
EDIT: systemctl list-unit-files give me the list of services enabled and qubes-tunnel.service is enabled enabled…ok good
i assume this ok an something about the services on qubes manager
must be added to create / recreate the list that I am not aware of
Sven’s suggestion was to use the native capacity in Network Manager -
not to use the qubes-tunnel at all.
You may find this much easier , given your other issues.
For a minimal template you will need to read this page
Many problems that people have in Qubes are actually not Qubes specific.
Using a VPN in Network Manager is one of those.
The only Qubes specific part is that you have to do this in the template.
For Debian you will want to install an additional package, relevant to
your VPN. For example network-manager-fortisslvpn for Fortinet VPN, network-manager-openvpn for OpenVPN. There are Gnome versions of these
For a minimal template you will need to read this page
Many problems that people have in Qubes are actually not Qubes specific.
Using a VPN in Network Manager is one of those.
The only Qubes specific part is that you have to do this in the template.
For Debian you will want to install an additional package, relevant to
your VPN. For example network-manager-fortisslvpn for Fortinet VPN, network-manager-openvpn for OpenVPN. There are Gnome versions of these
e.g. network-manager-openvpn-gnome
The page you linked return 404 right now , anyway i have already read the minimal guide doc.
journalctl grepin qubes* network-manager and openv-vpn was enabled enabled i haven’t try to install network-manager-opnevpn-gnome i also don’t have any graphical server…
maybe is firewall related or certificate
the guide you posted was very useful, as well as interesting,
don’t know about the ways to skin cat -.- i think is a proverb from your location maybe ? to say various method to make thinks ?
thanks!