In article <2b5e566d0809171242j56e1400ax2e00db8a133306c4@xxxxxxxxxxxxxx> you wrote: > Ahhh! I'm also seeing a single TCPDSACKRecv and a single TCPTimeout > at the same time. > > Does TCPDSACKRecv mean that the SACK was dropped? Oh I am guessing now, but I think it was recognized that the dup SACK was not a sign of a congestion. So it undid the window shrink. That might explain the 3 Counters to go up (whereas TCPDSACKRecv without undos affects bandwith, with undos it reovers) But that is just a really wild guess (sorry for the noise but I thought if nobody else offers a theory...) Gruss Bernd -- To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
