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

I have a dissector for a link-layer protocol for which I can dissect packets already. I need to implement conversations for my dissector for per-packet data, and would like to use find_or_create_conversation. I have already added my new address and port types to epan/address.h, epan/address_to_str.c and column-utils.c.

How do I set the source and destination information in the pinfo structure so that the correct conversation data is found?

Sometimes my protocol is simulated over UDP for testing, and I'd like to use the same dissection logic regardless if it's over the real hardware or UDP. How do I ensure that any other source/destination data is clobbered so that only my protocol's data is present?

asked 30 Aug '11, 07:22

multipleinterfaces's gravatar image

accept rate: 12%

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: 30 Aug '11, 07:22

question was seen: 3,425 times

last updated: 30 Aug '11, 07:22

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