On Fri, Nov 25, 2011 at 12:28:19AM -0800, Guy Harris wrote:
> ...at least until a standard version of Wireshark is released with
> your changes (which requires that you give a patch to the Wireshark
> core developers, e.g. in a bug on bugs.wireshark.org).
We will typically accept a patch to add
I fear you can't register your dissector without changing packet-ipx.c.
>>>
>>> ...by adding a new dissector table and code to use it.
>> ... what requires that you distribute your self-built Wireshark with your
DLL.
>...at least until a standard version of Wireshark is released with your
ch
On Nov 25, 2011, at 12:20 AM, Helge Kruse wrote:
>
> Original-Nachricht
>> Datum: Thu, 24 Nov 2011 12:11:21 -0800
>> Von: Guy Harris
>> An: Developer support list for Wireshark
>> Betreff: Re: [Wireshark-dev] SPX protocol subdissector
>&
Original-Nachricht
> Datum: Thu, 24 Nov 2011 12:11:21 -0800
> Von: Guy Harris
> An: Developer support list for Wireshark
> Betreff: Re: [Wireshark-dev] SPX protocol subdissector
>
> On Nov 24, 2011, at 11:44 AM, Andreas wrote:
>
> > You can only
On Nov 24, 2011, at 11:44 AM, Andreas wrote:
> You can only use add your dissector for fields that are registered with
> register_dissector_table for this purpose.
...and they're not fields, they're just dissector tables; by *convention*,
dissector tables are often given the same name as field
Am 24.11.2011 19:41, schrieb Sergey Glebov:
I'm trying to make a dissector for the protocol, that works inside SPX.
So I register my protocol, register a dissector with dissect_XXX function,
etc - all pretty much like in samples.
Tricky thing is, that if I call, say, dissector_add("udp.port"
Hi everyone,
Sorry if writing to unappropriate place, please redirect me if necessary.
I'm trying to make a dissector for the protocol, that works inside SPX.
So I register my protocol, register a dissector with dissect_XXX function,
etc - all pretty much like in samples.
Tricky thing
