Wireshark-dev: Re: [Wireshark-dev] Regarding Plugin attachment
From: Anders Broman <[email protected]>
Date: Tue, 18 Mar 2014 11:40:59 +0000

Hi,

Does the file packet-foo.h exist in epan/dissectors?

 

From: [email protected] [mailto:[email protected]] On Behalf Of Nilesh Nayak
Sent: den 18 mars 2014 12:03
To: Hadriel Kaplan; [email protected]; Peter Wu
Subject: Re: [Wireshark-dev] Regarding Plugin attachment

 

I have the following error while compiling each time my dissector using 'make' command.

make[5]: Entering directory `/home/nileshnayak/Desktop/wireshark-1.10.5/epan/dissectors'
make[5]: *** No rule to make target `packet-foo.h', needed by `all-am'.  Stop.
make[5]: Leaving directory `/home/nileshnayak/Desktop/wireshark-1.10.5/epan/dissectors'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home/nileshnayak/Desktop/wireshark-1.10.5/epan/dissectors'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/nileshnayak/Desktop/wireshark-1.10.5/epan/dissectors'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/nileshnayak/Desktop/wireshark-1.10.5/epan'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/nileshnayak/Desktop/wireshark-1.10.5'
make: *** [all] Error 2



Couldn't really figure out what the problem is actually..

Any help is greatly appreciated.

Thanks and Regards,

Nilesh Nayak

 

On Tue, Mar 18, 2014 at 3:57 PM, Nilesh Nayak <[email protected]> wrote:

I have the following error while compiling each time my dissector using 'make' command.

Couldn't really figure out what the problem is actually..

Any help is greatly appreciated.

Thanks and Regards,

Nilesh Nayak

 

On Wed, Mar 12, 2014 at 11:34 AM, Hadriel Kaplan <[email protected]> wrote:


So why do a plugin?  Just write a normal new dissector.

Regardless, the doc to read is this: doc/README.dissector

That explains a lot, in detail; and of course you should also look at some existing packet-* files in epan/dissectors.  For UDP, packet-stun.c or packet-ntp.c are a relatively small ones.

-hadriel



On Mar 12, 2014, at 1:48 AM, Nilesh Nayak <[email protected]> wrote:

> So, basically I want to build a basic wireshark dissector and try to capture the packets using my own customised protocol name.
> Example : I have a protocol of my own, lets name it as "foo" protocol. Now, I want to create a dissector for it like packet-<protocolname>.c and  packet-<protocolname>.h as source header files.
>
> Underlying the protocol, I am capturing UDP packets. But if I set the capture filter as "foo", then I should be able to capture "foo" packets.
> Could you please send me some good tutorials over the same?
>
> I have already read the README.developer and README.pluggins docs.
>
>
> And yes, I am adding a new protocol dissector in the wireshark source code itself and then building the environment and compiling.
>
> Thanks and Regards,
> Nilesh
>

> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <[email protected]>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>             mailto:[email protected]?subject=unsubscribe