Re: [Wireshark-dev] Determine address type of string

Hello Chris, I really like this idea but IIRC not the complete API is exposed to plugins and so str_to_ip and str_to_ip6 are not available in a standard installation for plugins (they are not included in the libwireshark.def file which I do not have on my windows development machine anyway but

Re: [Wireshark-dev] Dissect using val_to_str from external file

Hello Bill, thank you for your quick answer. I am developing a plugin. Am I on my windows development machine limited to the Wireshark API exposed to plugins (aka libwireshark.def)? Can I somewhere request that ipproto_val_ext is exported for plugins? Bye, Jo 2015-11-09 17:59 GMT+01:00 Bill

Re: [Wireshark-dev] Dissect using val_to_str from external file

On 11 November 2015 at 10:11, Jo wrote: > Hello Bill, > > thank you for your quick answer. > > I am developing a plugin. Am I on my windows development machine > limited to the Wireshark API exposed to plugins (aka > libwireshark.def)? > > Can I somewhere request that

Re: [Wireshark-dev] Dissect using val_to_str from external file

Hi Jo, The better is push a patch on code review for add ipproto_val_ext on libwireshark.def Regards, On Wed, Nov 11, 2015 at 11:11 AM, Jo wrote: > Hello Bill, > > thank you for your quick answer. > > I am developing a plugin. Am I on my windows development machine >

Re: [Wireshark-dev] Dissect using val_to_str from external file

Hello Graham, Thank you. Is this set of exported symbols meant to be extended on user request? Or what is the correct way to gain access to symbols that are not yet marked for export? Bye, jo 2015-11-11 11:25 GMT+01:00 Graham Bloice : > See ws_symbol_export.h for

Re: [Wireshark-dev] Dissect using val_to_str from external file

Hello, I did this now for the functions in my other question (http://seclists.org/wireshark/2015/Nov/78) but I have no idea how to get this working for val_to_str() in my plugin file. In my source file, i include and Visual Studio does only complain at compile time about unresolved external

[Wireshark-dev] GCC GTK3 Wireshark build warnings ?

When building GTK3 Wireshark on my Fedora system (after not having done so for a while), I'm getting many warnings similar to the following: CC libgtkui_a-about_dlg.o In file included from /usr/include/gtk-3.0/gtk/gtk.h:263:0, from about_dlg.c:28:

Re: [Wireshark-dev] GTP session plugin

On 11/11/15 07:36, POZUELO Gloria (BCS/PSD) wrote: Hi, I’ve almost finished the plugin I’m working on, but now I’m trying to improve the performance. I’d like to ask you if there’s a way to know if wireshark has dissected all packets of the pcap file, this way I could avoid to calculate all the

Re: [Wireshark-dev] GCC GTK3 Wireshark build warnings ?

On 11/11/15 12:28, Bill Meier wrote: When building GTK3 Wireshark on my Fedora system (after not having done so for a while), I'm getting many warnings similar to the following: CC libgtkui_a-about_dlg.o In file included from /usr/include/gtk-3.0/gtk/gtk.h:263:0, from

Re: [Wireshark-dev] GCC GTK3 Wireshark build warnings ?

2015-11-11 22:10 GMT+04:00 Jeff Morriss : > On 11/11/15 12:28, Bill Meier wrote: >> >> When building GTK3 Wireshark on my Fedora system (after not having done >> so for a while), I'm getting many warnings similar to the following: >> >> >> CC

Re: [Wireshark-dev] GCC GTK3 Wireshark build warnings ?

On 11-11-2015 17:28, Bill Meier wrote: When building GTK3 Wireshark on my Fedora system (after not having done so for a while), I'm getting many warnings similar to the following: CC libgtkui_a-about_dlg.o In file included from /usr/include/gtk-3.0/gtk/gtk.h:263:0,

Re: [Wireshark-dev] GCC GTK3 Wireshark build warnings ?

On Nov 11, 2015, at 10:10 AM, Jeff Morriss wrote: > On 11/11/15 12:28, Bill Meier wrote: > >> So: it seems we want to continue to support GTK3 ? > > Yes, I think so. At least RHEL 6 needs to continue to use the Gtk+ GUI > (since its Qt isn't new enough). (Though

Re: [Wireshark-dev] Dissect using val_to_str from external file

On 11 November 2015 at 10:33, Jo wrote: > Hello Graham, > > Thank you. > > Is this set of exported symbols meant to be extended on user request? > Or what is the correct way to gain access to symbols that are not yet > marked for export? > > If you can manage with local

Re: [Wireshark-dev] GTP session plugin

Hi, I’ve almost finished the plugin I’m working on, but now I’m trying to improve the performance. I’d like to ask you if there’s a way to know if wireshark has dissected all packets of the pcap file, this way I could avoid to calculate all the necessary things for getting the GTP session

Re: [Wireshark-dev] Dissect using val_to_str from external file

Hi, If I remember correctly there is a problem to use data between .dlls on Windows. You can copy the value string to your plugin I suppose. Regards Anders -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Jo Sent: den

Re: [Wireshark-dev] GTP session plugin

2015-11-11 13:36 GMT+01:00 POZUELO Gloria (BCS/PSD) : > Hi, > > > > I’ve almost finished the plugin I’m working on, but now I’m trying to > improve the performance. I’d like to ask you if there’s a way to know if > wireshark has dissected all packets of the pcap file,

Re: [Wireshark-dev] Dissect using val_to_str from external file

On 11 November 2015 at 13:38, Jo wrote: > Hello, > > I did this now for the functions in my other question > (http://seclists.org/wireshark/2015/Nov/78) but I have no idea how to > get this working for val_to_str() in my plugin file. > > In my source file, i include and

Re: [Wireshark-dev] GCC GTK3 Wireshark build warnings ?

On 11/11/2015 9:57 PM, Bill Meier wrote: On 11/11/2015 1:24 PM, Bálint Réczey wrote: It looks like Balint already sent a patch to Gtk: https://www.wireshark.org/lists/wireshark-dev/201403/msg00042.html It seems to be a new breakage, I have to check it. Yep: from the gtk 3.18 repository:

Re: [Wireshark-dev] GCC GTK3 Wireshark build warnings ?

On 11/11/2015 1:24 PM, Bálint Réczey wrote: It looks like Balint already sent a patch to Gtk: https://www.wireshark.org/lists/wireshark-dev/201403/msg00042.html It seems to be a new breakage, I have to check it. Yep: from the gtk 3.18 repository: gtkstyle.h commit 2015-05-14 Amend

[Wireshark-dev] Wireshark 2.0.0rc3 is now available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm proud to announce the release of Wireshark 2.0.0rc3. This is the third release candidate for Wireshark 2.0. __ What is Wireshark? Wireshark is the world's most popular

Re: [Wireshark-dev] GCC GTK3 Wireshark build warnings ?

On 11/11/15 13:22, Guy Harris wrote: On Nov 11, 2015, at 10:10 AM, Jeff Morriss wrote: On 11/11/15 12:28, Bill Meier wrote: So: it seems we want to continue to support GTK3 ? Yes, I think so. At least RHEL 6 needs to continue to use the Gtk+ GUI (since its Qt