On Fri, Sep 16, 2011 at 4:25 PM, Susam Pal <[email protected]> wrote: <snip>
> > The guest isn't running any DHCP server. VirtualBox is set to provide > the DHCP service for the host-only adapter. So, it should not be > possible for the guest OS to override the DHCP service configured in > the VirtualBox settings. > > >From what I found, the guest OS continues to successfully get an IP > address assigned to itself from the first DHCP server IP address even > after I have changed the DHCP server IP address to something else in > VirtualBox. This looks to me like a configuration bug in VirtualBox > due to which the new DHCP configuration I have set is not being used. > > Should I open a bug for this at http://www.virtualbox.org/wiki/Bugtracker ? > > Regards, > Susam Pal I went back and re-read your OP and I think I misunderstood your original post, I'm sorry for the noise. I don't think this is a bug per-se. OK so you run vbox and the host only network is enabled and has a dhcp server running. Fine. You have a client and it gets IP addresses properly. You change the settings on the dhcp server and your new settings are not respected. So far this is exactly the behavior I'd expect. If I had a real physical network it would behave exactly as you have described and there would be no bug. There is a missing step here. Somewhere the DHCP server service needs to be restarted so that it rereads its configuration file and adjusts itself to the new settings. The problem is how do you restart the dhcp server service in vbox so that the new settings are adopted. There is no way to restart just the dhcp server service in vbox (maybe there should be) Try your test procedure this way: Open vbox admin panel and run vm from it, ensure that ip addressing works at all (you've done this) Change dhcp server settings in preferences. shutdown vm shutdown admin panel restart admin panel check dhcp server settings, are they preserved? (should be yes) start vm are new settings respected? (they should be) Keep in mind that the dhcp lease on the client has not expired yet, and the client is going to want to reuse its current unexpired settings. There will be a negotiation with the dhcp server over the current lease that now represents an IP address outside the IP scope. I see two possible issues here. 1) maybe you should file a feature request with the developers so that the host only network settings can be reset on the fly and the internal dhcp server service restarted manually. 2) maybe the negotiation over a current-but-no-longer-scoped ip address is not working properly. This would be a bug report. Let me know what you find out. Rance ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA http://p.sf.net/sfu/rim-devcon-copy2 _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
