Wireshark mailing list archives
Re: subprotocols
From: Charles Smith <cts.private.yahoo () gmail com>
Date: Wed, 15 Oct 2014 09:13:50 +0200
Thank you. On Tue, Oct 14, 2014 at 10:34 PM, Pascal Quantin <pascal.quantin () gmail com> wrote:
2014-10-14 22:15 GMT+02:00 Charles Smith <cts.private.yahoo () gmail com>:Is it built in, I just have to get the linkage right? Or do I have to fetch it from somewhere?Yes it's a built-in dissector. Please have a look at packet-catapult-dct2000.c for an example on how to call a sub dissector via call_dissector_only() function (it is easier than using the UDP framing protocol which is more suitable when calling Wireshark from an external program).On Tue, Oct 14, 2014 at 7:22 PM, Pascal Quantin <pascal.quantin () gmail comwrote:2014-10-14 17:33 GMT+02:00 Charles Smith <cts.private.yahoo () gmail com>:Hi. I have created a dissector for our tunnel protocol. I have the feeling that if I want to decode a payload protocol, say LTE MAC protocol, I'd use the proto() statement to hang that into my tree and some library code somewhere would do the rest of the decoding ... but I can't find these libraries (e.g. http://wiki.wireshark.org/MAC-LTE). Can someone set me straight? ctsHi Charles, LTE MAC dissector is a bit specific as it requires some meta data allowing it to know how to decaode the payload. You have 2 ways to configure it: - either look at epan/dissectors/packet-catapult-dct2000.c and check how it is configuring those meta data (mac_lte_info structure attached to each frame) - or use the UDP framing format as described in epan/dissectors/packet-mac-lte.h file. Some sample code demonstrating how to use it can be found here: http://wiki.wireshark.org/MAC-LTE Regards, Pascal. ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark orgArchives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org ?subject=unsubscribe___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org ?subject=unsubscribe___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org ?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org?subject=unsubscribe
Current thread:
- subprotocols Charles Smith (Oct 14)
- Re: subprotocols Pascal Quantin (Oct 14)
- Re: subprotocols Charles Smith (Oct 14)
- Re: subprotocols Pascal Quantin (Oct 14)
- Re: subprotocols Charles Smith (Oct 15)
- Re: subprotocols Charles Smith (Oct 15)
- Re: subprotocols Pascal Quantin (Oct 15)
- Re: subprotocols Charles Smith (Oct 15)
- Re: subprotocols Charles Smith (Oct 14)
- Re: subprotocols Pascal Quantin (Oct 14)