virtualbox.org

So I've got 2 ethernet adapters on my host PC. I want one to be host only, and one VM only. I don't want any traffic shared between the host and VM. Is this something you guys can walk me through?
Host is Windows 10. VM is Linux Mint.

If you are on a LAN, you can do that from the adapter settings in Windows. You can disable all the features except the VirtualBox NDIS6 Bridged Networking Adapter on one NIC and bridge your vm to that NIC. On the other NIC you disable that one, but leave all the others enabled and use it for the host machine. The host and guest will behave like two separate devices on the network.

Unfortunately I don't see that as an option in any device. Is there something I have to install?

*NVM i see it in the service install section. I install it on eth2, and disable everything but that one. Then bridge it to the Host only adapter?

Cubanbread wrote:service install section

Please post a screenshot using Upload Attachment so we can see you are on the same screen that Bill is showing.

Cubanbread wrote:I install it on eth2

There's nothing to install, as Virtualbox installs the NDIS Bridging driver already on the host network adapters. And 'eth2' is not a Windows host network adapter name, it's in Linux, and you're posting in Windows Hosts. So we need to check that there is no confusion, as networking has a lot of room for pebcak errors.

Bill's screenshot shows the Windows Host network adapter properties, found in the list of adapters by right-clicking the adapter and choosing Properties. Of your two physical host adapters, one will have only "NDIS Bridged" checked, the other will have everything normal checked except "NDIS Bridged".

Then Virtualbox's Bridged settings in the VM's Network settings will only allow you to Bridge to the one adapter that still has the "NDIS Bridged" checkbox checked. There are no special settings in the VM OS to make, except, if you want a static IP address in the VM OS in the correct range delivered by the LAN attached to the NDIS-Bridged-enabled adapter.

Sorry for the confusion Scott. I was just using the name eth2 instead of my "VM Adapter". Everything seems to be working now.

I have never seen that missing on a Windows PC which has VirtualBox installed. Did you install a second network adapter after you installed VirtualBox?