Wireshark mailing list archives
Re: Enabling protocol in Decode As dialog
From: Guy Harris <guy () alum mit edu>
Date: Thu, 9 Jun 2016 00:54:18 -0700
On Jun 8, 2016, at 11:10 PM, Robert Cragie <robert.cragie () gridmerge com> wrote:
It's basically an 802.15.4 MAC frame plus an additional byte at the beginning placed into the payload of a UDP datagram.
So the answer to my question is "it runs atop UDP". So: if there's a standard UDP port number atop which it runs, you should...
The only thing the CoAP dissector does in addition is to add a port using dissector_add_uint()
...register it in the "udp.port" dissector with that port number; if there *is* no standard UDP port number atop which it runs, you should register it in the "udp.port" dissector with a call to dissector_add_for_decode_as(). ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Enabling protocol in Decode As dialog Robert Cragie (Jun 08)
- Re: Enabling protocol in Decode As dialog Guy Harris (Jun 08)
- Re: Enabling protocol in Decode As dialog Robert Cragie (Jun 08)
- Re: Enabling protocol in Decode As dialog Guy Harris (Jun 09)
- Re: Enabling protocol in Decode As dialog Robert Cragie (Jun 10)
- Re: Enabling protocol in Decode As dialog Guy Harris (Jun 10)
- Re: Enabling protocol in Decode As dialog Robert Cragie (Jun 10)
- Re: Enabling protocol in Decode As dialog Guy Harris (Jun 10)
- Re: Enabling protocol in Decode As dialog Robert Cragie (Jun 12)
- Re: Enabling protocol in Decode As dialog Robert Cragie (Jun 08)
- Re: Enabling protocol in Decode As dialog Guy Harris (Jun 08)