[Wireshark-dev] What is Wireshark 1.6.0 ?

2011-08-11 Thread news.gmane.com
In the developer guide section 3.3.4 (http://www.wireshark.org/docs/wsdg_html_chunked/ChSrcObtain.html) you can read: The officially released source files can be found at: http://www.wireshark.org/download/. You should use these sources if you want to build Wireshark on your platform for

Re: [Wireshark-dev] Compiling Wireshark for Win32

2011-08-11 Thread Stig Bjørlykke
On Wed, Aug 10, 2011 at 6:18 PM, news.gmane.com andreassand...@gmx.net wrote: I am a bit surprised about a problem with compiling Wireshark 1.6.0 with Visual Studio 2005 for Win32. Why do you build 1.6.0 when we have released 1.6.1? The issues you have are fixed in 1.6.1. -- Stig Bjørlykke

Re: [Wireshark-dev] Compiling Wireshark for Win32

2011-08-11 Thread news.gmane.com
Guy Harris g...@alum.mit.edu wrote in message news:0ced7f2d-8d53-40bd-bfc0-f86b7559c...@alum.mit.edu... On Aug 10, 2011, at 9:18 AM, news.gmane.com wrote: I am a bit surprised about a problem with compiling Wireshark 1.6.0 with Visual Studio 2005 for Win32. Some dissectors have assignments

Re: [Wireshark-dev] Compiling Wireshark for Win32

2011-08-11 Thread news.gmane.com
Stig Bjørlykke s...@bjorlykke.org wrote in message news:canoxo1qnrsjqq39xqeyw+w3vnib0oxv5bjcbz0h15cjkubn...@mail.gmail.com... I am a bit surprised about a problem with compiling Wireshark 1.6.0 with Visual Studio 2005 for Win32. Why do you build 1.6.0 when we have released 1.6.1? The issues

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-7-x64

2011-08-11 Thread buildbot-no-reply
The Buildbot has detected a new failure on builder Windows-7-x64 while building Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/2672 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build:

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.6-x64

2011-08-11 Thread buildbot-no-reply
The Buildbot has detected a new failure on builder OSX-10.6-x64 while building Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.6-x64/builds/3553 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build:

Re: [Wireshark-dev] Rev 38350 Capture Options Changes - Named Pipe?

2011-08-11 Thread Michael Tüxen
On Aug 10, 2011, at 10:55 PM, Guy Harris wrote: On Aug 10, 2011, at 1:49 PM, Michael Tüxen wrote: I was aware of this in the context of the -i arguments, but not that it could be specified in the GUI. We need to find a way to do this. Maybe an button which will add a named pipe to the

Re: [Wireshark-dev] Rev 38350 Capture Options Changes - Named Pipe?

2011-08-11 Thread Michael Tüxen
On Aug 10, 2011, at 11:16 PM, Jakub Zawadzki wrote: On Wed, Aug 10, 2011 at 10:49:47PM +0200, Michael Tüxen wrote: I was aware of this in the context of the -i arguments, but not that it could be specified in the GUI. We need to find a way to do this. Maybe an button which will add a named

Re: [Wireshark-dev] Rev 38350 Capture Options Changes - Named Pipe?

2011-08-11 Thread Michael Tüxen
On Aug 10, 2011, at 11:49 PM, Joerg Mayer wrote: On Wed, Aug 10, 2011 at 11:16:55PM +0200, Jakub Zawadzki wrote: On Wed, Aug 10, 2011 at 10:49:47PM +0200, Michael Tüxen wrote: I was aware of this in the context of the -i arguments, but not that it could be specified in the GUI. We need to

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-x86

2011-08-11 Thread buildbot-no-reply
The Buildbot has detected a new failure on builder OSX-10.5-x86 while building Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-x86/builds/4038 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build:

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-PowerPC

2011-08-11 Thread buildbot-no-reply
The Buildbot has detected a new failure on builder OSX-10.5-PowerPC while building Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-PowerPC/builds/3445 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build:

[Wireshark-dev] buildbot failure in Wireshark (development) on Ubuntu-10.04-x64

2011-08-11 Thread buildbot-no-reply
The Buildbot has detected a new failure on builder Ubuntu-10.04-x64 while building Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Ubuntu-10.04-x64/builds/2057 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build:

Re: [Wireshark-dev] Compiling Wireshark for Win32

2011-08-11 Thread Alex Lindberg
If you are interested in debugging in a windows environment you can add the compile flags in config.nmake on the LOCAL_CFLAGS variable.:    /FR to create .sbr files    /Zi to create .pdb files After you build wireshark, you can also do nmake -f Makfile.nmake wireshark.bsc to create the

Re: [Wireshark-dev] Rev 38350 Capture Options Changes - Named Pipe?

2011-08-11 Thread Joerg Mayer
On Thu, Aug 11, 2011 at 12:43:26PM +0200, Michael T?xen wrote: When building with remote capture, then there is a button below the Interface list. Maybe the remote capture stuff, the interface stuff and the pipe stuff can be unified by having a drop down button with which to select what

Re: [Wireshark-dev] capture_dlg.c: several unused_but_set warnings [GCC 4.6]

2011-08-11 Thread Michael Tüxen
On Aug 10, 2011, at 11:26 PM, Bill Meier wrote: capture_dlg.c: In function ‘insert_new_rows’: capture_dlg.c:665:18: warning: variable ‘cap_settings’ set but not used [-Wunused-but-set-variable] capture_dlg.c:664:8: warning: variable ‘linktype_select’ set but not used

Re: [Wireshark-dev] Rev 38350 Capture Options Changes - Named Pipe?

2011-08-11 Thread Michael Tüxen
On Aug 11, 2011, at 3:00 PM, Joerg Mayer wrote: On Thu, Aug 11, 2011 at 12:43:26PM +0200, Michael T?xen wrote: When building with remote capture, then there is a button below the Interface list. Maybe the remote capture stuff, the interface stuff and the pipe stuff can be unified by having

Re: [Wireshark-dev] Compiling Wireshark for Win32

2011-08-11 Thread news.gmane.com
Alex, thanks for reply. You're right, these compile flags cause the compiler to generate the file. If you would read my mail, you would see, that build always fails. So your after you build wireshark assumption doesn't meet. Thanks for suggesting nmake -f Makefile.bsc I am not sure

[Wireshark-dev] Network data mining

2011-08-11 Thread David Corrales
Hi everyone, I'm studying the possibility of writing a Wireshark plugin to do network data mining for a thesis work. It would basically go through the filtered packets and analyze them using a given set of methods. This way I get to use the functionality of filtering and sorting already

Re: [Wireshark-dev] What is Wireshark 1.6.0 ?

2011-08-11 Thread Gerald Combs
On 8/11/11 12:24 AM, news.gmane.com wrote: Why don't I get the same files, when I checkout the SVN repository? svn export http://anonsvn.wireshark.org/wireshark/releases/wireshark-1.6.0 wireshark compared to http://www.wireshark.org/download/src/wireshark-1.6.0.tar.bz2 If you take a

Re: [Wireshark-dev] Compiling Wireshark for Win32

2011-08-11 Thread Gerald Combs
On 8/11/11 2:28 AM, news.gmane.com wrote: Since there are no PDB files for 1.6.0 Is there something wrong with the wireshark-pdb-...zip files at http://www.wireshark.org/download/win32/all-versions/ and http://www.wireshark.org/download/win64/all-versions/ ?

Re: [Wireshark-dev] Compiling Wireshark for Win32

2011-08-11 Thread Alex Lindberg
The correct command is     nmake -f Makefile.nmake wireshark.bsc --- On Thu, 8/11/11, news.gmane.com andreassand...@gmx.net wrote: From: news.gmane.com andreassand...@gmx.net Subject: Re: [Wireshark-dev] Compiling Wireshark for Win32 To: wireshark-dev@wireshark.org Date: Thursday, August 11,

Re: [Wireshark-dev] Compiling Wireshark for Win32

2011-08-11 Thread Graham Bloice
On 11/08/2011 17:06, Alex Lindberg wrote: The correct command is nmake -f Makefile.nmake wireshark.bsc --- On *Thu, 8/11/11, news.gmane.com /andreassand...@gmx.net/* wrote: From: news.gmane.com andreassand...@gmx.net Subject: Re: [Wireshark-dev] Compiling Wireshark for Win32

Re: [Wireshark-dev] Network data mining

2011-08-11 Thread Jaap Keuter
Hi, There are two README's of interest to you: README.plugin README.developer And the other plugin directories of course. Thanks, Jaap Send from my iPhone On 11 aug. 2011, at 06:36, David Corrales corrales.da...@gmail.com wrote: Hi everyone, I'm studying the possibility of writing a

Re: [Wireshark-dev] [Wireshark-commits] rev 38476: /trunk/epan/dissectors/ /trunk/epan/dissectors/: packet-dcerpc-frsrpc.c packet-dcerpc-frsrpc.h

2011-08-11 Thread Guy Harris
On Aug 11, 2011, at 1:17 AM, sahlb...@wireshark.org wrote: http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=38476 User: sahlberg Date: 2011/08/11 01:17 AM Log: Regenerate a new updated FRSRPC dissector. This dissectors now dissects a whole lot more of the FRS protocol.

[Wireshark-dev] Feature Request - Comments attached to a packet

2011-08-11 Thread Alex Lindberg
Has anyone looked into creating the ability to attach comments to a capture file or to a specific packet? It would make sharing decode efforts easier. Any input would be welcome. Alex Lindberg ___ Sent via:

Re: [Wireshark-dev] Feature Request - Comments attached to a packet

2011-08-11 Thread Tyson Key
Hi Alex, Whilst no-one's looking into implementing support for attaching comments to packets (as far as I'm aware); someone recently wrote a patch to enable reading comments from pcap-ng/NTAR files, and attached it to bug #6229. Tyson. On 11 August 2011 19:04, Alex Lindberg alind...@yahoo.com

Re: [Wireshark-dev] Feature Request - Comments attached to a packet

2011-08-11 Thread Tyson Key
Right. Feel free to disregard my previous e-mail, then. :) Sorry for the inconvenience/false hope, Tyson. On 11 August 2011 19:24, Guy Harris g...@alum.mit.edu wrote: On Aug 11, 2011, at 11:16 AM, Tyson Key wrote: Whilst no-one's looking into implementing support for attaching comments

Re: [Wireshark-dev] Feature Request - Comments attached to a packet

2011-08-11 Thread Guy Harris
On Aug 11, 2011, at 11:16 AM, Tyson Key wrote: Whilst no-one's looking into implementing support for attaching comments to packets (as far as I'm aware); someone recently wrote a patch to enable reading comments from pcap-ng/NTAR files, and attached it to bug #6229. Actually, that bug

Re: [Wireshark-dev] [Wireshark-commits] rev 38350: /trunk/ /trunk/gtk/: capture_dlg.c capture_dlg.h capture_if_dlg.c capture_if_dlg.h main_welcome.c main_welcome.h menus.c menus.h /trunk/: capture.c c

2011-08-11 Thread Stephen Fisher
On Fri, Aug 05, 2011 at 11:05:55PM +0200, Michael Tuexen wrote: * Multiple IP addresses should be separated with comma in the Edit Interfaces Settings window, I think. Need to see how this haves with a lot of addresses. GTK has a function for truncating labels: gtk_label_set_ellipsize()

Re: [Wireshark-dev] [Wireshark-commits] rev 38350: /trunk/ /trunk/gtk/: capture_dlg.c capture_dlg.h capture_if_dlg.c capture_if_dlg.h main_welcome.c main_welcome.h menus.c menus.h /trunk/: capture.c c

2011-08-11 Thread Michael Tüxen
On Aug 11, 2011, at 10:02 PM, Stephen Fisher wrote: On Fri, Aug 05, 2011 at 11:05:55PM +0200, Michael Tuexen wrote: * Multiple IP addresses should be separated with comma in the Edit Interfaces Settings window, I think. Need to see how this haves with a lot of addresses. GTK has a

Re: [Wireshark-dev] Compiling Wireshark for Win32

2011-08-11 Thread Jeff Morriss
news.gmane.com wrote: Stig Bjørlykke s...@bjorlykke.org wrote in message news:canoxo1qnrsjqq39xqeyw+w3vnib0oxv5bjcbz0h15cjkubn...@mail.gmail.com... I am a bit surprised about a problem with compiling Wireshark 1.6.0 with Visual Studio 2005 for Win32. Why do you build 1.6.0 when we have

Re: [Wireshark-dev] reassembly again

2011-08-11 Thread Martin Kaiser
It looks like reassembly is not your favourite topic ;-) Never mind, I'll keep talking to myself, feel free to join in... Thus wrote Martin Kaiser (li...@kaiser.cx): I now think I know what happens, I'd appreciate your opinion how to deal with it properly: a tdpu looks like header | body

Re: [Wireshark-dev] [Wireshark-commits] rev 38490: /trunk/gtk/ /trunk/gtk/: io_stat.c

2011-08-11 Thread Joerg Mayer
On Thu, Aug 11, 2011 at 08:49:08PM +, etx...@wireshark.org wrote: http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=38490 User: etxrab Date: 2011/08/11 01:49 PM Log: Remove remaining GDK deprecated functons. (Use cairo_surface_t). Directory: /trunk/gtk/ Changes

Re: [Wireshark-dev] [Wireshark-commits] rev 38490: /trunk/gtk/ /trunk/gtk/: io_stat.c

2011-08-11 Thread Joerg Mayer
On Fri, Aug 12, 2011 at 01:12:16AM +0200, Joerg Mayer wrote: Why do you do this? #if CHECK_VERSION(2,22,0) cairo_surface_t *surface; #else GdkPixmap *pixmap; GdkPixmap *pixmap; #endif OK, I think I found the answer: gdk_window_create_similar_surface is a 2.22 function. Ciao

Re: [Wireshark-dev] [Wireshark-commits] rev 38477: /trunk/gtk/ /trunk/gtk/: tcp_graph.c

2011-08-11 Thread Joerg Mayer
On Thu, Aug 11, 2011 at 09:00:04AM +, etx...@wireshark.org wrote: http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=38477 Use Cairo in more places. The #if 0 code in draw_element_arc() currently crashes and the arc coordinates should be fixed to work with Cairo, any help

Re: [Wireshark-dev] Rev 38350 Capture Options Changes - Named Pipe?

2011-08-11 Thread Guy Harris
On Aug 11, 2011, at 6:00 AM, Joerg Mayer wrote: While everyone seems to be adding their wishes, now that someone is actually is working on that code: Would it make sense to add a button (or whatever) to scan for newly created/activated interfaces? When I'm running Wireshark and add a new

Re: [Wireshark-dev] Rev 38350 Capture Options Changes - Named Pipe?

2011-08-11 Thread Michael Tüxen
On Aug 12, 2011, at 4:41 AM, Guy Harris wrote: On Aug 11, 2011, at 6:00 AM, Joerg Mayer wrote: While everyone seems to be adding their wishes, now that someone is actually is working on that code: Would it make sense to add a button (or whatever) to scan for newly created/activated