On Sat, Sep 17, 2011 at 2:22 AM, Rance Hall <[email protected]> wrote: > On Fri, Sep 16, 2011 at 1:37 PM, Susam Pal <[email protected]> wrote: >> I am using VirtualBox 4.1.2 on Windows XP. I have running a Debian >> 6.0.2.1 virtual machine in VirtualBox. I see that after I update the >> DHCP setting for a host-only network adapter, the DHCP setting is not >> used by the Debian virtual machine. It still manages to get an IP >> address assigned by the old DHCP server. Here are the steps I >> performed listed down in detail to demonstrate the issue: >> >> 1. File > Preferences > Network > Add a host-only network. >> "VirtualBox Host-Only Ethernet Adapter" was created. >> >> 2. Edit "Virtual Host-Only Ethernet Adapter" and set: >> >> Adapter: >> IPv4 Address: 192.168.20.1 >> IPv4 Network Mask: 255.255.255.0 >> >> DHCP Server: >> Server Address: 192.168.20.100 >> Server Mask: 255.255.255.0 >> Lower Address Bound: 192.168.20.101 >> Upper Address Bound: 192.168.20.254 >> >> 3. I had a VM in which "Adapter 1" is set to: "Bridged Adapter". I >> updated "Adapter 2" to "VirtualBox Host-Only Ethernet Adapter". >> >> 4. Booted my VM (It's running Debian 6.0.2.1). Upon running: ifup >> eth1, I see that it gets DHCPACK from 192.168.20.100 and an IP address >> of: 192.168.20.101. >> >> >> So, everything is okay so far. Now, the issue I am facing follows in >> the next 3 steps. >> >> >> 5. Now I 'poweroff' the VM. >> >> 6. Edit File > Preferences > Network > "VirtualBox Host-Only >> Ethernet Adapter" and set: >> >> DHCP Server: >> Server Address: 192.168.20.110 >> Lower Address Bound: 192.168.20.111 >> (Left other fields untouched) >> >> 7. Now, if I boot my VM again and run: ifup eth1, I still see a >> DHCPACK from 192.168.20.100 and it gets IP address: 192.168.20.101 >> again. >> >> Why isn't the new DHCP setting being used? >> >> Regards, >> Susam Pal >> http://blog.susam.in/ | http://cotpi.com/ >> > > I tend to not use vbox to configure network settings for just this > reason. The guest OS can (and often does) override this setting based > on its on internal instructions. > > If I were you I would just use vbox to tell the vm how many network > adapters to emulate, what type of adapters they are, and how these > adapters are connected to (bridge, internal, whatever). > > Then configure the guests to do what you want for each adapter. > > HTH > > Rance >
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 ------------------------------------------------------------------------------ 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
