Wireshark-bugs: [Wireshark-bugs] [Bug 12765] After upgrading to 2.0.5 IP DSCP Value column shows

Date: Fri, 26 Aug 2016 22:00:12 +0000

changed bug 12765


What Removed Added
Status INCOMPLETE CONFIRMED
CC   [email protected]

Comment # 12 on bug 12765 from
I agree that we shouldn't have backported a change to a stable branch that
changed the format of a column.  As mentioned in the ReleasePolicy:

https://wiki.wireshark.org/Development/ReleasePolicy#Rationale

"stable" releases don't just mean "it doesn't crash" it is supposed to also
mean "the interfaces don't change."

But, now that it's changed I would suggest that we don't change it back (a 2nd
interface change doesn't seem better even if it does restore functionality).


That being said:

1) Why is DSCP even a column?  We have custom columns for this kind of thing. 
(Also see the next comment.)

2) If you add the DSCP field as a custom column (expand the DSF field, right
click on the DSC field, and select "Apply as Column") then you have your choice
as to whether you see EF or 46 (right click on the custom column and enable or
disable "Resolve Names" to change the behavior).  Yes, this is another reason
to remove the hard-coded DSC column...


If #2 works I'd suggest removing the DSCP column (in master only, of course)
and closing the bug.


You are receiving this mail because:
  • You are watching all bug changes.