On Tuesday 14 February 2006 10:53, Ted Percival wrote: > So in conclusion I'm guessing that there was recently an update to > dhclient that changed the way it deals with the interface, presumably > taking it down and up again before requesting an address, but not > bringing it back up exactly the way it was. I'm not sure why the DMA > messages only come up with dhclient, someone else will have to answer that. That got me thinking. I tried to run dhclient and associate the interface while it was DHCPDISCOVERing:
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3 receive_packet failed on eth1: Network is down DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12 DHCPOFFER from 192.168.0.1 DHCPREQUEST on eth1 to 255.255.255.255 port 67 DHCPACK from 192.168.0.1 SIOCADDRT: File exists bound to 192.168.0.14 -- renewal in 43200 seconds. Success! Thanks for the pointer, Tim _______________________________________________ Bcm43xx-dev mailing list [email protected] http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
