On Dec 19 2007 12:43, James Nichols wrote: >On 12/19/07, Eric Dumazet <[EMAIL PROTECTED]> wrote: >> James Nichols a écrit : >> >> So you see outgoing SYN packets, but no SYN replies coming from the remote >> >> peer ? (you mention ACKS, but the first packet received from the remote >> >> peer should be a SYN+ACK), >> > >> > Right, I meant to say SYN+ACK. I don't see them coming back. >> >> So... Really unlikely a linux problem, but ... > >I don't know how you can be so sure. Turning tcp_sack off instantly >resovles the problem and all connections are succesful. I can't >imagine even the most far-fetched scenario where a router or every >single remote endpoints would suddenly stop causing the problem just >by removing a single TCP option.
The router could be sooo crappy that it drops all packets from TCP streams that have SACK enabled and the client has opened 200+ SACK connections previously... something like that? -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
