https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6082
--- Comment #17 from Holger Pfrommer <hpfrommer@xxxxxxxxxxxx> 2011-11-14 07:54:12 PST ---
The problem why I originally intended to suppress the bit-field display is that
the content that is decoded by this dissector is no real frame data but
additional information which is used to provide some additional info about the
following Ethernet frame itself (which is sadly not supported by pcap natively,
maybe pcap-ng but thats another discussion...).
So the user is not interested in the origin (the single bits) of this
information, he just needs to know the port number or the frame length,
regardless of the way how this information is stored (which bits contain the
info). Contrary to an Ethernet frame's content, which of course is of interest
to the user in each single bit of the message.
This is also the reason for not displaying the version field. The user simply
is not interested in the version of the link-layer header, the dissector itself
of course has to decode it correctly.
You may compare this to the way the "Frame" tree is generated: if you decode
the timestamps etc. from a pcap file you see the frame's timestamp in various
formats, the frame's length in bytes and bits etc. but you don't see how this
information is physically stored (in which bits/bytes) in the pcap file.
So, thats why I used proto_tree_add_uint in my original implementation.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
