Re: Strange SACK behavior in 2.2.x

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello!

> After a while, the lost segments are retransmitted and properly
> acknowledged.

After a while? Did you not forget that SACKs are invalidated
after RTO?

>		 However, the segments previously SACK'ed are not
> included in this acknowledgement, forcing retransmission of them.

And this smells like severe bug at receiver side.

> AFAIK, since the reciever has sent an SACK for a segment, it is received
> OK and probably buffered 

And apparently discarded, as soon as receiver does not send them more. :-)


> For a visual description, see the zoomed tcptrace/xplot output at
> http://www.cse.kau.se/~di5alfs/tt/closeup.ps

Anyway, if you still did not know answer, send normal tcpdump, please.
I cannot read such graphical exersizes anyway.

Alexey
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux