I want the primary connection in Qubes to be Mullvad VPN and not APP or Templates
I know that dom0 is the key, if i can put a VPN in it, the entire system will connect through it
I tried all the methods and it doesn’t work. I just want to change the connection in dom0
You are coming at this with a misunderstanding; dom0 has no network connections. By default, all outgoing network connections are made through the sys-net qube.
2 Likes
In order to do this, it depends on what you mean by “main.” For updates, just make this qube the update qube. For app qubes, make it the default netvm and make sure the qubes you currently have already connect to that qube.
This is now how Qubes is designed to be used, and this will not function how you expect. For reference, please take a look at this:
It is highly discouraged to put networking in dom0. Any function that isn’t directly related to the management of your qubes should be done outside of dom0, including (especially) networking.
1 Like
After installation I have two problems
1- Wireguard does not work automatically - Although Mullvad VM works at startup
2- whonix does not connect to the internet when Mullvad is the connection option
Which guide did you follow?
I didn’t use the Mullvad App so I can’t tell how it should work, maybe someone else will clarify this.
Maybe the Mullvad is not connected to the VPN server.
Do you have internet working in debian/fedora qube with your Mullvad sys-vpn qube as its net qube?
This Guide - WireGuard on Qubes OS
Yes i Have Internet in Fedora APPs But Not Whonix APP
This guide won’t work for Qubes OS 4.2 because the firewall was switched from iptables to nftables in Qubes OS 4.2.
Use one of the Wireguard guides for Qubes OS 4.2 on this forum e.g.:
1 Like