In this guide we will set up a ProxyVM called "MullvadVPN" which will provide network to other AppVMs, using WireGuard. If you want to use OpenVPN instead then see our guide Mullvad on Qubes OS 4.
Note: We will use Sweden (se9-wireguard) as the server in this guide. If you want to use another server then replace the configuration with that.
Create a new qube
Click on the Qubes app menu and then Create Qubes VM.
- Name and label: MullvadVPN.
- Type: Qube based on a template (AppVM).
- Template: fedora-36 (or later).
- Networking: default (sys-firewall).
- Advanced: Check (enable) provides network.
- Click on OK.
Note: In the Qubes app menu, the newly created MullvadVPN AppVM qube will show up as "Service: MullvadVPN" and not "Qube: MullvadVPN" due to its "provides network" setting.
Download a WireGuard configuration
In another AppVM (not MullvadVPN) that you use for web surfing:
- Open a web browser and log in to our WireGuard configuration file generator.
- Select Linux as the platform and then click on Generate key.
- Select a country, a city and a server.
- Click on Download file.
- Click on the Qubes app menu and go to your current AppVM and open Files.
- Open the Downloads folder and right click on the downloaded WireGuard file.
- Select Copy To Other AppVM... and then enter MullvadVPN as the Target and click on OK.
We will install WireGuard in the Fedora-34 template so your MullvadVPN ProxyVM can use that.
- Click on the Qubes app menu and go to Template: fedora-36 and open the Terminal.
- In the Terminal run the command
sudo dnf install wireguard-tools -y
- Shut down the VM with the command
sudo shutdown -h now
- Shutdown and Start the MullvadVPN ProxyVM so that wireguard-tools are added to it.
Set the Networking
- Click on the Qubes app menu and go to System Tools > Qube Manager.
- Select the AppVM that you want to use with the MullvadVPN ProxyVM and click on the Stop button in the toolbar to shut it down.
- Right click on the same AppVM and then select Qube settings.
- On the Basic tab, click on the Networking drop-down list and select MullvadVPN.
- Click on OK.
- Click on the Start button in the toolbar to start the AppVM again.
In the MullvadVPN ProxyVM:
- Click on the Qubes app menu and go to MullvadVPN and open the Terminal.
- Now you will copy the WireGuard .conf file that was copied from the other AppVM to the /home/user/ folder so it persist after reboot. First run:
cp /home/user/QubesIncoming/*/se9-wireguard.conf /home/user/
- Now you will edit the /rw/config/rc.local file using a text editor. First install nano:
sudo dnf install nano -y
- Then run
sudo nano /rw/config/rc.local
wg-quick up /home/user/se9-wireguard.conf(or the config file you used) on a new line.
- Press Ctrl+O (Enter) and then Ctrl+X to save and exit.
Make sure that WireGuard connects:
sudo wg-quick up /home/user/se9-wireguard.conf
sudo wgand check for a WireGuard network interface and a peer handshake.
Add DNS hijacking rules
Now we will add firewall rules to redirect DNS requests to 10.64.0.1 (the DNS on the VPN server) for all AppVMs that use the MullvadVPN ProxyVM.
Make sure that you have started an AppVM that has the Networking set to MullvadVPN, otherwise the "vif" IP address will not be visible.
Still in the MullvadVPN Terminal:
- To find out your vif* IP address, run
ip a | grep -i vif
- Edit the firewall user file with nano:
sudo nano /rw/config/qubes-firewall-user-script
- Copy and paste the following in the bottom. Replace 10.137.0.47 with your own vif* IP address:
# replace 10.137.0.47 with the IP address of your vif* interface virtualif=10.137.0.47 vpndns1=10.64.0.1 iptables -F OUTPUT iptables -I FORWARD -o eth0 -j DROP iptables -I FORWARD -i eth0 -j DROP iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu iptables -F PR-QBS -t nat iptables -A PR-QBS -t nat -d $virtualif -p udp --dport 53 -j DNAT --to $vpndns1 iptables -A PR-QBS -t nat -d $virtualif -p tcp --dport 53 -j DNAT --to $vpndns1
4. Press Ctrl+O (Enter) and then Ctrl+X to save and exit.
Add qube firewall rules
In Qube Manger, select MullvadVPN then right click and select Qube settings.
Make the following changes:
- Ensure it is still set to use sys-firewall as "Networking".
- Check "Start qube automatically on boot".
- Click on the "Firewall rules" tab.
- Click on "Limit outgoing internet connections to ...".
- Click on "+" and enter the IP addresses of the VPN servers that you want to be able to connect to. You can find it in the WireGuard configuration file (mlvd-se9.conf) on the Endpoint line, or in our Servers list.
- Click on OK.
In the next step you will edit the firewall manually. After this you can not open Qube Manager and add rules on the Firewall rules tab anymore, so make sure to add all the servers you need now. If you have to add more servers later you can do it in the Terminal Emulator using the following command (replace SERVER-IP with the IP-address to the Mullvad VPN server).
qvm-firewall MullvadVPN add accept dsthost=SERVER-IP
If you need to undo the changes then you can remove all firewall rules and reset it to default (accept all connections) using this command:
qvm-firewall MullvadVPN reset
Disable ping (optional)
As noted in the qube Firewall rules window, those rules do not apply to DNS requests and ICMP (pings). If you want to block pings too then you can use the qvm-firewall command.
- Click on the Qubes app menu and open Terminal Emulator.
qvm-firewall MullvadVPN list. Find the rule in the bottom that says "accept icmp" and note the line number.
qvm-firewall MullvadVPN del --rule-no NUMBER. Replace NUMBER with the line number you found above.
qvm-firewall MullvadVPN add --before NUMBER drop proto=icmp. Replace NUMBER with the line number you found above. This new rule will be added before the last "drop" line.
- Check it by running the list command again. The rules should be in this order: accept (the IP addresses of the VPN servers), accept dns, drop icmp, drop.
How do I verify that traffic is going out via the MullvadVPN proxy?
Open a web browser in your AppVM that is using the MullvadVPN ProxyVM and go to our Connection check.
Internet works in the ProxyVM, but not in the AppVM.
Make sure you shut down your AppVM before setting the Networking to ProxyVM. It seems that it does not work as well to change it on the fly.
Try to lower the MTU in your AppVM:
sudo ifconfig eth0 mtu 1280