Re: [Wireshark-dev] Bug 491 : time delta behaviour

2007-03-20 Thread Jeff Morriss
Sake Blok wrote: On Mon, Mar 19, 2007 at 10:45:42AM +0800, Jeff Morriss wrote: I did however start to look into the code to see how I could implement the extra field. I realise that I need to start to understand how wireshark actually handles frames. Some fields are filled by the dissector

Re: [Wireshark-dev] Query on status of patches

2007-03-20 Thread Jeff Morriss
Joerg Mayer wrote: On Wed, Mar 14, 2007 at 09:58:26AM +0100, Sake Blok wrote: I have not seen many patches being overlooked actually. There were the occasions where a review lasted a little longer, but most patches were commited within a couple of days. Maybe a patch-tracking system is a

Re: [Wireshark-dev] Getting destination IP

2007-03-20 Thread Jeff Morriss
Hi, [Please don't send Excel docs to the mailing list--especially if they contain a picture. Not everyone has high speed Internet connections and not everyone can read Excel docs.] sara vanan wrote: [...] /home/saravanan/ethereal-0.99.0/tethereal -c 10 port 53 Capturing on eth0 [...] it

Re: [Wireshark-dev] Getting destination IP

2007-03-20 Thread sara vanan
Ok, Here after I will not send any attachments to the wireshark developer list. Sorry for attaching the excel sheet. On 3/20/07, Jeff Morriss [EMAIL PROTECTED] wrote: Hi, [Please don't send Excel docs to the mailing list--especially if they contain a picture. Not everyone has high speed

[Wireshark-dev] Getting destination IP

2007-03-20 Thread sara vanan
Hi, I am doing a DNS proxy for IPV6. For this I have to get the destination IP(DNS Sever IP stored in the client PC. I am trying to use Wireshark source code for getting the desdtination IP. for example client IP - 192.168.16.67DNS ( destination IP) - 192.168.16.106 By using the

Re: [Wireshark-dev] Prevent compiler warnings by using stop on warnings/treat warnings as errors compiler option?

2007-03-20 Thread Ulf Lamping
Jeff Morriss wrote: In fact I meant it just as a stop-gap until someone (smarter--or at least with more than to dedicate to the purpose--than me) can fix Wireshark's unsigned-vs-signed char problem. As it is, I have to scroll through hundreds of (probably not fixable by me) warnings just

Re: [Wireshark-dev] Getting destination IP

2007-03-20 Thread Andrej Mikus
Is your question somehow related to development of Wireshark? I am afraid you are not asking at the best place. Purpose of Wireshark is to analyze packets. The command mentioned below gives brief display of the data. If you do not need all that info, consider using other commands to process it

Re: [Wireshark-dev] Prevent compiler warnings by using stop on warnings/treat warnings as errors compiler option?

2007-03-20 Thread Richard van der Hoff
Ulf Lamping wrote: I just meant that in the long run just ignoring a long list of warnings is probably not a good idea ... However, disabling the signed warning, fix the rest and setting the stop on error barrier would still be a lot better than what we currently have ... I heartily

Re: [Wireshark-dev] Prevent compiler warnings by using stop on warnings/treat warnings as errors compiler option?

2007-03-20 Thread Martin Mathieson
Currently, you don't tend to even notice new warnings that you introduce on your own platform, as they get lost in the general compilation noise. Part of the problem (when working from the command-line at least) is how much output is generated, and how far you'd need to scroll back to see the

Re: [Wireshark-dev] Prevent compiler warnings by using stop on warnings/treat warnings as errors compiler option?

2007-03-20 Thread Mark H. Wood
Getting rid of warnings should not be confused with getting rid of the *reasons* for those warnings. -- Mark H. Wood, Lead System Programmer [EMAIL PROTECTED] Typically when a software vendor says that a product is intuitive he means the exact opposite. pgpomulJckxPF.pgp Description: PGP

Re: [Wireshark-dev] Prevent compiler warnings by using stop on warnings/treat warnings as errors compiler option?

2007-03-20 Thread Luis Ontanon
Inline comments... On 3/20/07, Martin Mathieson [EMAIL PROTECTED] wrote: Currently, you don't tend to even notice new warnings that you introduce on your own platform, as they get lost in the general compilation noise. Part of the problem (when working from the command-line at least) is

[Wireshark-dev] [PATCH] analyzing SHIM6 protocol

2007-03-20 Thread Matthijs Mekking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, The last two months I have been working on a SHIM6 enabled version of Wireshark. The subject of my final thesis is about SHIM6 and I needed to analyze the SHIM6 communication exchange. SHIM6 is an IPv6 based solution for

Re: [Wireshark-dev] [PATCH] analyzing SHIM6 protocol

2007-03-20 Thread Sebastien Tandel
I think most the proto_tree_add_text could be replaced by proto_tree_add_item which could allow (i.e. at least Sébastien Barré ;)) to perform an easy search on specific items. ;) Regards, Sebastien Tandel Matthijs Mekking wrote: Hello, The last two months I have been working on a SHIM6

[Wireshark-dev] idl2eth

2007-03-20 Thread Zivcec, Kristijan
Hi, Does anyone have idl2eth version for windows? I am stuck with linux version that is usable but only on linux. Does anyone have some other solution??? I need to create plugin for wireshark, to monitor my CORBA traffic... Thanks in advance, Kristijan

[Wireshark-dev] Compilation errors

2007-03-20 Thread taraniteja.vishwanatha
Hi , I have written a dissector, compiled and tested it( no problems). But the same dissector when used by somebody else at a different location is giving compilation problems. They are using the same OS (RHEL 4) and the same compiler version as ours. It is giving the following error:

Re: [Wireshark-dev] Prevent compiler warnings by using stop on warnings/treat warnings as errors compiler option?

2007-03-20 Thread Stephen Fisher
On Tue, Mar 20, 2007 at 03:04:49AM +0100, Ulf Lamping wrote: In my experience having a compiler warning free code is a good way to prevent very subtle bugs and would also be a good addition to the programs security - and BTW more pleasant to work with ;-) Indeed. So here comes the

Re: [Wireshark-dev] Prevent compiler warnings by using stop on warnings/treat warnings as errors compiler option?

2007-03-20 Thread Stephen Fisher
On Tue, Mar 20, 2007 at 01:01:20PM -0700, Stephen Fisher wrote: As usual, this is my Win32 point of view. I'm pretty sure the above is possible to do for the Win32 platform. I'm not sure if it's possible with the automake foo for the different unix/linux platform builds ... With

Re: [Wireshark-dev] Prevent compiler warnings by using stop on warnings/treat warnings as errors compiler option?

2007-03-20 Thread Stephen Fisher
On Tue, Mar 20, 2007 at 12:44:06PM +, Martin Mathieson wrote: Part of the problem (when working from the command-line at least) is how much output is generated, and how far you'd need to scroll back to see the compilation of the file you've just changed. Yup. I edit source files and

Re: [Wireshark-dev] Bug 491 : time delta behaviour

2007-03-20 Thread Sake Blok
On Tue, Mar 20, 2007 at 05:47:59PM +0800, Jeff Morriss wrote: Sake Blok wrote: I assigned the bug to myself, I hope that is the proper way to use bugzilla (as this is my first time to write code to solve an already listed bug). I don't know if there is a proper way but I will mention

Re: [Wireshark-dev] Bug 491 : time delta behaviour

2007-03-20 Thread Sake Blok
On Wed, Mar 14, 2007 at 10:24:10AM +0100, Sake Blok wrote: OK, I think an extra field needs to be added to the frame-dissector so that both delta's are available, also for filtering, searching and coloring. It would also be nice to be able to have both fields available for the columns in the

Re: [Wireshark-dev] Fun with Cisco DLT-value usage

2007-03-20 Thread Andrej Mikus
I believe the issue could be reported to Cisco TAC requesting correction, instead of hacking heuristics. At the other hand, did they announce somewhere that they are using libpcap format? I was googling a bit and found indications how to convert the file

Re: [Wireshark-dev] Prevent compiler warnings by using stop on warnings/treat warnings as errors compiler option?

2007-03-20 Thread ronnie sahlberg
On 3/21/07, Stephen Fisher [EMAIL PROTECTED] wrote: On Tue, Mar 20, 2007 at 12:44:06PM +, Martin Mathieson wrote: Yup. I edit source files and compile in the Emacs GUI. It makes it easy to spot warnings errors during the compliation process (Control-X ` takes you to the next warning or

Re: [Wireshark-dev] Prevent compiler warnings by using stop on warnings/treat warnings as errors compiler option?

2007-03-20 Thread Guy Harris
On Mar 20, 2007, at 5:21 PM, ronnie sahlberg wrote: How do you mean? Emacs is the only true editor! No, it's not: http://www.gnu.org/fun/jokes/ed.msg.html ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org

Re: [Wireshark-dev] Prevent compiler warnings by using stop on warnings/treat warnings as errors compiler option?

2007-03-20 Thread Guy Harris
On Mar 20, 2007, at 1:08 PM, Stephen Fisher wrote: Of course, this assumes that all the C compilers we use accept - Werror. I doubt that they do (and they definitely don't, if by we you mean everybody who compiles Wireshark - it's been compiled with Sun C, HP's ANSI C compiler for HP-UX,

Re: [Wireshark-dev] Getting destination IP

2007-03-20 Thread Jeff Morriss
Did you see my answer to your question in your previous email? (At the top of the email I said something about the Excel doc but I tried to answer your question below that.) sara vanan wrote: Hi, I am doing a DNS proxy for IPV6. For this I have to get the destination IP(DNS Sever IP

Re: [Wireshark-dev] Prevent compiler warnings by using stop on warnings/treat warnings as errors compiler option?

2007-03-20 Thread Luis Ontanon
On 3/21/07, Guy Harris [EMAIL PROTECTED] wrote: On Mar 20, 2007, at 5:21 PM, ronnie sahlberg wrote: How do you mean? Emacs is the only true editor! No, it's not: http://www.gnu.org/fun/jokes/ed.msg.html There *must* be an ed mode for emacs. so the point is that... After some

Re: [Wireshark-dev] Prevent compiler warnings by using stop on warnings/treat warnings as errors compiler option?

2007-03-20 Thread Guy Harris
Joerg Mayer wrote: No, it won't work. I've spent many many hours in the past to get rid of compiler warnings and it just won't work. While we definitely should try to get rid of some warnings, fixing warnings on one platform may introduce warnings on other platforms (or even gcc versions).