Both of these dumps were generated with the 100ms patch in place:
http://lyonlabs.org/ip65-timer-wait.txtfirst dump:
http://lyonlabs.org/ip65-dump3.pcapThere are usually five discovers and five offers; in this case there are
only four. Note how quickly my router (192.168.1.99) sends the offer
packets (2-3 ms apart). Is it possible that ip65 is trying to send
another request immediately after one had just been put into the buffer
but before the CS8900A has had time to send it? or would the send happen
independently of ip65 repeatedly checking for buffer space? Maybe if a
"don't send anything else while I'm doing this" flag were set...? I broke
into the debugger several times to verify that he was stuck in the transmit
loop; eventually, one of the times I started running again, the packet was
immediately sent (see last packet, at 318 seconds). The router shows that
an IP address of 192.168.1.109 was assigned.
second dump:
http://lyonlabs.org/ip65-dump4.pcapThis time, I just let it sit while I went to get a cup of coffee, and the
request was eventually sent... over 200 seconds after the last offer! The
router shows 192.168.1.109 assigned; notice again how quickly the offer
packets were sent.
Am I just being impatient? Should it be considered normal for the request
packet to go out after so long?