ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] Compiling Plugin error

From: Jeff Morriss <jeff.morriss.ws@xxxxxxxxx>
Date: Mon, 19 Nov 2012 09:18:50 -0500
Matteo Di Cosmo wrote:
Dear all,

I'm new in Wireshark and I'm trying to sniff IPMI packets throught a i2c bus.

To do this I need to compile a plugin which has been previously developed in the context of (https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1970 ) .

Actually, my first question is why do I need to add this plugin if wireshark already cames out with a ipmb dissector?

Well, I wouldn't think that you need to. The "new" (compared to that in bug 1970) IPMI dissector stuff is built-in (see epan/dissectors/packet-*ipmi*).

Why do you think you need to add the plugin?

Are you trying to capture IPMI packets or decode them? (I'm not aware of Wireshark/libpcap being able to capture from i2c buses but I could have missed that.)

Anyway, I tried to add this plugin following the README.plugin procedure and I faced the following problem.
I make the suggested modifications to the Makefile.am, Cmaketlist.txt etc.. files into the wireshark directory.

Then, from the wireshark derectory, I execute:

./autogen.sh
./configure
make

The compiling process correctly starts but after a while I get this error concerning the new plugin:

make[3]: Leaving directory `/home/userme/wireshark-1.8.3/plugins/gryphon' Making all in ipmb make[3]: Entering directory `/home/userme/wireshark-1.8.3/plugins/ipmb' make[3]: *** No rule to make target `all'. Stop. make[3]: Leaving directory `/home/userme/wireshark-1.8.3/plugins/ipmb' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/userme/wireshark-1.8.3/plugins' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/userme/wireshark-1.8.3' make: *** [all] Error 2

That suggests that there's no Makefile in plugins/ipmb/. Are you sure you added plugins/ipmb to the AC_OUTPUT() call in configure.in (or configure.ac if you were using trunk/)?