Re: [Wireshark-dev] Problem during compilation

I am compiling on windows XP n 32 bit. On Mon, Apr 26, 2010 at 3:37 AM, Stephen Fisher wrote: > On Fri, Apr 23, 2010 at 02:42:35PM +0530, ankur madan wrote: > > > packet-ieee802154.c(982) : warning C4244: '=' : conversion from > > 'guint64' to 'gu int32', possible loss of data > > I see that you'

Re: [Wireshark-dev] Problem during compilation

I have latest version code from the svn and latest development wireshark version.1.3.4 installed.i am still not able to resolve this issue.any help or comments are welcome thanks ankur On Mon, Apr 26, 2010 at 12:51 PM, ankur madan wrote: > I am compiling on windows XP n 32 bit. > > > On Mon, Ap

Re: [Wireshark-dev] Problem during compilation

On 26/04/2010 10:10, ankur madan wrote: > I have latest version code from the svn and latest development > wireshark version.1.3.4 installed.i am still not able to resolve this > issue.any help or comments are welcome > > thanks > ankur > > On Mon, Apr 26, 2010 at 12:51 PM, ankur madan

Re: [Wireshark-dev] Problem during compilation

On 26/04/2010 10:35, Graham Bloice wrote: > On 26/04/2010 10:10, ankur madan wrote: >> I have latest version code from the svn and latest development >> wireshark version.1.3.4 installed.i am still not able to resolve this >> issue.any help or comments are welcome >> >> thanks >> ankur >> >> On M

Re: [Wireshark-dev] Problem during compilation

Hi, the error which i was getting in packet-ieee802154.c has been resolved using the patch given.Now i am getting following linking error: Creating library libwireshark.lib and object libwireshark.exp GeoIP.lib(GeoIP.obj) : fatal error LNK1103: debugging information corrupt; recom pile modul

Re: [Wireshark-dev] Problem during compilation

On 26/04/2010 11:36, ankur madan wrote: > Hi, >the error which i was getting in packet-ieee802154.c has been > resolved using the patch given.Now i am getting following linking error: > >Creating library libwireshark.lib and object libwireshark.exp > GeoIP.lib(GeoIP.obj) : fatal error LNK

Re: [Wireshark-dev] Pidl patch for ABSOLUTE_TIMEs

My apologies Jeff. I mistakenly thought the dissector was maintained by wireshark.org not samba.org, and I didn't notice that it was only CC'd here. I just saw the [Wireshark-dev] in the subject line. BTW, it looks like samba.org does have their own bug tracker: https://bugzilla.samba.org/.

[Wireshark-dev] About Wiretap Library

Hi there, I'm doing my Final Project (University of Málaga, Spain) and need to use the Wiretap Library. I have been looking for some manual or documentation about the library for a week but no success. I have read the Developers Give too, but it doesn't explain to much. After all, I decided to jo

Re: [Wireshark-dev] About Wiretap Library

On Mon, Apr 26, 2010 at 08:49:36PM +0200, p2m p2m wrote: > I'm doing my Final Project (University of Málaga, Spain) and need to > use the Wiretap Library. I have been looking for some manual or > documentation about the library for a week but no success. I have read > the Developers Give too, b

Re: [Wireshark-dev] RFC: sorted value_string + bsearch

On Fri, Apr 23, 2010 at 11:32:16PM +0200, Anders Broman wrote: > like a full table starting at a number ( like 500 - 1000 ->value match index > minus > offset). Uhm, sounds complicated :) Maybe we can initialize match_type in proto_register_field_init() so developer don't need to care if it's

Re: [Wireshark-dev] Problem during compilation

Graham Bloice wrote: > On 26/04/2010 10:35, Graham Bloice wrote: >> On 26/04/2010 10:10, ankur madan wrote: >>> I have latest version code from the svn and latest development >>> wireshark version.1.3.4 installed.i am still not able to resolve this >>> issue.any help or comments are welcome >>>

Re: [Wireshark-dev] [Wireshark-bugs] [Bug 2748] M3UA dissector should mark "MTP3 equivalents" as generated.

wouldn't it be better if we hid the MTP3 equivalent entries? As it is now, the same information gets printed 2 or 3 times. Regards, Gerasimos > https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2748 > > Jeff Morriss changed: > >What|Removed |Added > ---

Re: [Wireshark-dev] About Wiretap Library

2010/4/26 Stephen Fisher > On Mon, Apr 26, 2010 at 08:49:36PM +0200, p2m p2m wrote: > > > I'm doing my Final Project (University of Málaga, Spain) and need to > > use the Wiretap Library. I have been looking for some manual or > > documentation about the library for a week but no success. I have

Re: [Wireshark-dev] [Wireshark-commits] rev 32561: /trunk/plugins/opcua/ /trunk/plugins/opcua/: opcua_enumparser.c opcua_hfindeces.c opcua_simpletypes.c

morr...@wireshark.org wrote: > http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=32561 > > User: morriss > Date: 2010/04/25 05:15 PM > > Log: > Make the OpcUa plugin's fields filterable (by giving them abbreviations). > (Thank you, sed, for doing the 90% of the work for me.) >

[Wireshark-dev] Code Collaborator from SmartBear Software

I recently came across a lightweight peer code review tool called Code Collaborator from SmartBear Software. See http://smartbear.com/codecollab.php. While the product seems like it would be very beneficial, the cost of the tool will almost certainly prohibit its use here at my company. Howeve

Re: [Wireshark-dev] About Wiretap Library

On Apr 26, 2010, at 1:24 PM, p2m p2m wrote: > I need to capture iSCSI packets (using tshark) and then open the capture > files and get the data I need using a dissector to analise it. Wireshark's capture files are in pcap format, so libpcap/WinPcap can also be used to read the raw packet data.

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-XP-x86

The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/100 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason:

Re: [Wireshark-dev] Code Collaborator from SmartBear Software

On Apr 26, 2010, at 2:28 PM, Maynard, Chris wrote: > I recently came across a lightweight peer code review tool called Code > Collaborator from SmartBear Software. Seehttp://smartbear.com/codecollab.php. > Platform: Windows, Mac OS X, Linux, Solaris, BSD Well, that, at least, is good news. T

[Wireshark-dev] Dissecting a Protocol with multiple static TCP ports

Hi, I am trying to write a dissector for a proprietary protocol. This protocol can use 4 static TCP ports. Thanks to the Wireshark tutorial I have gotten the dissector to work, but only with one static TCP port. I have tried: dissector_add("tcp.port", 21016, myproto_handle); dissector_add("t

Re: [Wireshark-dev] Dissecting a Protocol with multiple static TCP ports

Craig Bumpstead wrote: > Hi, > > I am trying to write a dissector for a proprietary protocol. This protocol > can use 4 static TCP ports. > Thanks to the Wireshark tutorial I have gotten the dissector to work, but > only with one static TCP port. > > I have tried: > dissector_add("tcp.port", 2

Re: [Wireshark-dev] Dissecting a Protocol with multiple static TCP ports

Bill, Thanks for the quick response. That setting is off. The first and second packets are TCP port 4435 and 21016 which it decodes. However from that point on it doesn't decode packets with TCP port 4435. I loath posting my code, but obviously I am making a mistake somewhere. #ifdef HAVE_CONFI

Re: [Wireshark-dev] Dissecting a Protocol with multiple static TCP ports

Craig Bumpstead wrote: > Bill, > > Thanks for the quick response. That setting is off. > The first and second packets are TCP port 4435 and 21016 which it decodes. > However from that point on it doesn't decode packets with > TCP port 4435. > > I loath posting my code, but obviously I am making

Re: [Wireshark-dev] Help Me To Solve The Problem

My version of Wireshark is wireshark-0.99.5. And more about my development is as follow: Version 0.99.5-lipps123 Copyright 1998-2007 Gerald Combs and contributors. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS

Re: [Wireshark-dev] Dissecting a Protocol with multiple static TCP ports

Bill, The packets that are not decoded are decoded as TCP packets. So I don't understand why it only decodes the first one. I must be making a mistake in the code. Regards, Craig - Original Message From: Bill Meier To: Developer support list for Wireshark Sent: Tue, 27 April, 201

Re: [Wireshark-dev] Help Me To Solve The Problem

Hi, Thanks a lot. I will check the source file about wireshark. But I still don't understand that I build *the same source tree* without my plug-in and it couldn' work. And more about the development of my version is as follows: Version 0.99.5-lipps123 Copyright 1998-2007 Gerald Com

Re: [Wireshark-dev] Dissecting a Protocol with multiple static TCP ports

Craig, You probably need to take a look at tcp_dissect_pdus(). If you're lucky, it'll help you reassemble your TCP stream; if not, you might need to write your own TCP reassembly routines. There are many dissectors that make use of it for reassembly and it's documented in section 2.7.1 of REA

Re: [Wireshark-dev] Code Collaborator from SmartBear Software

Hi, I quickly read through the website to get a feel for the product and the process it tries to support. From what I see it's very nice tool to do a CMM level 2 development, even distinuted geographically. Still I don't think it solves a real problem in Wireshark development. We're not loo

Re: [Wireshark-dev] Help Me To Solve The Problem

Maybe you can try to use your debugger and place a breakpoint at an appropriate place in capture_info.c to try to figure out exactly why it's failing? BTW, is there any particular reason why you're using 0.99.5 and Visual C++ 7.10? You might try using VS2008EE as your compiler, as that's the on

Re: [Wireshark-dev] Problem during compilation

So,is there any other solution for this problem.due to some reason i have 2 work on VS 2005 only.looking forward for a response. On Tue, Apr 27, 2010 at 1:32 AM, Jeff Morriss wrote: > Graham Bloice wrote: > > On 26/04/2010 10:35, Graham Bloice wrote: > >> On 26/04/2010 10:10, ankur madan wrote: >

Re: [Wireshark-dev] Dissecting a Protocol with multiple static TCP ports

Chris, So your saying to reassemble the packet then run the dissector again? Is there a way that I can just specify the TCP Port range with just 2 port numbers? Regards, Craig - Original Message From: "Maynard, Chris" To: Developer support list for Wireshark Sent: Tue, 27 April, 20

Re: [Wireshark-dev] RFC: sorted value_string + bsearch

Hi, I like it! Can you provide an example use of the new value_string_ext as well? Regards Anders Jakub Zawadzki skrev 2010-04-26 21:13: On Fri, Apr 23, 2010 at 11:32:16PM +0200, Anders Broman wrote: like a full table starting at a number ( like 500 - 1000 ->value match index minus offset

Re: [Wireshark-dev] RFC: sorted value_string + bsearch

On Tue, Apr 27, 2010 at 08:15:35AM +0200, Anders Broman wrote: > Can you provide an example use of the new value_string_ext as well? Attaching sample patch for dns. Can you do some benchmarks? :) diff --git epan/dissectors/packet-dns.c epan/dissectors/packet-dns.c index 960231e..a814612 100644 ---