On Sun, Apr 28, 2013 at 05:29:05PM -0400, David Higgs wrote: > On Sun, Apr 28, 2013 at 4:00 PM, Kenneth R Westerback > <kwesterb...@rogers.com> wrote: > > On Sun, Apr 28, 2013 at 02:41:36PM -0400, David Higgs wrote: > >> Confirmed in 5.3-current downloaded several minutes ago. > >> > >> Steps to reproduce: > >> - Boot bsd.rd > >> - Select upgrade, hit enter until dhclient gets and assigns an address > >> - Complete upgrade or control-C, then restart the upgrade process > >> - dhclient on 2nd run REMOVES the assigned address > >> > >> Probably affects the bsd.rd install option as well. This does not > >> happen with 5.2 bsd.rd. > >> > >> Easy to work around, but probably not "right". > >> > >> Thanks! > >> > >> --david > >> > > > > Can't reproduce on amd64 -current here. I did control-C after getting > > dhclient lease, entered 'upgrade' at command prompt, and re-started > > upgrade. dhclient worked fine. Checked 'ifconfig' and the expected > > address was present. > > > > So more info you what exactly you are doing, on what machine are > > you doing it, and perhaps anything interesting in your dhclient.conf > > would be helpful. Thanks. > > > > .... Ken > > I would have provided output, but I haven't figured out how to log > console output from VMware images. Hopefully this will suffice: > > i386 / 5.3-current / RAMDISK_CD #120 > > dhclient #1 (good) > DHCPDISCOVER on vic0 to 255.255.255.255 port 67 interval 1 > DHCPOFFER from 172.16.223.254 (mac addr) > DHCPREQUEST on vic0 to 255.255.255.255 port 67 > DHCPACK from 172.16.223.254 (mac addr) > bound to 172.16.223.131 -- renewal in 900 seconds > > dhclient #2 (bad) > DHCPREQUEST on vic0 to 255.255.255.255 port 67 > Active address (172.16.223.131) deleted; exiting
Is there a configured ip address on the interface at this point? This is a message emitted by one dhclient on noticing that another one is active and has deleted the address the first one configured. It *shouldn't* mean that no ip address is configured. Now what is different in the virtual environment you are using that makes i386 timing different than amd64 ... dunno. .... Ken > > dhclient #3 (good) > DHCPREQUEST on vic0 to 255.255.255.255 port 67 > DHCPACK from 172.16.223.254 (mac addr) > bound to 172.16.223.131 -- renewal in 900 seconds > > amd64 / 5.3-current / RAMDISK_CD #132 > > dhclient #1 (good) > DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 1 > DHCPOFFER from 172.16.223.254 (mac addr) > DHCPREQUEST on em0 to 255.255.255.255 port 67 > DHCPACK from 172.16.223.254 (mac addr) > bound to 172.16.223.130 -- renewal in 900 seconds > > dhclient #2 (still good) > DHCPREQUEST on em0 to 255.255.255.255 port 67 > DHCPACK from 172.16.223.254 (mac addr) > bound to 172.16.223.130 -- renewal in 900 seconds > > /etc/dhclient.conf appears to be identical to between i386 and amd64. > I am sending an identical hostname FWIW, but I am only launching only > one VM at a time. > > initial-interval 1; > send host-name "vm"; > request subnet-mask, broadcast-address, routers, domain-name, > domain-name-servers, host-name; > > Let me know if you want me to try anything else. > > --david
