Ethereal-dev: Re: [Ethereal-dev] non-registered things on the proto_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: Gilbert_Ramirez@xxxxxxxxxx
Date: Tue, 17 Oct 2000 16:39:16 -0500
You can use proto_tree_add_text() to add arbitrary text to the protocol
tree. You're right, the fields you add this way won't be filterable.
Remember, you never know when you or someone else may need to filter on a
particular field. That's what makes Ethereal so handy, compared against
other protocol analyzers that let you filter on only a few fields.

--gilbert

Mark Atwood <mra@xxxxxxxxx> on 10/17/2000 04:36:30 PM

To:   ethereal-dev@xxxxxxxxxxxx
cc:    (bcc: Gilbert Ramirez/Tivoli Systems)
Subject:  [Ethereal-dev] non-registered things on the proto_tree?





Okay. My dissector now dissects my packet headers very well. Now I'm
moving on the the payload portion. I have potentially a large number
of kinds of payloads, each one different, with lots and lots of fields.

Do I have to register them all in proto_register_foo, or can I add
things to the proto_tree without the fields be registered? (I assume
that unregistered things aren't filterable.)

--
Mark Atwood   |
mra@xxxxxxxxx |
http://www.pobox.com/~mra

_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev