Hi,
If you send a diff -u of the required changes to libwireshark.def as a patch it will be considered for
inclusion I think.
Regards
Anders
________________________________
Från: wireshark-dev-bounces@xxxxxxxxxxxxx genom yin sun
Skickat: to 2007-06-07 16:16
Till: Developer support list for Wireshark
Ämne: Re: [Wireshark-dev] how to make tcap subdissector in plugin
This is what I ended up doing. Copy paste TCAP and GSMMAP code into
plugin and add my private opcode handling. Why do I need private
opcode. Probably I don't understand how can I utilize this extension
container as mentioned below. In my case what I need is switch to a
new opcode such as 0xff, then dissect a bunch of private parameters.
Are then defined in 3GPP maybe or maybe not. I think the problem I had
is generic.
Someone wants to have something new for wireshark, and the new thing
is easier to deploy under plugin. But it needs to inherit
implementation from build-in dissector.
Thanks,
/Yin
On 6/6/07, Anders Broman <a.broman@xxxxxxxxx> wrote:
> Hi,
> I suppose this means you have to rebuild the complete MAP
> Dissector as a plugin adding your opcode(s) if the opcode isn't
> clashing with the existing ones perhaps it can be added to the existing MAP
> dissector.
>
> Why do you feel the you need to add private opcodes to MAP
> instead of using the existing ones adding extension containers for any
> private data needed or work with 3GPP to get the new opcodes you need
> added to MAP.
> Regards
> Anders
>
> -----Ursprungligt meddelande-----
> Från: wireshark-dev-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] För yin sun
> Skickat: den 5 juni 2007 21:13
> Till: Developer support list for Wireshark
> Ämne: Re: [Wireshark-dev] how to make tcap subdissector in plugin
>
> It is a private opcode to MAP.
>
> /Yin
>
> On 6/5/07, Anders Broman <a.broman@xxxxxxxxx> wrote:
> > Hi,
> > Is it a private opcode to MAP or something missing from MAP?
> > Regards
> > Anders
> >
> > -----Ursprungligt meddelande-----
> > Från: wireshark-dev-bounces@xxxxxxxxxxxxx
> > [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] För yin sun
> > Skickat: den 5 juni 2007 20:59
> > Till: Developer support list for Wireshark
> > Ämne: [Wireshark-dev] how to make tcap subdissector in plugin
> >
> > Hello developer,
> >
> > I have made the FooPage example working for plugin. Now I want to have
> > a plugin similar to GSM-MAP but as a plugin. Basically this plugin
> > will provide decoder for new opcode. The problem is, to register under
> > tcap I have to call add_itu_tcap_subdissector as I read from gsmmap
> > code. And this function is defined in dissectors.lib, which is not
> > visible to plugin. So the question is
> > 1. Can we in general make all the functions in dissectors accessible to
> > plugin.
> > 2. where should we draw a line between dissector and plugin.
> >
> > Thanks,
> > /Yin
> > _______________________________________________
> > Wireshark-dev mailing list
> > Wireshark-dev@xxxxxxxxxxxxx
> > http://www.wireshark.org/mailman/listinfo/wireshark-dev
> >
> > _______________________________________________
> > Wireshark-dev mailing list
> > Wireshark-dev@xxxxxxxxxxxxx
> > http://www.wireshark.org/mailman/listinfo/wireshark-dev
> >
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev
<<winmail.dat>>