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: > > > > I've seen this problem intermittently before. Every once in a while, > > > > this happens (the adapter it happens on doesn't matter): > > > > > > > > # 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 > > > > > > DHCP process goes > > > > > > 1. Discover > > > 2. Offer > > > 3. Request > > > 4. Ack > > > > Ooooooh, that's very good to know. I didn't know it worked like that! > > Thanks. > > > > > In the above, the request for the offered address was never > > > acknowledged, so it asked again, and then went back to discovery. > > > > But how do you explain the "No DHCPOFFERS received" phrase (that you > > snipped)? That would seem to say that the problem is not that the > > server never ACK'd, it's that the server never OFFER'd.. except it > > did, and dhclient 'knew' that. > > > > I didn't read it literally as if no offers were received throughout > the entire process. I read it as "no offers received during this > discovery period". >
Okay... so why did it bother going into a second discovery period after getting an offer? -Nick
