| | 1 | '''[UPDATE]''' |
| | 2 | |
| | 3 | I have performed a lot of testing with host-only networks (up to and including version 4.3.28) and it seems that there are several bugs with this thing at least on MS Windows hosts:[[BR]] |
| | 4 | When 1st (default) adapter is there and you add a second one, then:[[BR]] |
| | 5 | a) Set IP address to 172.16.1.2 with mask 255.255.255.0; new network adapter in Windows network control panel is OK. In VirtualBox UI, a generated IP address with mask 255.255.0.0 is shown instead. Interface is malfunctioning (of course).[[BR]] |
| | 6 | b) Workaround posted by 'Bright' does not work either. You can remove all network adapters and create a new one. New one will not work as expected (at least sometimes).[[BR]] |
| | 7 | c) It randomly happens that if I remove all adapters and create two new ones, then '''no error are reported.''' After closing and re-opening the VirtualBox UI, none of the network adapters are still there (also not in the MS Windows network control panel).[[BR]] |
| | 8 | |
| | 9 | Moreover, once the host-only interface gets configured in the right way, then starting a virtual machine and pinging the (static) IP configured on eth1 in the VM (in my case: 172.16.1.15) from the physical host takes up to fifteen (15!!!) seconds until the interface comes up and pongs. Please note that the services in the VM bound to this IP are up and running after approx. four seconds. Once it is up and running, then everyhting works smoothly, though.[[BR]] |
| | 10 | |
| | 11 | '''[PREVIOUS POST]'''[[BR]] |
