Re: [Wireshark-dev] Questions about dev

2006-11-08 Thread Jaap Keuter
Hi, I'm all for that. I personally don't like extending Wireshark into the realm of trace file analyser. Thanx, Jaap On Wed, 8 Nov 2006, Kukosa, Tomas wrote: Hello, I use a little bit differen solution for a similar problem. Sometimes I need to dissect proprietray protocols from

Re: [Wireshark-dev] Release 00.99.4 missing file?

2006-11-08 Thread Graham Bloice
Ulf Lamping wrote: I let cygwin do its default thing, plus adding in the additional downloads required for the Wireshark documentation. Then I went back to an earlier version of Bash. I only installed cygwin to get Wireshark working so it should be standard. The file system is NTFS. Hi!

Re: [Wireshark-dev] Release 00.99.4 missing file?

2006-11-08 Thread Robert Trybis
Hello, Peter hit the nail on the head, it's the Windows PATH variable. The cygwin installation does not set an environment variable to allow python to be found. Also all the stuff that accumulates in the PATH environment variable can confuse things, though I don't think the length is important.

Re: [Wireshark-dev] Release 00.99.4 missing file?

2006-11-08 Thread Jaap Keuter
On Wed, 8 Nov 2006, Robert Trybis wrote: Hello, Peter hit the nail on the head, it's the Windows PATH variable. The cygwin installation does not set an environment variable to allow python to be found. Also all the stuff that accumulates in the PATH environment variable can confuse things,

Re: [Wireshark-dev] Release 00.99.4 missing file?

2006-11-08 Thread Robert Trybis
Can anybody tell me how to undo everything that has been done by Nmake -f Makefile.nmake all ? Go back to the beginning, like so nmake -f Makefile.nmake distclean then build again nmake -f Makefile.nmake all I did the clean as above then tried to build again it failed :-( The

[Wireshark-dev] Question about Wireshark´s repor ts

2006-11-08 Thread Andreina Toro
Hi everyone, I have a question, I´ve being told that wireshark has an option that shows the Quality of Sevice of each call, but not in the RTP Stream´s Window. I mean, somewhere in a protocol´s data or protocol´s header. My problem is that I´m doing my measures in a specific point of the trace

Re: [Wireshark-dev] Questions about dev

2006-11-08 Thread Joerg Mayer
On Wed, Nov 08, 2006 at 09:52:26AM +0100, Jaap Keuter wrote: I'm all for that. I personally don't like extending Wireshark into the realm of trace file analyser. Actually adding new file formats is quite ok, as long as there is some real use for it for more than just a handful of users. Also,

Re: [Wireshark-dev] Release 00.99.4 missing file?

2006-11-08 Thread Robert Trybis
I have tried again after deleting the wireshark directory and getting a clean copy of 00.99.4. Under XP the build ends prematurely with the lines given below. Any ideas why these files appear to be missing and how to work round it? I did not go through the process of doing the automated library

Re: [Wireshark-dev] [Patch] Fix for bug #1163: Dissector bug. ISO8073COTP protocol.

2006-11-08 Thread Graeme Lunt
Steve, This patch (r19733) breaks the dissection of X.400 and X.500 protocols, and probably other things besides. I think that the heuristic is incorrect. Oops, sorry about that. Do you know where I can get a copy of the standard so I can fix the heuristic in a better way? No problem.

Re: [Wireshark-dev] Release 00.99.4 missing file?

2006-11-08 Thread Ulf Lamping
Robert Trybis wrote: I have tried again after deleting the wireshark directory and getting a clean copy of 00.99.4. Under XP the build ends prematurely with the lines given below. Both files should be copied by epan\Makefile.nmake: mkstemp.c: ..\mkstemp.c xcopy ..\mkstemp.c . /d I

[Wireshark-dev] The builbot is deeply red seem to be caused by h248 changes

2006-11-08 Thread Ulf Lamping
Hi List! Someone may have a look? Regards, ULFL ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev

[Wireshark-dev] [PATCH] dccp: support for variable-length checksums

2006-11-08 Thread Gerrit Renker
This patch adds support for correct computation of variable length DCCP checksums as specified in RFC 4340, section 9. Previously wireshark was unable to compute these checksums, only full-coverage checksums could be validated. This patch * makes checksum computation dependent

Re: [Wireshark-dev] Release 00.99.4 missing file?

2006-11-08 Thread Lars Ruoff
is xcopy in the PATH? On the command line type xcopy. The PATH to add on WinXP might be C:\WINNT\system32\ instead of C:\Windows\system32\ Lars Robert Trybis wrote: I am in C:\Program Files\wireshark which is where I installed the sources using SVN and I am using the commands you mentioned;

Re: [Wireshark-dev] Release 00.99.4 missing file?

2006-11-08 Thread Bill Florac
I think you need to look further back into the nmake output. You should see this: -- cd .. ..\tools\lemon\lemon t=..\tools\lemon\lempar.c dtd_grammar.lemon flex -odtd_parse.c dtd_parse.l flex

Re: [Wireshark-dev] Release 00.99.4 missing file?

2006-11-08 Thread Jaap Keuter
Hi, It's only now that I see it Robert Trybis wrote: I am in C:\Program Files\wireshark which is where I installed the sources using SVN and I am using the commands you mentioned; You've actually put the sources where the installation is going to be? For one that is considered poor style

Re: [Wireshark-dev] Enabling threads

2006-11-08 Thread ronnie sahlberg
yes. we used to have 2 threads in the old ethereal for a short period. one thread for the main application and a second thread that was dedicated to only update/redraw teh statistics taps once every few seconds. this did cause a quite significant degradation in performance/speed of ethereal

Re: [Wireshark-dev] Enabling threads

2006-11-08 Thread LEGO
However I believe that what Gerald is talking about is using threads for asyncronously executing upgrades. I do not think that the very linking to the thread libraries causes performance degradation. If on a single processor you must continiuously switch contexts between the main thread and the

Re: [Wireshark-dev] Release 00.99.4 missing file?

2006-11-08 Thread Robert Trybis
Hi, I copied what seems to have been done in the binary distribution. Anyway just to check things I moved everything to C:\wireshark_source_00_99_4(no spaces in path) and tried another build, but I got exactly the same result with mkstemp.c strptime.c not being found. Regards RT

Re: [Wireshark-dev] Release 00.99.4 missing file?

2006-11-08 Thread Robert Trybis
Bill, Here is what I got in the build output; cd .. ..\tools\lemon\lemon t=..\tools\lemon\lempar.c dtd_grammar.lemon flex -odtd_parse.c dtd_parse.l flex -odtd_preparse.c dtd_preparse.l flex radius_dict.l xcopy ..\mkstemp.c . /d xcopy

Re: [Wireshark-dev] Release 00.99.4 missing file?

2006-11-08 Thread Bill Florac
The cd.. will make epan would working directory. So it copies the mkstemp.c and strptime.c files from the root directory to the epan directory. (Odd but it does not copy the header file) I confimed this by deleting the files in epan, and the script copied them again. So, by deduction, it seems

Re: [Wireshark-dev] Warnings in gtkvumeter.c

2006-11-08 Thread Ulf Lamping
Hmmm, I don't understand both. Joerg Mayer wrote: gtkvumeter.c:946: warning: comparison of unsigned expression 0 is always false CLAMP is called with three variables of type GtkVUMeterScaling gtkvumeter.c:1144: warning: comparison of unsigned expression 0 is always false CLAMP is

Re: [Wireshark-dev] Enabling threads

2006-11-08 Thread Gerald Combs
That's correct. Checking for updates would be pretty easy if we could connect to the server, issue a request, and feed the response to read_prefs_file(). It'd be even easier if we could do so from a thread instead of a separate process. In regard to Ulf's comment about threads not working

[Wireshark-dev] Core points to wtap_buf_ptr in wtap.c at line 556

2006-11-08 Thread Neha Chahal
Hi I am trying to test my code in the wiretap directory.When I run tethereal on my binary file it crashes randomly.The core points here-- Loaded symbols for /lib/libresolv.so.2#00x0038fbfd in

Re: [Wireshark-dev] Enabling threads

2006-11-08 Thread Ulf Lamping
Gerald Combs wrote: That's correct. Checking for updates would be pretty easy if we could connect to the server, issue a request, and feed the response to read_prefs_file(). It'd be even easier if we could do so from a thread instead of a separate process. And probably less memory

Re: [Wireshark-dev] Replace ntohl() with g_ntohl() - automated check?

2006-11-08 Thread Ulf Lamping
LEGO wrote: what about #defining them so they trigger an error? Although this would be a nice solution, I don't see a way to do this - it will conflict with the existing function declarations IMHO. I would be more than glad if we could do it that simple ... Regards, ULFL

Re: [Wireshark-dev] Warnings in gtkvumeter.c

2006-11-08 Thread Stephen Fisher
On Wed, Nov 08, 2006 at 11:07:15PM +0100, Ulf Lamping wrote: Joerg Mayer wrote: gtkvumeter.c:946: warning: comparison of unsigned expression 0 is always false CLAMP is called with three variables of type GtkVUMeterScaling gtkvumeter.c:1144: warning: comparison of unsigned expression

Re: [Wireshark-dev] Warnings in gtkvumeter.c

2006-11-08 Thread Stephen Fisher
On Wed, Nov 08, 2006 at 04:48:58PM -0800, Stephen Fisher wrote: One way that you can fix the warning is by manually assigning numbers to the enumerated values in gtkvumeter.h: A cleaner fix would be to just reverse the parameter order: CLAMP (scaling, GTK_VUMETER_SCALING_LINEAR,

Re: [Wireshark-dev] Warnings in gtkvumeter.c

2006-11-08 Thread Stephen Fisher
On Wed, Nov 08, 2006 at 04:59:56PM -0800, Stephen Fisher wrote: On Wed, Nov 08, 2006 at 04:48:58PM -0800, Stephen Fisher wrote: One way that you can fix the warning is by manually assigning numbers to the enumerated values in gtkvumeter.h: A cleaner fix would be to just reverse the

[Wireshark-dev] Questions about frame buffer

2006-11-08 Thread Neha Chahal
Hi I have a question about wth-frame_buffer. Does the plugin library (i.e the code that I am writing) have to initialize this buffer or is it done by wireshark internally. in what case will this buffer be empty. Currently my program is crashing becase the frame buffer is not initialized properly

Re: [Wireshark-dev] Questions about dev

2006-11-08 Thread Neha Chahal
I try this out as well. Thank you. On 11/7/06, Kukosa, Tomas [EMAIL PROTECTED] wrote: Hello,I use a little bit differen solution for a similar problem.Sometimes I need to dissect proprietray protocols from tracesfiles not supported by Wireshark.I use following way:1) convert trace file to pcap

[Wireshark-dev] Proposal for a Win32 update functionality - http://wiki.wireshark.org/Development/Update

2006-11-08 Thread Ulf Lamping
Hi List! I've added a proposal for an automatic update functionality to the Wiki. Please comment! Regards, ULFL ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev