Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-users: Re: [Wireshark-users] Unable to see plugin in filters

From: Omer Khalid <Omer.Khalid@xxxxxxx>
Date: Tue, 8 Feb 2011 10:46:11 +0100
Hi Jaap,

Thanks for your reply. So when i launch wireshark from command line, there are no errors shown..

But under "About -> Plugins" box; no plugin is shown. I assume none of the plugins are loaded..

So I am wondering, is there an internal wireshark log which I could look at the figure out what's going or is there a way to loaded plugins manually one by one in the GUI?

Regards
Omer


On Mon, Feb 7, 2011 at 22:09, Jaap Keuter <jaap.keuter@xxxxxxxxx> wrote:
Hi,

Try to launch from the command line, in the build directory, using:

       ./wireshark

and see what appears at the console. Also check the About box, the plugins page to see if your plugin is listed there.

Thanks,
Jaap


On 02/07/2011 05:25 PM, Omer Khalid wrote:
Hi,

I have been trying to get my plugin working with Wireshark 1.4.3 on
Fedora 14 but with out luck.

Every thing compiles fine (after configuring the following files
[configure, configure.in <http://configure.in>, makefile.am
<http://makefile.am>, makefile.common, plugins/makefile.am
<http://makefile.am>] to point to the plugin/my_plugin_folder) but I

don't see the plugin in the filters.

Just to exclude the option that I may not be doing it the correct way; i
also compiled this test plugin
(http://www.codeproject.com/KB/IP/custom_dissector.aspx) and yet this is
not visible either...

I am wondering if I am missing any further steps after executing
autogen.sh, configure, make?

Regards,
Omer


___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
           mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe