Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Ethereal-dev: Re: [Ethereal-dev] Desegmentation atop TCP problem / TCP reassembly and desegmen

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Peter Johansson <Peter.xc.Johansson@xxxxxxxxxxxx>
Date: Wed, 01 Sep 2004 14:53:14 +0200
Jeff Foster wrote:

This will work for a fixed length PDU, which does seem to be Peter's situation, or a PDU with a length value in the start of the PDU.

This is exactly my situation.

---8<--- snip snip ---8<---

From: Ronnie Sahlberg
Sent: Wednesday, September 01, 2004 4:14 AM

---8<--- snip snip ---8<---

remember to enable BOTH the tcp preference as well as your own
preference for your protocol to enable desegmentation.

Yes, thank you. I tracked this down myself a few hours ago (reading the source code). Enabling "Allow subdissector to reassemble TCP streams" in the preferences for TCP made my life a whole lot easier. I would really have liked to see something about this in the README.developer. It would sure help others in the future. I would like to see additional notes in the README.developer, section 2.7, showing the use of "pinfo->can_desegment". It seems rather vital after having read through a bunch of other dissector sources.

Currently I am instead receiving too much data in the reassembled packets. But I guess that is a problem with my code. I will try and hunt it down myself...

Thanks for your replies!

/ Peter