The real problem is the fields below Frame Control
and above Fixed Parameters (addresses, etc).
Perhaps we could put them in a nice, neat category and
make it a top level entry? Say, "Media Access Control"
or some derivative?
- Joe
At 07:53 PM 6/20/2001, you wrote:
> In the latest anon-CVS I just compiled, 802.11 packets are now
> completely within the tree, instead of having the expandable
> portions (fixed and tagged parameters) able to be opened
> independently. Since the arguably most relevent items
> are in the tagged parameters, exploding the 802.11 frame,
> then the tagged parameters, usually leaves too little room to
> display any of the summaries or hex info. I won't complain
> (loudly) if this change is here to stay, but with the limited real estate
> on this laptop's screen, every line counts; I like being able to expand
> only what I need to see. Therefore, I hope it's a bug. ;)
It's a consequence of fixing the bug that caused it to dump core when
you tried to get the protocol statistics.
As I said in my response, in Ethereal, top-level entries in a protocol
tree *MUST* correspond to protocols - no exceptions. Neither the fixed
nor the tagged parameters corresponded to protocols, so they could not
be put at the top level of the protocol tree.
The only alternative is to declare a new protocol - "IEEE 802.11
Management", say - and put the fixed and tagged parameters under an
entry for that protocol. That still takes one more line in the protocol
tree, for that protocol's top-level item, but so it goes....
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users
