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

Hello The patch is a "context diff" (diff -c). I forget to use "unify diff" (diff -u) to generate that patch. Sorry about the mix up. You might not be familiar with context diff syntax. The patch actually means removing the extra "Len" in messages away (i.e. replacing the top chunk with the botto

Re: [Wireshark-dev] Unsupported ERF format

On Fri, Feb 16, 2007 at 12:50:20PM +0900, Horyong Choi wrote: > Currently wireshark is support to some ERF header format. > > ERF header format have a totally 11 types according to document at > http://www.endace.com/support/EndaceRecordFormat.pdf > > But wireshark 0.55.9 is only support for typ

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

On Wed, Jan 31, 2007 at 09:20:25PM +0700, Kriang Lerdsuwanakij wrote: > 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

Re: [Wireshark-dev] [patch] Update for packet-jxta.c

On Mon, Jan 29, 2007 at 04:54:10PM -0800, Mike Duigou wrote: > Adds support for dissecting the new version 2 binary wire format messages. > > Has been fuzz tested with a number of traces. Committed as SVN revision 20836. Thanks for your contribution! Steve ___

Re: [Wireshark-dev] Update camel dissector

Checked in /Anders -Ursprungligt meddelande- Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] För [EMAIL PROTECTED] Skickat: den 16 februari 2007 13:27 Till: wireshark-dev@wireshark.org Ämne: [Wireshark-dev] Update camel dissector Hello, I did update the Camel dissector to have t

[Wireshark-dev] Patch for bug 310

This patch fixes the issue of adding list widget numbers to the packet history instead of adding frame numbers. bug310patch.gz Description: GNU Zip compressed data ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mail

Re: [Wireshark-dev] [PATCH] Indicate Empty bitstrings in BER dissector

Stig, Checked in - 20834. Thanks for your attention to detail. Graeme > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Stig Bjørlykke > Sent: 17 February 2007 12:46 > To: Developer support list for Wireshark > Subject: [Wireshark-dev] [PATCH]

Re: [Wireshark-dev] saving "User Specified Decodes"

I have a set of UDP messages with the same problem, they can be on different UDP ports, depending on alot of factors. How do I get a dissector heuristic? Can you point me in the right direction on where to look please? - Original Message - From: "Jaap Keuter" <[EMAIL PROTECTED]> To: <[EM

[Wireshark-dev] [PATCH] Indicate Empty bitstrings in BER dissector

Hi. From X.690: 8.6.2.3 "If the bitstring is empty, there shall be no subsequent octets, and the initial octet shall be zero." The BER dissector marks empty bitstrings as "Padding", but I think it's better to mark this as "Empty". -- Stig Bjørlykke packet-ber.patch.gz Description: GNU

Re: [Wireshark-dev] [PATCH] Option to decode unknown BER OCTET STRINGas BER encoded data

Stig, Checked in - 20831. Thanks. Graeme > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Stig Bjørlykke > Sent: 12 February 2007 19:58 > To: Developer support list for Wireshark > Subject: [Wireshark-dev] [PATCH] Option to decode unknown BER

Re: [Wireshark-dev] build problem at creating libwire shark.lib and object libwireshark.exp

Hi! I've recently moved this stuff from epan/dissectors to plugins/profinet (just where it belong). You may try to delete register.c and register.obj and rebuild. If that doesn't help, try a distclean. Regards, ULFL > -Ursprüngliche Nachricht- > Von: Developer support list for Wiresh