[Feature] Add ability to have internal networks like VirtualBox

[isayakmondal]

Hi all, I'm wondering if it is possible to have an "Internal Network" configuration in UTM like VirtualBox

Internal Networking is similar to bridged networking in that the VM can directly communicate with the outside world. However, the outside world is limited to other VMs on the same host which connect to the same internal network.

Ref: Internal Network VirtualBox

I have tried using "Host Only" mode both with "Isolate Guest from host" turned on and off still I'm not able to achieve the functionality I want.

Context: I'm trying to run pfSense (emulated) and some client VM's and I want to setup a blank network so that my VM's will get the network configuration from pfSense and not UTM's/QEMU's/host's DHCP server.

*Note I have already tried passing direct QEMU arguments like -device virtio-net-pci,netdev=net0 -netdev vmnet-host,id=net0 but that still seems to get either no IP or IP from my host's DHCP server.

I think this might possible as UTM is based on QEMU as I was able to find How to create "internal network" using libvirt/QEMU/KVM stack.

[CrudeDiatribe]

Would love if this could be added to Apple Hypervisor guests and not just QEMU guests (even if each virtualization tech had to have separate internal networks).

I have a MacOS VM for running things I don't entirely trust and when my host Mac is on ethernet it's fine— it is easy to put the guest on its own network via VLANs. Would love the flexibility when the Mac was on wifi, but the setup has to be more complicated since no VLANs on WiFi. If I had a guest-only/internal network for a Linux firewall/router and the Mac guest to share, the former could control what the latter talked to.