Re: [Wireshark-dev] filter expression required

2007-07-01 Thread Amit Paliwal
I cant afford to loose any packet because I have to run this application for RTOS so packets will eb coming with great speed. "Gilbert Ramirez" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 07/02/2007 12:05 PM Please respond to Developer support list for Wireshark To "Developer support lis

Re: [Wireshark-dev] filter expression required

2007-07-01 Thread Amit Paliwal
thx gilbert i already used the port number and it is working fine... thx for giving em your vlauable time. "Gilbert Ramirez" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 07/02/2007 12:05 PM Please respond to Developer support list for Wireshark To "Developer support list for Wireshar

Re: [Wireshark-dev] filter expression required

2007-07-01 Thread Gilbert Ramirez
Okay, so that's a capture filter, and it won't work. Capture filters (-f) use pcap syntax, while display filters (used *after* the capture is made) use wireshark syntax. You should be able to use -R instead of -f, but note that this uses more processing than -f, so if the packets are coming in fa

[Wireshark-dev] Debian package files for 0.99.6

2007-07-01 Thread Jaap Keuter
Hi Frederic, I noticed that Wireshark 0.99.6pre1 came in on testing so it would be great if you can send the new package files to the list so they can be put into the repository before the real 0.99.6 comes out. Thanx, Jaap ___ Wireshark-dev mailing

Re: [Wireshark-dev] filter expression required

2007-07-01 Thread Amit Paliwal
Command line:- wireshark -i \Device\NPF_{52EFAA93-34C5-4F7E-80AE-638A48E3F1BD} -k -f UDP but I want something like Command line:- wireshark -i \Device\NPF_{52EFAA93-34C5-4F7E-80AE-638A48E3F1BD} -k -f UDP contains my_protocol so that only my_protocol gets sniffed. "Gilbert Ramire

Re: [Wireshark-dev] filter expression required

2007-07-01 Thread Gilbert Ramirez
Can you show us the command-line you are using? --gilbert On 7/2/07, Amit Paliwal <[EMAIL PROTECTED]> wrote: yes that is what i am saying, when i try to give a filter from Wireshark GUI i am able to do so, but I want the same scenario in command line alsonot from GUI. *"Gilbert Ramir

Re: [Wireshark-dev] filter expression required

2007-07-01 Thread Amit Paliwal
yes that is what i am saying, when i try to give a filter from Wireshark GUI i am able to do so, but I want the same scenario in command line alsonot from GUI. "Gilbert Ramirez" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 07/02/2007 11:31 AM Please respond to Developer support list f

Re: [Wireshark-dev] filter expression required

2007-07-01 Thread Gilbert Ramirez
A pcap filter? You mean a capture file? The pcap/capture filter syntax does not provide a 'contains' keyword, so it's not possible. You can only use 'contains' in the display filter syntax, which is unique to wireshark (and tshark, etc.) --gilbert On 7/2/07, Amit Paliwal <[EMAIL PROTECTED]> wrot

Re: [Wireshark-dev] filter expression required

2007-07-01 Thread Amit Paliwal
yes i am using 'contains' keyword, and i am giving name of my protocol which is a string. i am running it on Windows and i used 'udp contains my_protocol' also but its not working... i need to give filter expressions defined by pcap, but i am not getting any documentation of it. "Gil

Re: [Wireshark-dev] filter expression required

2007-07-01 Thread Gilbert Ramirez
You're really using the "contains" keyword? That's for strings and binary strings. The spaces in your filter are probably confusing the shell when you invoke wireshark/tshark from the command-line. Are you running on Unix? Use single quotes around your filter: tshark 'udp contains xx

[Wireshark-dev] filter expression required

2007-07-01 Thread Amit Paliwal
I want to set command line filter expression for proprietary protocol that is registered over UDP by its name. I am able to do it directly in Wireshark GUI by setting the expression as "UDP contains my_protocol", but I need to do the same from command line that I am unable to do right now. Plea

Re: [Wireshark-dev] Beginner article for custom dissector now on Code Project

2007-07-01 Thread Jaap Keuter
Hi Ken, Did a quick review of your article. These are the point you could improve. 8<--- 7.0 Your Dissector Code You can use a text editor of your choice to open the packet-yourprotocol.c. Let's take it line by line: #ifdef HAVE_CONFIG_H # include "config.h" #endif #include

Re: [Wireshark-dev] [Wireshark-commits] rev 22227: /trunk//trunk/asn1/cmip/: Makefile.nmake cmip-exp.cnf cmip.cnfpacket-cmip-template.c /trunk/epan/dissectors/: packet-cmip.cpacket-cmip.h packet-gnm.c

2007-07-01 Thread Anders Broman
Hi, Right :-) /Anders _ Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] För Kukosa, Tomas Skickat: den 1 juli 2007 21:21 Till: wireshark-dev@wireshark.org Ämne: Re: [Wireshark-dev] [Wireshark-commits] rev 7: /trunk//trunk/asn1/cmip/: Makefile.nmake cmip-exp.cnf cmip.cnfpacket-c

Re: [Wireshark-dev] Beginner article for custom dissector now on Code Project

2007-07-01 Thread ronnie sahlberg
You need to terminate the value_string with a {0,NULL} entry to tell wireshark where it ends. Othervise you risk reading beyond the end which will cause a segfault. On 7/1/07, Ken Thompson <[EMAIL PROTECTED]> wrote: > I've recently published a beginner article on creating a custom > dissector. T

Re: [Wireshark-dev] [Wireshark-commits] rev 22227: /trunk/ /trunk/asn1/cmip/: Makefile.nmake cmip-exp.cnf cmip.cnf packet-cmip-template.c /trunk/epan/dissectors/: packet-cmip.c packet-cmip.h packet-gn

2007-07-01 Thread Kukosa, Tomas
Hi, I guess #.TABLE2_BODY and #.TABLE1_BODY directives in the cmip.cnf are useless and only the rest of copy and past. Am I right? Tomas Od: [EMAIL PROTECTED] za uživatele [EMAIL PROTECTED] Odesláno: ne 1.7.2007 20:48 Komu: [EMAIL PROTECTED] Předmět: [Wiresha

[Wireshark-dev] Beginner article for custom dissector now on Code Project

2007-07-01 Thread Ken Thompson
I've recently published a beginner article on creating a custom dissector. This article would not of been possible without the developers guide. Note: The article is designed for the Win32 environment. http://www.codeproject.com/useritems/custom_dissector.asp Regards Ken ___

Re: [Wireshark-dev] Wireshark conference

2007-07-01 Thread Gerhard Gappmeier
Sounds interesting. I believe this would be especially interesting for developers. Using wireshark is not that difficult, but maybe users have a different opinion. Where do you plan to make this happen? Europe or USA? Where do most WS developers come from? You could offer wireshark developers w