This is our old Q&A Site. Please post any new questions and answers at

We have a custom hardware device that uses the IEEE 802.15.4 transport mechanism. To capture these data in WireShark, we are making use this project

When the data is captured, data transmission packets appear as protocol LwMesh and acknowledgment packets appear as protocol IEEE 802.15.4.

We want to create a custom dissector, to be applied to all of our packets, to more readily understand the traffic. Based on my reading (and I am brand new to this), it is not clear to me if I should create a regular dissector or a heuristic dissector. In either case, I do not understand why the new dissector would be given preference over the existing one (or, similarly, how to apply a specific dissector to multiple packets).

Would you please point me int he direction of an answer. Thank you.

asked 09 Oct, 20:17

groston's gravatar image

accept rate: 0%

Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 09 Oct, 20:17

question was seen: 79 times

last updated: 09 Oct, 20:17

p​o​w​e​r​e​d by O​S​Q​A