Ethereal-dev: Re: [Ethereal-dev] patch to M3UA to call MTP3 dissector even when !tree

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

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Jeff Morriss <jeff.morriss@xxxxxxxxxxx>
Date: Mon, 27 Jan 2003 19:01:53 -0500

Guy Harris wrote:

On Tue, Jan 28, 2003 at 12:04:38AM +0100, Michael Tuexen wrote:


if I load my example file with the command given by you I DO see the
correct entry in the Info Column. I'm not using any Display filter.



Are you using any color filters (regardless of whether any of them match
any packets in the capture)?

Are you using any taps?

It's not really an issue of display filters vs. no display filters, it's
an issue of generating a protocol tree vs. not generating a protocol
tree - if a display filter is being used, a protocol tree is generated,
but that's also the case if a color filter, or a tap that does filtering
or passes the protocol tree to the tap, is being used.

(BTW, there's a similar problem with the RFC 3332 version of M3UA -
"dissect_parameter()" returns immediately if "tree" is null, even if the
parameter is "Protocol data".  I'll check in a fix.)
Oops, that would be the fault of my patch... I was only thinking of -05 and -06 calling the MTP3 dissector, not of the RFC version calling SCCP or ISUP... <sigh> 

--
Jeff Morriss
Senior Software Support Engineer
Ulticom, Inc.
Helpdesk: +1-856-787-2765
Fax: +1-856-222-9947