On Wed, 2007-08-01 at 12:45 -0700, Ramanathan Ramadass wrote: > 2. I am finding some odd behaviour w.r.t. Dup Acks. While I am hunting > it down; I am not sure whether it is a known problem and/or whether it > has been fixed. Attached is a trace of the problem. It was generated > using “nc” (netcat). In the trace; > > - 20.1.1.2 is the Linux client > > - 10.1.1.2 is our system using lwIP’s TCP.
Hmm, no obvious ideas about what might be causing this but I can confirm that it doesn't look right. I suppose it could be caused by there being some confusion within the stack about the delayed ACK flag. If this got set when it shouldn't do (or not cleared when it should), then the fast timer went off, it might result in the stack sending an extra ACK packet. To see if this is happening, search for TF_ACK_DELAY within the source, and you should find all the places that set or clear this flag. I'd try adding some tracing to see when this is getting set, and whether the duplicate ACK packets sent are due to it being set when the timer goes off. Hope that helps Kieran _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
