Wireshark mailing list archives
Re: Standard defined field names in Wireshark dissectors
From: Guy Harris <guy () alum mit edu>
Date: Sun, 5 Jan 2020 10:16:21 -0800
On Jan 5, 2020, at 8:06 AM, Tomasz Moń <desowin () gmail com> wrote:
In case of the USB Audio descriptor dissection, I would like to change the header_field_info name, leaving abbrev as is. Would that still cause problems?
It would cause problems for programs that parse TShark -T text (default text) output (or "export the packet dissections as plain text" Wireshark output), but programs should avoid doing that if possible - they should use other -T formats, in which the abbrev is used. It shouldn't cause problem for any other software; filters, for example, use the abbrev. ("abbrev" should be thought of as the field name, and "name" should be thought of as the field *description*.) ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Standard defined field names in Wireshark dissectors Tomasz Moń (Jan 05)
- Re: Standard defined field names in Wireshark dissectors Graham Bloice (Jan 05)
- Re: Standard defined field names in Wireshark dissectors Tomasz Moń (Jan 05)
- Re: Standard defined field names in Wireshark dissectors Guy Harris (Jan 05)
- Re: Standard defined field names in Wireshark dissectors Dario Lombardo (Jan 05)
- Re: Standard defined field names in Wireshark dissectors Alexis La Goutte (Jan 05)
- Re: Standard defined field names in Wireshark dissectors Tomasz Moń (Jan 05)
- Re: Standard defined field names in Wireshark dissectors Graham Bloice (Jan 05)