Quoting Sergey Babkin ([EMAIL PROTECTED]):
> John Capo wrote:
> > 21:41:49.001039 client.4427 > server.22: P 144:192(48) ack 12937 win 17376 
><nop,nop,timestamp 53827954 105528895> (DF) [tos 0x10]
> > 21:41:49.001073 server.22 > client.4427: . 28049:29497(1448) ack 192 win 17328 
><nop,nop,timestamp 105529049 53827954> (DF) [tos 0x10]
> > 21:41:49.001085 server.22 > client.4427: P 29497:30313(816) ack 192 win 17328 
><nop,nop,timestamp 105529049 53827954> (DF) [tos 0x10]
> > 21:41:49.109131 client.4427 > server.22: . ack 12937 win 17376 <nop,nop,timestamp 
>53827967 105528895> (DF) [tos 0x10]
> 
> And here a _very_ pathological thing has happened: the server
> just forgot to send the data between sequence numbers 12937
> and 28049. Since the dump was done on the server side, this suggests
> that something very bad has happened with the TCP state on
> the server side. Possibly the value of the current sequence number
> in the protocol control block got overwritten by something.

Very interesting, I overlooked that.  Full dumps:

    http://www.irbs.net/server-dump.html
    http://www.irbs.net/client-dump.html

I was beginning to think it was a client problem since 4.3 clients
and Winblows clients work fine.  A -stable client built from November
7 CVS code does not see the pause either.  The client in the dump
is built from CVS on November 11.

John Capo


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

Reply via email to