Opened 10 years ago
#13323 new defect
Stop pre-populating a DHCP server on fresh installs?
| Reported by: | phinze | Owned by: | |
|---|---|---|---|
| Component: | network/hostif | Version: | VirtualBox 4.3.14 |
| Keywords: | dhcp | Cc: | |
| Guest type: | all | Host type: | all |
Description
Hello there good VBoxers! :)
Vagrant core maintainer here. Working on an issue that comes up pretty regularly for folks in Vagrant-land:
https://github.com/mitchellh/vagrant/issues/3083
A fresh install of VirtualBox adds a default dhcpserver into its config.
https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Main/xml/Settings.cpp?rev=52312#L1520
This dhcpserver ends up messing up Vagrant's interface <-> dhcpserver accounting and causes any first-time user with a DHCP-using interface in their Vagrantfile to get a cryptic error message.
We've considered writing code to detect and remove this default config, but it seems the simplest solution would just be to have VirtualBox avoid the default config and leave dhcpservers blank for fresh installs. Since there's no vboxnet0 by default it seems like this is less surprising behavior than having a dhcpserver that references a nonexistent interface in its name.
Looking forward to your thoughts - thanks for your time!
Paul / phinze
