![]() Create a new standaloneVM based on debian-minimal template (name it like `vpn-mullvad`) ![]() ![]() `sudo qubes-dom0-update qubes-template-debian-11-minimal`Ģ. Install the debian 11 minimal template on dom0 using the following command (if you haven't already done so). *Since I'm new to Qubes, many things in this note can be wrong.*ġ. This is a note about setting up the Mullvad GUI with the debian minimal template. mullvad-gui-qubes.md # Setting up mullvad gui in debian 11 minimal standaloneVM - r4.1 # FIXME: Tinyproxy does not reload DNS servers. # You may need to increase it beyond 5 seconds. Insert the line sleep 5 above the line /usr/lib/qubes/qubes-setup-dnat-to-ns in /etc/NetworkManager/dispatcher.d/qubes-nmhook like this: #!/usr/bin/sh A better understanding of how DNS resolution is handled in Qubes.Bonus points if I can still access a printer on my home 192.168 network circumventing VPN.A way to automatically run this qubes-setup-dnat-to-ns command when Mullvad connects (or disconnects?).If I run sudo /usr/lib/qubes/qubes-setup-dnat-to-ns in the mullvad VM, then DNS resolution works. I thought I could use the Mullvad GUI in the mullvad Qube to control the traffic for all my AppVMs.įrom my AppVMs I can ping an IP address, but I cannot resolve any DNS names. I inserted this VM either between sys-firewall and sys-net or between my normal appvms and sys-firewall (don’t know which would be better). In the Mullvad AppVM I set /etc/mullvad-vpn to be persistent and I start the GUI and connect to VPN. I have installed the Mullvad GUI in (the template of) an AppVM and set that AppVM to “provide networking”.
0 Comments
Leave a Reply. |