move tutorials to new repo

This commit is contained in:
nihilist 2025-05-06 15:58:25 +02:00
parent df0647a632
commit ccf5a7caf9
1956 changed files with 25133 additions and 0 deletions

BIN
vpnqemu/0.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 18 KiB

BIN
vpnqemu/1.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 33 KiB

BIN
vpnqemu/10.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 32 KiB

BIN
vpnqemu/11.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 105 KiB

BIN
vpnqemu/12.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 71 KiB

BIN
vpnqemu/2.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

BIN
vpnqemu/3.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 10 KiB

BIN
vpnqemu/4.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 52 KiB

BIN
vpnqemu/5.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 62 KiB

BIN
vpnqemu/6.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 152 KiB

BIN
vpnqemu/7.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 41 KiB

BIN
vpnqemu/8.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 33 KiB

BIN
vpnqemu/9.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 68 KiB

57
vpnqemu/index.md Normal file
View file

@ -0,0 +1,57 @@
---
author: nihilist
date: 2024-08-08
gitea_url: "http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/94"
xmr: 8AUYjhQeG3D5aodJDtqG499N5jXXM71gYKD8LgSsFB9BUV1o7muLv3DXHoydRTK4SZaaUBq4EAUqpZHLrX2VZLH71Jrd9k8
---
# Route QEMU VMs through a Host OS VPN
## **Initial Setup**
First, install the VPN like we saw previously [here](../vpn/index.md), but the only difference being that we now install it on the Host OS, rather than inside the VM.
# Download the Mullvad signing key
sudo curl -fsSLo /usr/share/keyrings/mullvad-keyring.asc https://repository.mullvad.net/deb/mullvad-keyring.asc
# Add the Mullvad repository server to apt
echo "deb [signed-by=/usr/share/keyrings/mullvad-keyring.asc arch=$( dpkg --print-architecture )] https://repository.mullvad.net/deb/stable $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/mullvad.list
# Or add the Mullvad BETA repository server to apt
echo "deb [signed-by=/usr/share/keyrings/mullvad-keyring.asc arch=$( dpkg --print-architecture )] https://repository.mullvad.net/deb/beta $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/mullvad.list
# Install the package
sudo apt update
sudo apt install mullvad-vpn
# Connect to Mullvad VPN
mullvad account login
Enter an account number: 91320912809328832
Mullvad account "91320912809328832" set
# Connect to the VPN:
mullvad lockdown-mode set on
mullvad connect
curl ifconfig.me
194.127.199.92
Then, configure mullvad as follows:
![](0.png) ![](1.png) ![](2.png)
From there you can check from the host OS that you have a access to the internet via the VPN:
![](11.png)
From there, you need to make sure that your VM has it's network interface set as "NAT" as it is by default (be aware that if the VM network interface is configured as macvtap or bridge, the traffic won't go through the VPN!):
![](12.png)
And then once applied, you can check if it works as intended from inside the VM (all that's required is for the VM to have a NAT connection), by going to <https://mullvad.net/en/check> from inside the VM:
![](6.png)