Hello!
> 14:03:37.621234 client > server: F 3233940357:3233940357(0) ack 2584922207 win 31360
><nop,nop,timestamp 40250 1587826> (DF)
>
> Server keeps sending, valid for half close.
>
> 14:03:37.871174 server > client: P 2584930895:2584932343(1448) ack 3233940357 win
>31856 <nop,nop,timestamp 1588068 40248> (DF) [tos 0x10]
> 14:03:37.871174 server > client: P 2584932343:2584933791(1448) ack 3233940357 win
>31856 <nop,nop,timestamp 1588068 40248> (DF) [tos 0x10]
>
> Client sends reset, server should abort. Interesting that RST does not
> include a timestamp.
RSTs should not include timestamps.
> 14:03:38.121117 client > server: R 3233940357:3233940357(0) win 0 [tos 0x10]
This RST is too old, this guy has already sent us this sequence number in FIN.
It is out of window and it is dropped, certainly.
> But we keep sending. Our ACK does not include the RST sequence so
RSTs have no sequence number.
> All of a sudden, we include the RST sequence number in our ACK! We
It is not RST's, but FIN's sequence number.
> send two ACKs (why?) and then we send more data, even after recognising
> the RST. Stuffed.
I see no RST.
> 25 minutes later we give up. No RST from the client, they probably
> dropped off the net.
All is OK. Client is seriously broken.
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
