Wireshark · Ethereal-dev: Re: [Ethereal-dev] RE: [Ethereal-users] Re: H.225 SETUP not recognised ? (2)

[Guy Harris <gharris@xxxxxxxxx>]

On Fri, Mar 19, 2004 at 10:36:30AM +0100, Biot Olivier wrote:
> [To ethereal-dev now] We should enhance reassembly-and-matching code so that
> this type of behavior does not occur anymore.

E.g., by putting into the protocol tree, for all the cases where the TCP
reassembly code puts a "TCP segment data" item into the protocol tree
(i.e., where the data in that segment is saved for reassembly rather
than being dissected), a hidden item with the protocol ID for the
protocol whose dissector started the reassembly?

That will, I think, work for TCP - but for other protocols, where the
reassembly is done above the layer that handles the reassembled data
(e.g., IP fragment reassembly), that won't do it; we'd have to handle
that in some other way.