Re: [Wireshark-dev] Modify default settings?

2010-11-14 Thread Alexander Koeppe
Stephen Fisher schrieb: Are we using the best default settings when Wireshark is installed for the first time on a machine? I always make these changes: - uncheck Ask for unsaved capture files - check Welcome screen and title bar shows version - Always start in directory (Desktop on

[Wireshark-dev] Filter for generated items

2010-11-14 Thread Helge Kruse
Hi I write a dissector DLL, that adds a generated item to the tree. After defining the hf_info with type FT_STRING, i use proto_item_append_text to show the generated string. But this item cannot be used neither to search or to filter for this item. I have seen, that the packet-frame.c uses

[Wireshark-dev] regarding sgsap procotol

2010-11-14 Thread Rajesh Alluri
Hello All, Does any one know when SGSAP protocol will be added in wireshark? (in which version of Wireshark) I checked in the latest Wireshark but couldnt able to find. please let me know if any have information? Best regards, Rajesh,

Re: [Wireshark-dev] Filter for generated items

2010-11-14 Thread wsgd
Look at : - proto_tree_add_item - proto_tree_add_string - proto_tree_add_string_format Olivier Le 14/11/2010 13:34, Helge Kruse a écrit : Hi I write a dissector DLL, that adds a generated item to the tree. After defining the hf_info with type FT_STRING, i use proto_item_append_text to show

Re: [Wireshark-dev] regarding sgsap procotol

2010-11-14 Thread Stephen Fisher
On Sun, Nov 14, 2010 at 08:44:19PM +0530, Rajesh Alluri wrote: Does any one know when SGSAP protocol will be added in wireshark? (in which version of Wireshark) I checked in the latest Wireshark but couldnt able to find. please let me know if any have information? There is no way of telling

[Wireshark-dev] Filter for generated items

2010-11-14 Thread Helge Kruse
Hi I write a dissector DLL, that adds a generated item to the tree. After defining the hf_info with type FT_STRING, i use proto_item_append_text to show the generated string. But this item cannot be used neither to search or to filter for this item. I have seen, that the packet-frame.c uses

Re: [Wireshark-dev] [Wireshark-commits] rev 34856: /trunk/gtk/ /trunk/gtk/: CMakeLists.txt Makefile.am Makefile.common file_import_dlg.c file_import_dlg.h menus.c text_import.c text_import.h text_impo

2010-11-14 Thread Joerg Mayer
On Fri, Nov 12, 2010 at 10:20:15PM +, j...@wireshark.org wrote: http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=34856 Add text import capability, like text2pcap, directly into the GUI. Is this completley new code or does it share the analysis of the input file with

Re: [Wireshark-dev] Filter for generated items

2010-11-14 Thread Guy Harris
On Nov 14, 2010, at 4:31 AM, Helge Kruse wrote: Hi I write a dissector DLL, that adds a generated item to the tree. After defining the hf_info with type FT_STRING, i use proto_item_append_text to show the generated string. But this item cannot be used neither to search or to filter for

Re: [Wireshark-dev] Filter for generated items

2010-11-14 Thread Helge Kruse
Original-Nachricht Datum: Sun, 14 Nov 2010 16:53:38 +0100 Von: wsgd w...@free.fr An: Developer support list for Wireshark wireshark-dev@wireshark.org Betreff: Re: [Wireshark-dev] Filter for generated items Look at : - proto_tree_add_item - proto_tree_add_string -

[Wireshark-dev] Strange desegmentation code in packet-ssl?

2010-11-14 Thread Kaul
Any idea why isn't the SSL dissector using the straightforward desgementation facilities available by Wireshark? It is left over from ancient times? It seems like a complex piece of work, instead of nicely using the PDUs dissection infrastructure - and I believe that SSL is a classic protocol for

Re: [Wireshark-dev] [Wireshark-commits] rev 34860: /trunk/gtk/ /trunk/gtk/: text_import.c

2010-11-14 Thread Pascal Quantin
Hi 2010/11/13 Jaap Keuter jaap.keu...@xs4all.nl Hi, That seems to be the result of the flex version being used. What platform are you using? We'll probably need to take a step back and rework using older mechanisms. I'm facing the same issue with my Debian Lenny. Updating my flex version