https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4968
Guy Harris <guy@xxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Platform|x86 |All
Summary|New DSCP filter syntax uses |DSCP column can't be
|hex not decimal |displayed as decimal
OS/Version|Windows 7 |All
--- Comment #2 from Guy Harris <guy@xxxxxxxxxxxx> 2010-07-02 12:18:32 PDT ---
...and the field has always been ip.dsfield.dscp; there was never an
ip.dscp.value field in Ethereal/Wireshark.
(In addition, in a filter, an integral-valued field can be compared with a
decimal, hex, or octal value, regardless of the base used to display the field
- you can do "ip.dsfield.dscp eq 0x2e" or "ip.dsfield.dscp eq 46" or even
"ip.dsfield.dscp eq 056" in a filter - although if you generate the filter with
"apply as filter" or "prepare as filter" the value being compared against will
be generated using the base of the field.
I've retitled the bug to indicate the actual problem.
The reason why the DSCP field is displayed in hex is probably that it's shown
as binary in, for example, the IANA registry of codepoints. If it's more often
given in decimal, we could change it to BASE_DEC to display it - in a custom
column *and* in the packet detail display (the two would always be the same for
a custom column) - in decimal, or to BASE_DEC_HEX or BASE_HEX_DEC to display it
both as decimal and hex.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.