[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [bug #28288] Data after FIN in oos queue

From: Simon Goldschmidt
Subject: [lwip-devel] [bug #28288] Data after FIN in oos queue
Date: Mon, 14 Dec 2009 16:19:33 +0000
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv: Gecko/20091102 Firefox/3.5.5

Follow-up Comment #4, bug #28288 (project lwip):

> If we get two FINs at different sequence numbers we should
> definitely reset the connection so that the application at the
> other end might be made aware that there has been a problem and
> some data are not delivered.

Hm, that can happen in two cases:
a) Out-of-sequence, this case is quite easy to check, as we have both
segments to compare
b) In-sequence (i.e. the second FIN arrives in a closed state), this case is
not that easy to check as we would have to remember the seqno of the first FIN
to know it isn't a retransmission.

What do other stacks do about this? What do RFCs (or the requested comments,
if any) say about this?


Reply to this item at:


  Nachricht geschickt von/durch Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]