Your dissector won't appear under "Preferences -> Protocols" if it doesn't have 
any preferences.  Does it?

Does it appear under "Analyze -> Enabled Protocols"?
- Chris

From: wireshark-dev-boun...@wireshark.org 
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Koglin, Patrick
Sent: Tuesday, April 06, 2010 10:02 AM
To: wireshark-dev@wireshark.org
Subject: [Wireshark-dev] Build my own "foo" dissector example, Plugin/Protocol 
not visible


Hey,

I make my first steps with wireshark and a own dissector. For testing I send 
only UDP packages with integers on network and I can see the traffic and 
content in wireshark as "UDP" Protocol.

Now I want to test my own "foo" protocol dissector. Also I followed the 
examples in readme.plugins/readme.developers and the documentation on 
wireshark.org. State of my dissector is final. I can generate it with "make" 
without errors and I can build wireshark with "make". Its only the standard 
implementation, buts thats ok - the implementation follow in nex step.

My current problem is, I cant see the plugin/protocol in wireshark. I looked at 
wireshark preferences (=> protocols), or I looked ad context menue "decode as". 
Nowhere any "myfoo" protocol. The other protocols like ehtercat, gryphon, asn1, 
couldn´t found, too.

Where can I find my protcol/the other plugins? They perhabs aren´t within my 
build?

I develop on current Ubuntu version with wireshark 1.2.6.

Thanks.
Patrick Koglin

--
CONFIDENTIALITY NOTICE: The contents of this email are confidential
and for the exclusive use of the intended recipient. If you receive this
email in error, please delete it from your system immediately and 
notify us either by email, telephone or fax. You should not copy,
forward, or otherwise disclose the content of the email.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Reply via email to