Elektrine lite

← Feed

@brickfrog@lemmy.dbzer0.com

Post #3850523

2026-07-16 04:51 UTC

Not sure how you had it set up in VirtualBox but I’m guessing you should just do the same thing since that’s what you’re used to. The other comment is correct but if you need a slightly shorter version Bridge networking = Pretend the VM is its own separate physical computer connecting directly to your network. It is receiving an IP address from your network router, it is doing DNS through the network router, etc. And the network router is able to direct incoming internet traffic directly to the VM if configured that way so you could do stuff like port forwarding to a specific open port in the VM if you choose. NAT = The host system (your Linux computer) is pretending to be a virtual router for the VM, the VM is not doing any direct communication with the network router. The VM gets its IP address from the host computer (the virtual NAT router). Since the VM sits behind the host computer that means it’s double-NAT’d, all internet traffic goes through the host first. It is not possible to configure an incoming port forward from the internet router directly to the VM.

Replies (1)

  • @nootux@lemmy.ml 2026-07-16 05:00

    Excellent explanation, thank you very much. Since I am using a VPN configuration on the host computer, am I correct in thinking NAT is the option I want if I want all traffic routed through that? It seems to function that way at the moment (checking IP on speedtest). If I recall, I had it configured that way on virtualbox. I want everything to network wise to be piped through the host first so if in the future I have custom firewall rules etc on the host, those are in place from the sounds of it using NAT correct? Thanks again.

    Open ##3850653