Ethereal-dev: RE: [Ethereal-dev] help with broken-up messages running atop TCP?

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

From: nak26 <nak26@xxxxxxxxxx>
Date: Thu, 08 May 2003 13:44:23 -0400
I decided to revisit our conversation...

>However, with the current scheme, "tcp_dissect_pdus()" would set the
>reported length to the length from the header, causing the
>"Unreassembled Packet" error to be reported with BoundsError and show up
>as "Short Frame", rather than as "Malformed Packet" or "Unreassembled
>Packet".

If it shows as "Unreassembled Packet", would that cause ethereal to
reassemble the conversation. If not, how then calling tcp_dissect_pdus()
would help me in reassembling broken-up messages. I guess, if you
describing a use case would be most appreciated.

>If the packet isn't being reassembled, "tcp_dissect_pdus()"

Following my previous question, how exactly the packet reassembly
is triggered?
When I right click on the "Short Frame" packet and choose followTCPstream I 
see 
the whole conversation. Can this be handed to my dissector as a tvb?

>I suspect that, in this case, your packets aren't getting reassembled,
>for whatever reason. Is the TCP checksum valid?

The TCP checksum, as reported by Ethereal, is "correct".

Can you suggest something else besides calling tcp_dissect_pdus() that can 
help in these situations. README.developer mentions "conversations". Can they 
be helpful in such cases?

Thanks, Nik