Re: custom dissector

[Beth <beth.tridium () gmail com>]

Can you make the port# a preference, and fill it in at runtime once you
know what it is?


On Fri, Apr 27, 2012 at 12:26 PM, Chad Milam <cdubbm () gmail com> wrote:

> I've written two relatively simple dissectors and gotten them to work
> under some basic conditions. However, the protocols can use random ports
> (not inside of a single conversation, but generally speaking).  Also, the
> protocols are not easily identified by any marker inside of the protocol,
> making heuristics not terribly ideal.  Both of them are based on UDP.
>
> Is there a way I can get the protocol dissector plugin to show up in the
> decode as menu, and not have them do any real work until it is selected? I
> do not see them in the menu today.
>
> Or is there another way to achieve what is that I am looking to do?
>
> Thanks
___________________________________________________________________________
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-request () wireshark org?subject=unsubscribe