Hi,
I'm writing my first protocol dissector (a plugin).
I have the basics up and running. However,
this protocol has a couple of unique issues:
1 Although encapsulated in UDP, it doesn't use a
well-known port. I'm OK with telling wireshark
to decode using the protocol specifically (right-
Hi,
I've got a plugin dissector working for the top-level header of a
multi-layer protocol, and I need to add the subdissectors for the
subsequent layers.
I've tried doing this as separate plugins, and in a single plugin
with multiple registered dissectors. However, whenever I
call add_dissector
Guy Harris wrote:
> Bob Doolittle wrote:
>
>
>> Looking at packet.c, it appears that the type of the HF name
>> I'm passing as the first arg doesn't map to an acceptable type,
>> but in fact I've declared that field with type FT_UINT8,
>> which
Guy Harris wrote:
> On Apr 3, 2007, at 4:53 PM, Bob Doolittle wrote:
>
>
>> Thanks. My subdissector is now being called, and is updating the List
>> window
>> properly. But for some odd reason the sub-protocol isn't appearing
>> in the
>> Details
Guy Harris wrote:
> What's the code in the subdissector that adds the top-level entry for
> the protocol?
Sorry - I just realized you asked for the subdissector code, and I sent
the dissector code for the top-level protocol. At least you can check that
I'm calling dissector_try_port properly...
Guy Harris wrote:
> Bob Doolittle wrote:
>
>
>> alp_dgram_tree = proto_item_add_subtree(ti, ett_alp_dgram);
>>
>
> ett_alp_dgram - and ett_alp_commonr - aren't -1, right?
Right. They were both initialized in the proto_register_* routines
by call
Hi,
Can wireshark handle env-variable control of the
location of the plugins directory (similar to
LD_LIBRARY_PATH etc)?
I haven't found it, and desperately need it. I
work in an environment where I commonly use
several platforms, including Solaris sparc and x86
as well as various Linux distros.
Jeff Morriss wrote:
> Bob Doolittle wrote:
>
>> Hi,
>>
>> Can wireshark handle env-variable control of the
>> location of the plugins directory (similar to
>> LD_LIBRARY_PATH etc)?
>>
>> I haven't found it, and desperately need it. I
>
Richard van der Hoff wrote:
> Bob Doolittle wrote:
>
>> What about preferences, do they get stored in $WIRESHARK_HOME
>> as well? That would be unfortunate - it would be undesirable to
>> maintain multiple copies...
>>
>
> Yes. You could symlink all the
