Maynard, Chris wrote:
If a given udp port does not have a name associated with it,
epan/resolve.c:get_udp_port() simply returns a string containing the decimal
value of the port number. However, in that case, the udp dissector ends up
displaying the decimal port value twice, as in "decimalport (decimalport)",
in both the udp summary tree and the individual "Source port:" and
"Destination port:" fields.
Does anyone else like the idea of displaying something like
"decimalport (hexport)" instead, or perhaps to make things simpler, it could
display "decimalport (decimalport/hexport)", so that even if the port names
are displayed, you'll still get both decimal & hex displayed?
No, I don't like that idea.
TCP/UDP ports are commonly represented as a decimal value in programs
and documentation. Adding a hex value will make things confusing IMHO.
As Micheal noted, you can get the hex value from the "Packet Bytes" if
you need it.
Regards, ULFL