Wireshark mailing list archives

Re: Handling TCP packets reordering


From: Max Dmitrichenko <dmitrmax () gmail com>
Date: Thu, 5 May 2011 04:36:37 +0400

2011/5/5 Jeff Morriss <jeff.morriss.ws () gmail com>:

I did stumble across a (apparently unrelated) problem in that it will fail
if you see a gap while the subdissector is returning
DESEGMENT_ONE_MORE_SEGMENT (as HTTP does until it gets all the headers): in
that case TCP has to assume that the current message is not part of the
existing multisegment_pdu--which unfortunately breaks things.  Not sure what
can be done about that...

Such situation can be detected inside the dissector if we know position in
the stream and have the tcpinfo->seq for the packet. The application protocol
dissector can use this knowledge to signal down to the TCP dissector.

Can we make TCP dissector to delay such marked packet and resubmit
it (possibly reassembled with other fragments) to the subdissector again?

--
  Max
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe

Current thread: