pappine/blog-contributions
1
0
Fork 0
forked from nihilist/blog-contributions
Code Pull Requests Activity

fix

Browse Source
This commit is contained in:
nihilist 2024-09-01 16:03:02 +02:00
parent e61bff55a0
commit 02cfbffecb
3 changed files with 11 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
opsec/vpnqemu/11.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 195 KiB

BIN
opsec/vpnqemu/12.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 159 KiB

18
opsec/vpnqemu/index.html
View File

@ -107,20 +107,24 @@ curl ifconfig.me
<img src="0.png" > <img src="0.png" >
<img src="1.png" > <img src="1.png" >
<img src="2.png" > <img src="2.png" >
<p>From there you'll have the tun0 network interface available, which we can use in the QEMU VM XML configuration: </p> <p>From there you can check from the host OS that you have a access to the internet via the VPN:</p>
<img src="11.png" class="imgRz">
<!--<p>From there you'll have the tun0 network interface available, which we can use in the QEMU VM XML configuration: </p>
<img src="3.png" class="imgRz"> <img src="3.png" class="imgRz">
<p>As you can see here, we have the tun0 interface, with the 10.5.0.0/16 subnet, so we'll use a smaller subnet within that same subnet to create our VPN NAT configuration:</p> <p>As you can see here, we have the tun0 interface, with the 10.5.0.0/16 subnet, so we'll use a smaller subnet within that same subnet to create our VPN NAT configuration:</p>
<img src="4.png" class="imgRz"> <img src="4.png" class="imgRz">
<p>Then use it on your VM configuration like so:</p> <p>Then use it on your VM configuration like so:</p>
<img src="5.png" class="imgRz"> <img src="5.png" class="imgRz">-->
<p>And then once applied, you can check if it works as intended from inside the VM, by going to <a href="https://mullvad.net/en/check">https://mullvad.net/en/check</a></p> <p>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!):</p>
<img src="12.png" class="imgRz">
<p>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 <a href="https://mullvad.net/en/check">https://mullvad.net/en/check</a> from inside the VM:</p>
<img src="6.png" class="imgRz"> <img src="6.png" class="imgRz">
</div> </div>
</div><!-- /row --> </div><!-- /row -->
</div> <!-- /container --> </div> <!-- /container -->
</div><!-- /white --> </div><!-- /white -->
<div id="anon2"> <!-- <div id="anon2">
<div class="container"> <div class="container">
<div class="row"> <div class="row">
<div class="col-lg-8 col-lg-offset-2"> <div class="col-lg-8 col-lg-offset-2">
@ -164,9 +168,9 @@ curl ifconfig.me
<p>And that's it! We now have a (VPN -> Tor) setup, in case if your ISP doesn't allow Tor traffic, concealing it behind the VPN.</p> <p>And that's it! We now have a (VPN -> Tor) setup, in case if your ISP doesn't allow Tor traffic, concealing it behind the VPN.</p>
</div> </div>
</div><!-- /row --> </div>
</div> <!-- /container --> </div>
</div><!-- /white --> </div>
<!-- +++++ Footer Section +++++ --> <!-- +++++ Footer Section +++++ -->
<div id="anonb"> <div id="anonb">