Hello, I wanted to build a MullvadVPN ProxyVM, but it doesn’t work!
I’m going crazy. The VM itself has internet, connects to the VPN fine, but other Qubes can’t connect to the internet as soon as I set the ProxyVM as network qube in the settings.
I wonder why? I have followed all possible tutorials and more than a year ago everything worked. Now I’m gradually switching to Qubes and I can’t get anything to work…
In the meantime I was able to create a MullvadVPN Proxy Qube which also (finally…) works.
There were problems with the DNS and I had no qubes-core-agent-networking tools installed.
But now I have another problem. My Mullvad app does not stay logged into the ProxyVM, meaning all configurations are lost after restarting the Qube. This means I have to log in again and again.
I have adapted it a little. I took a fedora-42-minimal as the template for the ProxyVM and installed the tools qubes-core-agent-networking, inotify-tools and mullvad-vpn. I created an AppVM from the template and made all the remaining configurations there according to the tutorial (Fix DNS, Wireguard MTU Issue). In the end, I set up my other Qubes, which should go through a VPN, accordingly and I now see that my ProxyVM has to be set up after every restart.
Does anyone know what the problem is? I first thought of gnome-keyrings but that was already preinstalled.
Configuration is saved to /etc/mullvad-vpn - in my salt
I use bind-dirs to retain these settings.
An advantage of this is that if you set up disposables using the
same template, then Mullvad use in the disposable is ephemeral.
All of this is contained in the salt states, and packaged here for simple installation -
sys-mullvad, and disposables where you can run the Mullvad VPN client,
or Mullvad browser.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.