Ethereal-dev: Re: [Ethereal-dev] [RFC] specially mark protocol fields "generated" by Ethereal?
Hi,
it is an interesting question. I was assuming that in the middle pane
the
protocol fields are displayed in the sequence they appear in the packet
(and related to the layer in the stack). For other thinks I was using
hidden fields and I'm currently working on analysis stuff which I
thought
would be display best in a separate window via the Statistics menu.
We should have one way to handle this stuff across al protocols to have
a simple und coherent GUI.
Any suggestions?
Best regards
Michael
On Apr 24, 2004, at 7:01 PM, Ulf Lamping wrote:
Hi List!
It's sometimes confusing to distinguish between protocol fields
derived from the capture data and fields that are generated by
Ethereal while dissecting "from knowledge" (e.g. from context
information).
Example:
In the DCE-RPC dissecting are some protocol fields generated by
knowlegde from context, like a hint to the response in a request
packet, looking like.
Response in frame: 10
This means that the response PDU to the current one is in packet 10.
This protocol field has no data representation inside the packet.
From the DCE/RPC desegmenting, I got the idea to put some brackets
(what's the correct english name for this brackets?) around the
Ethereal generated info, so this will look like:
[Response in frame]: 1
I've checked in an example of this in the DCERPC dissector (but I can
easily remove it again, if others really don't like it).
What do others think of the idea, to put this brackets around field
names of Ethereal generated protocol fields in general?
Regards, ULFL
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
