Hi! I would like to add a custom column for ptp.v2.ClockIdentity, but when I do this, the value of this field is represented in the column (packet list view) as a number while it shows as a hex-byte sequency in the packet details. I guess this is because the data type of the field itself is 64bit unsigned int, so my question is: Is there a way to let custom columns use the same representation that is used in the packet details? If not, I would really like to see this feature being added in later versions. This whole thing is one of the most powerful network analyzing tools (as we all know), but this thing would increase its usefulness even more for me (anybody else?). Thanks, Heiko asked 11 Oct '11, 01:30  Heiko closed 19 Mar '14, 05:53  grahamb ♦ |
This is a static archive of our old Q&A Site.
Please post any new questions and answers at ask.wireshark.org.
+1: many protocols feature fields with structured bitmasks that are very difficult to read in decimal (e.g. SMPP). the ability for Wireshark to utilize an arbitrary (user-supplied) format for its display columns would be highly useful. why stop at hex? binary, float, various date formats — just give us everything
printf(…)has :]Ask Wireshark isn't the place for Feature Requests, those should be added to the Wireshark Bugzilla, marking the item as an "enhancement".