Re: [Wireshark-dev] question about RTP Streams - [ SPAM - Bayesian] Bayesian Filter detected spam

2006-09-07 Thread Miha Jemec
looking at the packets you could see a delay of 100ms, which is long but acceptablewhere in the RTP Streams window you look at the delay? The only parameters I see are: * Src IP addr,Src port,Dest IP addr,Dest port,SSRC,Payload,Packets,Lost,Max Delta (ms),Max Jitter

Re: [Wireshark-dev] query regarding gtp_handlefuntionanddecoderfunction.

2006-09-07 Thread prashanth joshi
Hi Anders, thanks. But, as u know i've been trying to write a deceder function So it goes something like this: My_decoder_fun(..) { proto_tree *my_tree; proto_item *te; te = proto_tree_add_text(tree, tvb, offset, 1, val_to_str(MY_EXT_VAL, gtp_val, "Unknown message"));

Re: [Wireshark-dev] Portability issue of capture files.

2006-09-07 Thread Guy Harris
LEGO wrote: I just tried to open some files with my intel based minimac and they do not work... Where were the capture files created, and what application wrote them? oddly enough capture works only if you are seeing packets in real-time, if instead you try to capture without it fails to

Re: [Wireshark-dev] A plugin dissector and fragmented messages

2006-09-07 Thread Still Life
Check out doc/README.developer chapter 2.7 Reassembly/desegmentation for protocols running atop TCP. Thanx, Jaap Thank you Jaap! I resolved my problem with the second method exposed in chapter 2.7. Now things seems to work. Cheers -- Email.it, the professional e-mail, gratis per te:

Re: [Wireshark-dev] tcp_dissect_pdus

2006-09-07 Thread Guy Harris
John R. wrote: I have an issue with desegmentation of packets: if the minimal header required to judge length is broken across TCP segments A and B, at segment A it decides properly to return expecting the remainder of the minimal header. In my problem case, the next tcp segment to arrive has

Re: [Wireshark-dev] query regarding gtp_handlefuntionanddecoderfunction.

2006-09-07 Thread ronnie sahlberg
you MUST use a hf_ field as the second parameter. you can NOT use NULL since 1, NULL is not an integer and is therefore the WRONG type for the second parameter and would anyway give you a compiler error if you tried. 2, there are plenty of examples on how to use hf_fields in the code. please

Re: [Wireshark-dev] display filter on a field that appears more than once in a message

2006-09-07 Thread Andrew Schweitzer
Guy Harris wrote: ronnie sahlberg wrote: The difference is the difference between the upside down A (==For ALL it is true) and the mirrored E (==there EXISTS at least one) I.e.: payload.packet.a_field != 1 means there exists at least one instance of payload.packet.a_field in

Re: [Wireshark-dev] Portability issue of capture files.

2006-09-07 Thread LEGO
Found! there's libz.1.2.3 in both /usr/lib and /opt/local/lib as soon as I removed that in /opt/local/lib I solved the issue... diferent library same mis-bahaviour as I used to have with open-ssl Solved by [pociccio:~/src/trunk] lego% sudo mv /opt/local/lib/libz.1.2.3.dylib

[Wireshark-dev] Win32 build error return code 0x66666666

2006-09-07 Thread VOCAL Technologies, LTD
Thank you Tim, I reinstalled Cygwin tools, and I was able to compile, but am now unable to link. I checked my path to make sure I am using the MSVC linker, and I get this error: ftype-ipv4.c(108) : error C2065: 'fvalue_t_free_list' : undeclared identifier I am working on tracking this bug down,

Re: [Wireshark-dev] Portability issue of capture files.

2006-09-07 Thread Andreas Fink
Oh thats interesting. I think my wireshark was built with the source of libz as well but really what whould have been needed was a export LDFLAGS -lz for most of the tools. I'm rebuilding it currently on a new MacPro. Will report if that fixes it too. On 07.09.2006, at 13:57, LEGO wrote:

Re: [Wireshark-dev] Win32 build error return code 0x66666666

2006-09-07 Thread Cook, Timothy
What are you using as source (e.g. SVN tip or source distribution 0.99.3)? I usually build from SVN tip. However, I haven't applied updates for couple months. Maybe I'll have time to update do a clean build. -Tim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL

[Wireshark-dev] Win32 build error return code 0x66666666

2006-09-07 Thread VOCAL Technologies, LTD
I am building from the source distrobution 0.99.3 ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev

[Wireshark-dev] Http dissector - Am I missing something?

2006-09-07 Thread Bryant Eastham
All- I have done several plugin dissectors in the past for internal protocols, all TCP- and UDP-based. I am now trying to add a plugin for a protocol that uses HTTP as the transport. Easy, I thought! Well, not so easy it appears. I am confused by the logic in packet-http.c around line 1059:

Re: [Wireshark-dev] tcp_dissect_pdus

2006-09-07 Thread John R. Hogerhuis
On Thu, 2006-09-07 at 03:22 -0700, Guy Harris wrote: John R. wrote: I have an issue with desegmentation of packets: if the minimal header required to judge length is broken across TCP segments A and B, at segment A it decides properly to return expecting the remainder of the minimal

Re: [Wireshark-dev] Http dissector - Am I missing something?

2006-09-07 Thread LEGO
XML's dissector is called as an heuristic dissector for http, can't you do like it does? Luis On 9/7/06, Bryant Eastham [EMAIL PROTECTED] wrote: All- I have done several plugin dissectors in the past for internal protocols, all TCP- and UDP-based. I am now trying to add a plugin for a

Re: [Wireshark-dev] [Patch] epan/make-sminmpec.pl

2006-09-07 Thread LEGO
Committed revision 19172. I modified so that calling it like make-sminmpec.pl -gen is like calling it make-sminmpec.pl -gen \ http://www.iana.org/assignments/enterprise-numbers \ sminmpec.c Luis On 9/7/06, Andrew Feren [EMAIL PROTECTED] wrote: This adds some features to

Re: [Wireshark-dev] [Patch] epan/make-sminmpec.pl

2006-09-07 Thread Andrew Feren
--- LEGO [EMAIL PROTECTED] wrote: Committed revision 19172. I modified so that calling it like make-sminmpec.pl -gen is like calling it make-sminmpec.pl -gen \ http://www.iana.org/assignments/enterprise-numbers \ sminmpec.c If you try using this default I doubt

Re: [Wireshark-dev] win32: nmake setup: can't find cl

2006-09-07 Thread Cook, Timothy
Have you done the following: Do you intend to build using MSVC CYGWIN tools? Was your Win32 build environment setup using the Developers Guide, sections 2.3 4.6.2? If you intended to use MSVC CYGWIN tools, a command prompt [DOS prompt] is the way to go! Also ensure that you have run

[Wireshark-dev] win32: nmake setup: can't find cl

2006-09-07 Thread Jacques, Olivier \(OpenCall Test Infra\)
Hello, I re-installed my PC and I'm trying to re-setup my wireshark build environment. After a fresh svn checkout, a nmake -f makefile.nmake distclean, I can't run nmake -f makefile.nmake setup: win32setup.sh complains about cl that can't be found: --

Re: [Wireshark-dev] Win32 build error return code 0x66666666

2006-09-07 Thread Cook, Timothy
I just did build based on source distribution 0.99.3 (retrieved today)! I did find that the file \wireshark\airpcap.h is missing from the distribution and causes the build to fail. Before starting the first build, did you execute: nmake -fmakefile.nmake distclean and nmake -fmakefile.nmake

Re: [Wireshark-dev] Portability issue of capture files.

2006-09-07 Thread Guy Harris
LEGO wrote: there's libz.1.2.3 in both /usr/lib and /opt/local/lib Gak. Any idea what package installed its own private libz? It probably shouldn't be doing that, unless it needs 1.2.3 or later and can't work with earlier versions. as soon as I removed that in /opt/local/lib I solved the

Re: [Wireshark-dev] Portability issue of capture files.

2006-09-07 Thread LEGO
On 9/7/06, Guy Harris [EMAIL PROTECTED] wrote: Gak. Any idea what package installed its own private libz? It probably shouldn't be doing that, unless it needs 1.2.3 or later and can't work with earlier versions. Darwinports does use its own dependencies for a *lot* of things even if

Re: [Wireshark-dev] tcp_dissect_pdus

2006-09-07 Thread John R.
OK, so I'm digging into desegment_tcp. What I find is that when segment B comes it looks for the most recent prior PDU which it calls msp. It calculates an offset and length for the last snippet of Segment A. The length is 4, which is the length of data at the end of Segment A. It uses this info

Re: [Wireshark-dev] Further HTTP woes...

2006-09-07 Thread Bryant Eastham
Thank you! My intent was really not to add more work to others, but to investigate how to solve the problem on my own. I appreciate your offer. Since that solution is "real", I will not spend any time on my "conversation" hack. Thanks again, Bryant From: [EMAIL PROTECTED] [mailto:[EMAIL

Re: [Wireshark-dev] Further HTTP woes...

2006-09-07 Thread ronnie sahlberg
Check the WishList on the wiki Analysis item 5.It has been planned for quite a while but there has not yet been any real or urgent need for this.Ill try to implement this sometimes this weekend.The solution I implement will require that you have reassembly enabled. On 9/8/06, Bryant Eastham [EMAIL

Re: [Wireshark-dev] tcp_dissect_pdus

2006-09-07 Thread ronnie sahlberg
Are you using the latest SVN ?I fixed a bug in pdu tracking/reassembly about ~2 weeks agoOn 9/8/06, John R. [EMAIL PROTECTED] wrote:OK, so I'm digging into desegment_tcp.What I find is that when segment B comes it looks for the most recent prior PDU which it calls msp. It calculates an offset and

[Wireshark-dev] Problem with docbook build process

2006-09-07 Thread Joerg Mayer
Hello, for some reasons not really clear to me, the build process for the documentation tries to download some files from the docbook repository: 34.327847 192.168.0.3 - 217.237.150.115 DNS Standard query A docbook.sourceforge.net 34.391786 217.237.150.115 - 192.168.0.3 DNS Standard query

[Wireshark-dev] ESP Patch for Hexadecimal keys

2006-09-07 Thread Frédéric Roudaut
Hi, as requested here is a patch in order to take into account Encryption and Authentication keys for ESP in hexa. You only have to write your key with 0x first. In this case if the key is not in 8-bit unit, it will be considered as starting with a 0 (4 bits). Excepted this case, the key