Wireshark-dev: Re: [Wireshark-dev] packet parsing question
From: "Anders Broman" <[email protected]>
Date: Thu, 29 May 2008 21:31:33 +0200

How does your application get called from the network stack?

Wireshark works in a similar way so the answer depends on what your protocol

Ethernet ATM FR TCP UDP SCTP....





Från: [email protected]
[mailto:[email protected]] För Piety, Timothy [USA]
Skickat: den 29 maj 2008 20:32
Till: Developer support list for Wireshark
Ämne: Re: [Wireshark-dev] packet parsing question


Okay. I did a quick read through the README.developers doc and didn't see
anything that looked like it applied. I also took a look at the
README.design and a couple of other README docs. I have been looking through
code, but I am kind of stuck right now. I guess I was looking for an
overview of the flow. I thought that might help "unstick" me.


Am I missing something or is this all there is? I do not think I have a
"conversation" as described in the README.developer doc. What I have is a
packet that I know the protocol and simply want wireshark to dissect it. Is
it possible for me to have wireshark easily do this?





From: [email protected] on behalf of Luis EG Ontanon
Sent: Thu 5/29/2008 10:45 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] packet parsing question

You want to read doc/README.developer from the src tree.

On Thu, May 29, 2008 at 4:31 PM, Piety, Timothy [USA]
<[email protected]> wrote:
> Hi,
> I am trying to figure out how wireshark actually does teh dissection of a
> packet. I have a packet and I know the protocol, but do not have a parser
> for it. I would like to be able to give the packet to wireshark and have
> wireshark parse it then read the values back form the appropriate
> I have been looking a the code and do not see where wireshark a determines
> what the protocol is and which specific dissector to call. I have been
> to find out where it determines which file type the input file is. I
> have traced the code into a routine called call_dissector_through_handle
> packet.c. This appears to call the specific dissector through
> dissector_handle funtion pointer. I cannot find where the dissector_handle
> is set.
> Am I on the right track? Any guidance would be appreciated.
> thanks,
> Tim
> _______________________________________________
> Wireshark-dev mailing list
> [email protected]
> http://www.wireshark.org/mailman/listinfo/wireshark-dev

This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan
Wireshark-dev mailing list
[email protected]

<<attachment: winmail.dat>>