Re: [Wireshark-dev] SVN doesn't compile under MacOS X

2007-01-31 Thread Andreas Fink
On 01.02.2007, at 02:39, Stephen Fisher wrote:On Thu, Feb 01, 2007 at 02:01:41AM +0100, Andreas Fink wrote: current SVN seems to have some double defined symbol conflict:ld_classic: multiple definitions of symbol _svnversionversion_info.o definition of _svnversion in section (__DATA,__data)gtk/libu

Re: [Wireshark-dev] Overriding existing RPC-TCP heuristic dissector with another heuristic one

2007-01-31 Thread Jaap Keuter
Hi, The solution is to improve the heuristics until they can figure out which dissector is the correct one. Thanx, Jaap On Thu, 1 Feb 2007, Shehjar Tikoo wrote: > Hi all > > I am writing a RPC over TCP heuristic dissector but the RPC dissector(in > packet-rpc.c) also registers a heuristic RPC o

[Wireshark-dev] Overriding existing RPC-TCP heuristic dissector with another heuristic one

2007-01-31 Thread Shehjar Tikoo
Hi all I am writing a RPC over TCP heuristic dissector but the RPC dissector(in packet-rpc.c) also registers a heuristic RPC over TCP dissector. It is possible that the packet my heuristic dissector needs, gets routed to the existing dissector. From the list archives I see discussions about ove

Re: [Wireshark-dev] Multiple pdus atop TCP -- a lie in README.developer?

2007-01-31 Thread Richard van der Hoff
Guy Harris wrote: > Then > > 1) have a dissector for a single one of your PDUs; > > 2) use that dissector with tcp_dissect_pdus() when dissecting your > protocol over TCP; > > 3) write your own reassembly code for other protocols and call your > single-PDU dissector from th

Re: [Wireshark-dev] "Cisco format" MAC addresses in display filters?

2007-01-31 Thread Stephen Fisher
On Tue, Jan 30, 2007 at 02:12:28PM -0800, Stephen Fisher wrote: > How hard would it be to allow the display filter to accept "Cisco > format" MAC addresses (..) and still match the usual > format (xx:xx:xx:xx:xx:xx)? Where would I change this? I have committed SVN revision 20660 th

Re: [Wireshark-dev] SVN doesn't compile under MacOS X

2007-01-31 Thread Stephen Fisher
On Thu, Feb 01, 2007 at 02:01:41AM +0100, Andreas Fink wrote: > current SVN seems to have some double defined symbol conflict: > > ld_classic: multiple definitions of symbol _svnversion > version_info.o definition of _svnversion in section (__DATA,__data) > gtk/libui.a(main.o) definition of _svnv

[Wireshark-dev] SVN doesn't compile under MacOS X

2007-01-31 Thread Andreas Fink
current SVN seems to have some double defined symbol conflict: ld_classic: multiple definitions of symbol _svnversion version_info.o definition of _svnversion in section (__DATA,__data) gtk/libui.a(main.o) definition of _svnversion in section (__DATA,__common) gtk/libui.a(about_dlg.o) definitio

Re: [Wireshark-dev] [patch] address_to_str_buf not checking available buffer length

2007-01-31 Thread Gerald Combs
Checked in, with the error string changed to "[Buffer too small]". Thanks! Andrej Mikus wrote: > Accepted or not, I needed to do something to get my working copy > compiled. Attached is the patch if you like to use it. > > Thanks > Andrej > > On Wed, 31.Jan.07 12:29:30 +0100, Andrej Mikus wrote

Re: [Wireshark-dev] bootstrapping SVN checkout

2007-01-31 Thread Guy Harris
On Jan 31, 2007, at 3:07 PM, Andreas Fink wrote: > thanks. It does in fact. Current SVN version hits me size_t in > aircap code (easy to fix, size_t is already there). As far as I know, the airpcap code shouldn't even be built unless you're building on Windows. (If any file is built even if

Re: [Wireshark-dev] bootstrapping SVN checkout

2007-01-31 Thread Andreas Fink
thanks. It does in fact. Current SVN version hits me size_t in aircap code (easy to fix, size_t is already there). Hi, ./autogen.sh && ./configure && make usually does the trick. Thanx, Jaap On Wed, 31 Jan 2007, Andreas Fink wrote: Hello, I've just done a SVN checkout of the sources into

Re: [Wireshark-dev] U3 questions/remarks

2007-01-31 Thread Maynard, Chris
Sorry, let me clarify my preference. I don't mean for the binary executable itself to include the version, but rather the desktop and menu shortcuts would be sufficient enough for me. On UN*X, I guess if there are any symbolic links to the binary, then that might also be useful as well. The sit

Re: [Wireshark-dev] U3 questions/remarks

2007-01-31 Thread Ulf Lamping
Guy Harris wrote: > Maynard, Chris wrote: > >> Just one comment about the name: Personally, I prefer the version as >> part of the program name, not just for U3, but I would prefer it for all >> installs actually. >> > > I would strongly prefer it *NOT* be part of the file name (i.e., *NOT

Re: [Wireshark-dev] bootstrapping SVN checkout

2007-01-31 Thread Jaap Keuter
Hi, ./autogen.sh && ./configure && make usually does the trick. Thanx, Jaap On Wed, 31 Jan 2007, Andreas Fink wrote: > Hello, > > I've just done a SVN checkout of the sources into a new directory. > I have troubles to "bootstrap" this version as there is no > "configure" file. > So I run automa

[Wireshark-dev] bootstrapping SVN checkout

2007-01-31 Thread Andreas Fink
Hello, I've just done a SVN checkout of the sources into a new directory. I have troubles to "bootstrap" this version as there is no "configure" file. So I run automake (version 1.6.3 is installed) and I get: andreas10:~/development/ws/wireshark afink$ automake configure.in:17: no proper implem

Re: [Wireshark-dev] packet statistics screen

2007-01-31 Thread Andrej Mikus
My suggestion would be tshark -z io,stat,60 -q -r capturefile and then sort accordingly. I am new here, but I feel that this type of question is perhaps better for user list rather than dev. Andrej On Wed, 31.Jan.07 12:12:05 -0500, Aamer Akhter wrote: > Hello, > > I'm looking at the ethereal s

Re: [Wireshark-dev] Is anyone working/planning ANSI C12.22

2007-01-31 Thread Guy Harris
On Jan 31, 2007, at 1:34 PM, [EMAIL PROTECTED] wrote: > Is anyone working on or planning a ANSI C12.22 dissector? C12.22 is > the > designation of a new standard that is being developed to allow the > transport of ANSI C12.19 table data over networked connections. > > If not, I'd like to get it

[Wireshark-dev] Is anyone working/planning ANSI C12.22

2007-01-31 Thread jim
Hi folks, Is anyone working on or planning a ANSI C12.22 dissector? C12.22 is the designation of a new standard that is being developed to allow the transport of ANSI C12.19 table data over networked connections. If not, I'd like to get it on the wish list. Thanx, ~Jim

Re: [Wireshark-dev] [PATCH] New menu items to copy packet data

2007-01-31 Thread Stephen Fisher
On Wed, Jan 31, 2007 at 09:14:24AM -, Douglas Pratley wrote: > Ok, I've attached the text as well. > > I must have done something odd with tar and gzip (you can probably > tell that I'm more familiar with Windows than UNIX tools). Will be > more cautious next time... The attachment came ac

Re: [Wireshark-dev] Multiple pdus atop TCP -- a lie in README.developer?

2007-01-31 Thread Guy Harris
On Jan 31, 2007, at 12:02 PM, Richard van der Hoff wrote: > Sorry - I meant that my pdu reassembly needs to work over myriad other > protocols too (my pdus don't align with UDP pdus). Then 1) have a dissector for a single one of your PDUs; 2) use that dissector with tcp_dissect

Re: [Wireshark-dev] packet statistics screen

2007-01-31 Thread Stephen Fisher
On Wed, Jan 31, 2007 at 12:12:05PM -0500, Aamer Akhter wrote: > I'm looking at the ethereal screen in Statistics->Summary and was > wondering if there is a way to calculate the highest pps and bitrate > within a 1 min window. Right now, the stats seem to be over the entire > length of the file.

Re: [Wireshark-dev] Multiple pdus atop TCP -- a lie in README.developer?

2007-01-31 Thread Richard van der Hoff
Anders Broman wrote: >> (I don't want to use tcp_dissect_pdus as this protocol can run over a > > You can solve that by having a separate entry for TCP and call the main > dissector from there. (See SIP, DIAMETER etc). Sorry - I meant that my pdu reassembly needs to work over myriad other proto

Re: [Wireshark-dev] Multiple pdus atop TCP -- a lie in README.developer?

2007-01-31 Thread Anders Broman
>(I don't want to use tcp_dissect_pdus as this protocol can run over a http://www.wireshark.org/mailman/listinfo/wireshark-dev

[Wireshark-dev] Multiple pdus atop TCP -- a lie in README.developer?

2007-01-31 Thread Richard van der Hoff
Hi, I'm trying to write a dissector for a protocol which consists of a series of small (160 bytes or so) PDUs, over TCP. That obviously means that PDUs can span TCP segment boundaries, and each TCP segment can contain several PDUs. README.developer (section 2.7.2) implies that I can just disse

[Wireshark-dev] New dissector - FMP

2007-01-31 Thread Ian Schorr
Hello, Please consider for checkin the following new dissectors, for the FMP protocol. FMP (File Mapping Protocol) is the network protocol basis for EMC's HighRoad (MPFS) technology. Highroad is used to allow multiple clients to share access to NAS-shared files while allowing clients to directl

[Wireshark-dev] [PATCH] Bogus length reported for reassembled UDP packets

2007-01-31 Thread Andrej Mikus
Hi, Wireshark complains about bogus udp length when processing last fragment of UDP data. It compares length field from UDP header with payload size of last fragment. Attached is my attempt to fix this by referring to tvp->length instead of pinfo->iplen - pinfo->iphdrlen. Not entirely sure if it

Re: [Wireshark-dev] U3 questions/remarks

2007-01-31 Thread Guy Harris
Maynard, Chris wrote: > Just one comment about the name: Personally, I prefer the version as > part of the program name, not just for U3, but I would prefer it for all > installs actually. I would strongly prefer it *NOT* be part of the file name (i.e., *NOT* part of the last component of the pa

Re: [Wireshark-dev] [PATCH] User can select dissector based on packet matching display filter

2007-01-31 Thread Guy Harris
Douglas Pratley wrote: > b) Adds functionality analogous to dissector tables, but instead of > directing by field values, there is a list of display-filter / > sub-dissector pairs. A sub-dissector is called if the display filter is > matched by the packet. Display filter values are available o

Re: [Wireshark-dev] What about a universal XML parsing dissector

2007-01-31 Thread John R.
On 1/30/07, Guy Harris <[EMAIL PROTECTED]> wrote: > > On Jan 30, 2007, at 11:07 AM, John R. wrote: > > > Sequence, iteration, algorithms, > > etc. are more naturally handled in code than XML document (that didn't > > stop the abomination that is XSLT though ;-) ). > > Nor did it stop NetPDL: > An

Re: [Wireshark-dev] U3 questions/remarks

2007-01-31 Thread Maynard, Chris
Just one comment about the name: Personally, I prefer the version as part of the program name, not just for U3, but I would prefer it for all installs actually. Wireshark gets installed on quite a few of our servers and the only way to know which version has been installed, and thus which ones ne

[Wireshark-dev] packet statistics screen

2007-01-31 Thread Aamer Akhter
Hello, I'm looking at the ethereal screen in Statistics->Summary and was wondering if there is a way to calculate the highest pps and bitrate within a 1 min window. Right now, the stats seem to be over the entire length of the file... Any other tools that might do this? -- Aamer Akhter / [EMAIL

Re: [Wireshark-dev] col_add_fstr doesn't _add_ string to column

2007-01-31 Thread Amit Khullar
Hi, col_append_fstr() could be used. cheers, Amit Wiese, Hendrik wrote: >Hi list, > >I've got another problem here developing a dissector: why doesn't >col_add_fstr() really _add_ (append) a string to the selected column, >but clears the column and fills it with a new one? > >I've got some TP

Re: [Wireshark-dev] col_add_fstr doesn't _add_ string to column

2007-01-31 Thread Jaap Keuter
Hi, Sure: http://anonsvn.wireshark.org/wireshark/trunk/epan/column-utils.h Thanx, Jaap On Wed, 31 Jan 2007, Wiese, Hendrik wrote: > Hi list, > > I've got another problem here developing a dissector: why doesn't > col_add_fstr() really _add_ (append) a string to the selected column, > but clears

[Wireshark-dev] col_add_fstr doesn't _add_ string to column

2007-01-31 Thread Wiese, Hendrik
Hi list, I've got another problem here developing a dissector: why doesn't col_add_fstr() really _add_ (append) a string to the selected column, but clears the column and fills it with a new one? I've got some TPKT encapsulated messages here inside a single TCP packet and I'd like to get all of

Re: [Wireshark-dev] [patch] address_to_str_buf not checking available buffer length

2007-01-31 Thread Andrej Mikus
Accepted or not, I needed to do something to get my working copy compiled. Attached is the patch if you like to use it. Thanks Andrej On Wed, 31.Jan.07 12:29:30 +0100, Andrej Mikus wrote: > On Mon, 29.Jan.07 12:49:00 -0800, Gerald Combs wrote: > > Andrej Mikus wrote: > > > > > In file to_str.c I

[Wireshark-dev] [PATCH] Fix bugs in IuUP

2007-01-31 Thread Kriang Lerdsuwanakij
Hello While I reading source code of IuUP dissector, I notice some obvious bugs inside the code. One is a missing assignment that causes the following "if (iuup_circuit)" block to never execute. Another is wrong field names. Althoug both won't show up in final result (for the first bug, the call

Re: [Wireshark-dev] address_to_str_buf not checking available buffer length

2007-01-31 Thread Andrej Mikus
On Mon, 29.Jan.07 12:49:00 -0800, Gerald Combs wrote: > Andrej Mikus wrote: > > > In file to_str.c I notice function address_to_str_buf that takes buf_len > > as argument, but does not use it for IPv4 and IPv6 addresses: > > > Unfortunately, there wasn't a mechanism to ensure that the buffer was

Re: [Wireshark-dev] Use ethereal as a proprietary protocol parser; no ethernet/IP decoding

2007-01-31 Thread Hal Lander
Tom will be distributing the code since his company will be selling the communications systems to the utility industry. I still don't see a problem though, it just means the utility company will be entitled to the source code, and have to be told they are entitled to it. If the proprietary pro

Re: [Wireshark-dev] Use ethereal as a proprietary protocol parser; no ethernet/IP decoding

2007-01-31 Thread Jaap Keuter
Hi, You surely can make a dissector for a proprietary protocol, you just can't distribute it without source code. From that sourcecode one can easily write a protocol spec, or at least the static part of it. So don't distribute it and you're fine. The keyword here is distribution. Thanx, Jaap O

Re: [Wireshark-dev] Use ethereal as a proprietary protocol parser; no ethernet/IP decoding

2007-01-31 Thread Abhik Sarkar
Hi, I don't know if I am straying from the core of the topic here, but this particular topic has always foxed me. If a protocol is proprietery (in the sense that the specifications are not open and they might be released only under NDA), then wouldn't writing a dissector for it create legal probl

Re: [Wireshark-dev] [PATCH] New menu items to copy packet data

2007-01-31 Thread Douglas Pratley
> > Stephen Fisher wrote: > > On Mon, Jan 29, 2007 at 10:22:15AM -, Douglas Pratley wrote: > > > >> Are there any other encodings / decodings it would be worth having > >> available (uuencode? zip?). This might be better done as a full > >> "Select bytes and decode / encode" feature ra

Re: [Wireshark-dev] Use ethereal as a proprietary protocol parser; no ethernet/IP decoding

2007-01-31 Thread Hal Lander
Hi Tom, I am just starting to learn how to use Wireshark myself (it used to be Ethereal),messing about with a protocol sent within TCP. You should probably start by downloading Wireshark and running it on your network to see what it does. It will capture and decode the TCP which it knows abo

Re: [Wireshark-dev] Problem with uint preference

2007-01-31 Thread Hal Lander
Hi Jeff, That did the trick :-) I had seen the defines for the various bases so when the function asked for a base I just plugged BASE_DEC in. The old documentation did misslead me but I could kick myself for not plugging in the obvious 10 ! Thanks for clearing that up. Hal From: Jeff Mor

Re: [Wireshark-dev] [PATCH] New menu items to copy packet data

2007-01-31 Thread Douglas Pratley
Ok, I've attached the text as well. I must have done something odd with tar and gzip (you can probably tell that I'm more familiar with Windows than UNIX tools). Will be more cautious next time... Cheers Doug -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf

Re: [Wireshark-dev] How do I get my dissector to work in theDisplay Filter

2007-01-31 Thread Hal Lander
In the function proto_register_foo(void) I register the protocol using the line; proto_foo = proto_register_protocol("Top level text for foo","foo", "foo"); I notice you say lineS, am I missing something? The thing is the dissector is called and the all the other fields are visible in the 'expr

Re: [Wireshark-dev] [REPOST][PATCH] update USB dissector

2007-01-31 Thread Paolo Abeni
Hello, On Tue, 2007-01-30 at 12:19 -0800, Guy Harris wrote: > You might want to check to make sure that file (written out in > big-endian format) can be read by your little-endian machine; I've > attached that capture. It works also on my machine. > I modified the code to make the Linux-speci

Re: [Wireshark-dev] [PATCH] update wiretap and USB dissector

2007-01-31 Thread Paolo Abeni
Hello, On Tue, 2007-01-30 at 13:27 -0800, Guy Harris wrote: > Paolo Abeni wrote: > > This new API should be available > > in the linux kernel starting from version 2.6.21 or 2.6.22. > > but kernel.org only has 2.6.19 as the current version and 2.6.20 as the > upcoming version. Should it just sp