a 2nd line from your ISP, and using a USB to WiFi/Ethernet to connect to the 2nd router. The only solution I can think of would be to have a separate router, with a different public IP, i.e.

Even if using a USB WiFi adapter, the guest will still be part of the LAN and will be able to access anything inside the router.

But then the guest is isolated, and not going to have access to anything, except its own Internal network. To sum it up, if the guest has any sort of networking that it's NOT of the 'Internal' networking option, there can be no complete isolation. youll need to stop all the instances first multipass stop -all and tell Multipass to use libvirt sudo multipass set local.driverlibvirt All your existing instances will be migrated and can be used straight away. It's actually the guest that's protected by default, not the host. The host->guest on the othere hand, has to have some sort of port forwarding set specifically for that purpose.

Using NAT/NATservice, the guest can always access the host and the LAN, even if only by IP. It's the reason that I had to modify the Overview of Networking Modes Table from its first revision and add specifically the VMNet/LAN columns, after it was pointed out to me some time ago, that using NAT/NATservice a guest could access the host/host's LAN resources (IP printers, other computers, everything). Mpack wrote:In the NAT case the guest can't access the host

How to stop virtualbox interface