If memory serves me right, John Capo wrote: [TCP weirdness]
> I see exactly the same behavior on 3 -stable machines running kernels > from late October and early November. Another -stable machine with > a kernel from late September does pause but not as consistently as > the later kernel machines do. The client machine is running a > kernel from early November. How early in November? I'm staring at this commit message and wondering if it has any relevance to your situation: ----- revision 1.107.2.18 date: 2001/11/12 22:11:24; author: nate; state: Exp; lines: +3 -1 MFH: V1.139 when newreno is turned on, if dupacks = 1 or dupacks = 2 and new data is acknowledged, reset the dupacks to 0. The problem was spotted when a connection had its send buffer full because the congestion window was only 1 MSS and was not being incremented because dupacks was not reset to 0. Reviewed by: jlemon ----- Bruce.
msg29032/pgp00000.pgp
Description: PGP signature
