Vboxnet fails to fully configure interface
rc.d/vboxnet fails to fully configure interface
Volodymyr Kostyrko c.kworr at gmail.com
Mon Jan 21 12:53:32 UTC 2013 Previous message: FreeBSD amd64 guest sometimes hangs during boot * Next message: rc.d/vboxnet fails to fully configure interface * Messages sorted by:*[ date ][ thread ][ subject ][ author ]
Hi all. After patching rc.d/vboxnet to run VBoxManage correctly I found that it doesn't create interface at all, as all interface specification is bound to user running machines. I had created a sample config file for VirtualBox: <VirtualBox xmlns="http://www.innotek.de/VirtualBox-settings" version="1.12-freebsd"> <Global> <ExtraData> <ExtraDataItem name="HostOnly/vboxnet0/IPAddress" value="192.168.56.1"/> <ExtraDataItem name="HostOnly/vboxnet0/IPNetMask" value="255.255.255.0"/> <ExtraDataItem name="HostOnly/vboxnet0/IPV6NetMask" value="64"/> </ExtraData> </Global> </VirtualBox> But this only results in interface been created but not configured: vboxnet0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether 0a:00:27:00:00:00 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> media: Ethernet autoselect status: active This is very bad from a production perspective. Imagine that I want to run a number of machines on one host-only interfaces making parent host the firewall for all of them. Then no system service can start and bind to this interface prior to making it fully active. This covers at least named and isc-dhcpd as I prefer to use full fledged dhcpd server to be able to provide routing info, local dns servers and machine registration in dns. -- Sphinx of black quartz, judge my vow.