<<On Fri, 30 Nov 2001 00:47:09 -0600 (CST), Jonathan Lemon <[EMAIL PROTECTED]> said:

[Quoting Bruce Mah:]

>> happens.  In *most* cases, the receiver somehow gets the missing data
>> because you can later see it acking later sequence numbers.  The first
>> place I saw this was at :41.504152.

Those are not duplicate acks because the window is still getting updated.

>> Another place to look is the large number of consecutive dupacks
>> starting around :41.978767.  I don't know what's happening here, but
>> after a long time (about a second?!?) the sender finally gives up and
>> sends the receiver what it wants.

> Yes, I think that area (I was looking at it too) provides a fairly
> good illustration that fast retransmits are broken.  The transmit 
> at 14:01:42.969338 appears to be the retransmit timer finally kicking in.

Yes, that's the conclusion Tim Shepard and I came to as well.

-GAWollman


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message

Reply via email to