Wireshark mailing list archives
Re: Transport name resolution
From: Guy Harris <guy () alum mit edu>
Date: Mon, 16 Sep 2013 13:33:29 -0700
On Sep 16, 2013, at 1:15 PM, Dirk Jagdmann <doj () cubic org> wrote:
Should we, instead, look the port number up in the "tcp.port" or "udp.port" (or "sctp.port") dissector table and, if it finds a dissector handle, look up the short name of the protocol for that dissector handle and use that?I think this is more useful, since the dissector short name is typically used as the filter prefix. It is just confusing if slightly different strings are shown, because they come from some other list/database.
Actually, the dissector *filter* name is typically used as the filter prefix - for example, for DNS, there's: name - Domain Name Service short name - DNS filter name - dns Are you recommending using the filter name instead of the short name? ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Transport name resolution Anders Broman (Sep 16)
- Re: Transport name resolution Guy Harris (Sep 16)
- Re: Transport name resolution Jeff Morriss (Sep 16)
- Re: Transport name resolution Anders Broman (Sep 16)
- Re: Transport name resolution Guy Harris (Sep 16)
- Re: Transport name resolution Dirk Jagdmann (Sep 16)
- Re: Transport name resolution Bill Meier (Sep 16)
- Re: Transport name resolution Guy Harris (Sep 16)
- Re: Transport name resolution Dirk Jagdmann (Sep 16)
- Re: Transport name resolution Jeff Morriss (Sep 16)
- Re: Transport name resolution Jeff Morriss (Sep 16)
- Re: Transport name resolution Guy Harris (Sep 16)
- Re: Transport name resolution Jeff Morriss (Sep 17)
- Re: Transport name resolution Guy Harris (Sep 16)
- Re: Transport name resolution Jakub Zawadzki (Sep 16)