On Dec 21, 2007 6:49 PM, Nick Guenther <[EMAIL PROTECTED]> wrote: > On Dec 21, 2007 6:26 PM, Kian Mohageri <[EMAIL PROTECTED]> wrote: > > On Dec 19, 2007 8:25 PM, Nick Guenther <[EMAIL PROTECTED]> wrote: > > > On Dec 19, 2007 7:53 PM, Kian Mohageri <[EMAIL PROTECTED]> wrote: > > > > On Dec 19, 2007 10:26 AM, Nick Guenther <[EMAIL PROTECTED]> wrote: ... > > > > > # dhclient de0 > > > > > DHCPREQUEST on de0 to 255.255.255.255 port 67 > > > > > DHCPREQUEST on de0 to 255.255.255.255 port 67 > > > > > DHCPDISCOVER on de0 to 255.255.255.255 port 67 interval 5 > > > > > DHCPDISCOVER on de0 to 255.255.255.255 port 67 interval 12 > > > > > DHCPDISCOVER on de0 to 255.255.255.255 port 67 interval 12 > > > > > DHCPOFFER from 192.168.0.1 > > > > > DHCPREQUEST on de0 to 255.255.255.255 port 67 > > > > > DHCPREQUEST on de0 to 255.255.255.255 port 67 > > > > > DHCPDISCOVER on de0 to 255.255.255.255 port 67 interval 7 ... > Okay... so why did it bother going into a second discovery period > after getting an offer?
Because that offer could not be confirmed: the server that made the offer didn't respond to the client's request. Servers _may_ offer the same address to multiple clients concurrently; clients can only use an address after it has been confirmed. So given that it can't use that address, what do you expect it to do other than restart discovery? (For the full details, check out RFC 2131 <http://www.rfc-editor.org/rfc/rfc2131.txt>) Philip Guenther
