PHWinfo - Afficher un message - Does any packet transfer( fin,rst ) happen after tcp detects connection timeout occured ??

11/09/2007, 19h49

Ilkka Oksanen <ilkkao@omppu.modeemi.cs.tut.fi> wrote:
> Any reasonable TCP stack sends RST segment after final
> re-transmission timeout. Socket is closed after that. There
> is no point to expect that FIN handshake would work after
> multiple unsuccesful retransmissions of previous segment.

Well, the RST isn't necessarily any more likely to get there than the
FIN, but if it does, it does communicate the "right" message, which is
that the connection is toast.

Especially if the RST is from a stack which actually "extends" the RST
segment with some ASCII for the abort reason

Of course one only
sees that with a packet sniffer...

rick jones
--
Process shall set you free from the need for rational thought.
these opinions are mine, all mine; HP might not want them anyway...

feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...

11/09/2007, 19h49	#3
Rick Jones Messages: n/a Hébergeur:	Re: Does any packet transfer( fin,rst ) happen after tcp detects connection timeout occured ?? Ilkka Oksanen <ilkkao@omppu.modeemi.cs.tut.fi> wrote: > Any reasonable TCP stack sends RST segment after final > re-transmission timeout. Socket is closed after that. There > is no point to expect that FIN handshake would work after > multiple unsuccesful retransmissions of previous segment. Well, the RST isn't necessarily any more likely to get there than the FIN, but if it does, it does communicate the "right" message, which is that the connection is toast. Especially if the RST is from a stack which actually "extends" the RST segment with some ASCII for the abort reason Of course one only sees that with a packet sniffer... rick jones -- Process shall set you free from the need for rational thought. these opinions are mine, all mine; HP might not want them anyway... feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...