this post was submitted on 07 Nov 2023
4 points (100.0% liked)

networking

2779 readers
2 users here now

Community for discussing enterprise networks and the ensuing chaos that comes after inheriting or building one.

founded 1 year ago
MODERATORS
4
submitted 1 year ago* (last edited 1 year ago) by HW07 to c/[email protected]
 

So on my host I run Mullvad VPN all the time due to living in one of the X eyes countries and being over-paranoid, but when I torrent I do almost no uploading due to Mullvad blocking port forwarding. I had the bright idea to create a VM then attach it to my network in a way to completely bypass my host (also running Linux) connection and in-turn bypass Mullvad, I'd then connect this VM to my own Wireguard server that I rent overseas and configure port forwarding on that. I think I'm almost there however I seem to have hit a roadblock that I think the only workaround is attaching a second ethernet cable to my host, in order to get another interface so that the VM doesn't steal my host's connection.

Doing the dual ethernet setup isn't impossible, but it is extra cables and dongles that I'd rather do without, so I was wondering if I could create a second IP address on my host and pass that into the VM to use? I'm using qemu and virt manager for my virtual machines, Artix on my host and probably Linux Mint on my torrent VM.

Again I have no idea if this is possible or not, I simply don't know enough about networking yet to know for certain. I feel like it is but I wanted to ask some people who know what they're talking about :D.

top 2 comments
sorted by: hot top controversial new old
[โ€“] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)

yeah its 100% possible, check the qemu manual for your VM network backends. https://wiki.qemu.org/Documentation/Networking

A tap device, and have it bypass your mullvad routing rules

[โ€“] HW07 1 points 1 year ago

Great! So I'm following the Setting up taps on Linux part of the docs and I understand what it's doing however I get caught up with the last 3 commands in the second block, it returns that the operation is not supported on my machine from RNETLINK. Also these changes don't persist after reboot...