diff --git a/opsec/vpnqemu/11.png b/opsec/vpnqemu/11.png new file mode 100644 index 00000000..bfc00c2d Binary files /dev/null and b/opsec/vpnqemu/11.png differ diff --git a/opsec/vpnqemu/12.png b/opsec/vpnqemu/12.png new file mode 100644 index 00000000..fd64fe9b Binary files /dev/null and b/opsec/vpnqemu/12.png differ diff --git a/opsec/vpnqemu/index.html b/opsec/vpnqemu/index.html index 902f0bb9..2d19c3e4 100644 --- a/opsec/vpnqemu/index.html +++ b/opsec/vpnqemu/index.html @@ -107,20 +107,24 @@ curl ifconfig.me -

From there you'll have the tun0 network interface available, which we can use in the QEMU VM XML configuration:

+

From there you can check from the host OS that you have a access to the internet via the VPN:

+ + +

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!):

+ +

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:

-
+ -
- + + +