One thing I have noticed this morning is that the filter syntax has changed in 1.4.0rc1. In 1.2.x it used to be:-
ip.dscp.value
which did display just the decimal for a packet under this column heading e.g.
46
whereas the new filter syntax in 1.4.0rc1 is:-
ip.dsfield.dscp
and this displays the verbose description for a packet under this column heading:-
Differentiated Services Codepoint: Expedited Forwarding (0x2e)
I have also noticed that the same has happened to the 802.1P COS field when used as a column. It uses the filter syntax of:-
vlan.priority
and this column now displays the verbose value on any packet where the 802.1P Priority is set to decimal 3.
Excellent Effort
Whereas it used to display just the decimal of:-
3
If these columns would need to be unresolved to display the decimal, please could you make this an option? This way it would keep column widths for these two fields to a minimum, whilst still conveying useful information?
Keith French.
________________________________
From: wireshark-users-bounces@xxxxxxxxxxxxx on behalf of Guy Harris
Sent: Wed 23/06/2010 23:01
To: Community support list for Wireshark
Subject: Re: [Wireshark-users] Adding DSCP column in Wireshark 1.4.0rc1
On Jun 23, 2010, at 2:54 PM, Jaap Keuter wrote:
> That would required the option of having custom columns with unresolved values.
> An interesting concept in itself.
...which might let us have the type of column and resolved vs. unresolved as separate notions, even for non-custom columns.
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
<<winmail.dat>>
