Comment # 5
on bug 12429
from João Valverde
(In reply to Betty DuBois from comment #3)
> (In reply to João Valverde from comment #2)
> > I agree with your comments but I think this should be addressed by improving
> > the IP DSCP column format (as opposed to a custom field column).
> >
> > Have you tried that? It displays in decimal, so not an immediate solution,
> > but that's trivial to fix.
>
> João,
>
> If modifying the DSCP column format would be better/easier, I am all for it.
> I have tried using the decimal format of the DSCP column, but students find
> it confusing and are looking for the IETF abbreviation, so if that could be
> switched - it would be wonderful. (I teach for Wireshark U)
>
> Thanks!
Thanks for the clarification. My comment was intended to suggest making the bug
against the IP DSCP column (in decimal) and not the "ip.dsfield.dscp" column
(in extended textual format).
The first is much easier to change because it's just a matter of changing the
string format specifier. The latter is not configurable without making an ugly
special case in the code, AFAIK. Of course, changing the field display format
to "short textual" would be an option. But column length is a very dubious
rationale for changing the field format to me...
I pushed a patch to change the "IP DSCP" column from decimal to text some time
ago but it kind of stalled:
https://code.wireshark.org/review/#/c/10701/
You are receiving this mail because:
- You are watching all bug changes.