When you run ifconfig -a to get the MAC addresses of the enp0s8 interfaces on both machines and also run arp -n to display the ARP cache, you will see that the MAC address of boxA is known on boxB and vice versa. You should be able to ping boxB as 192.168.50.5 from boxA and similary boxA as 192.168.50.4 from boxB. So we should expect that the machines can talk to each other via this device, and in fact they can. However, the trick is that both machines are actually connected to the same virtual device, as in the following diagram. There is a virtual network interface enp0s3 which is connected to the NAT device, and there is a virtual interface enp0s8 which is connected to vboxnet0 via the mechanisms discussed in the previous post.

In each virtual machine, the situation is as in the last post. Again, there is the virtual device vboxnet0 which has an IP address assigned to it, and there is a new entry in the routing table which sends all traffic for the network 192.168.50.0 to this device. When we inspect the network on the host, we see nothing which is really unexpected. When both of them are running, use vagrant ssh boxA and vagrant ssh boxB to connect to them. This will bring up two virtual machines, boxA and boxB. To run the example, you can again clone my repository and use the prepared Vagrantfile. In this lab, we will connect two virtual machines that both use host-only networking. Lab3: Virtualbox host-only networking with more than one machine Now let us see how we can establish virtual networks connecting more than one machine. So far, we have been playing with virtual networking for one virtual machine, connected to the host.

What is virtualbox networking