gmane.network.wireshark.devel

buildbot failure in Wireshark (development) onWindows-XP-x86

2008-10-07T07:38:27

The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/4933 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason: Build Source Stamp: HEAD Blamelist: jake BUILD FAILED: failed failed slave lost sincerely, -The Buildbot

buildbot failure in Wireshark (development) onUbuntu-7.10-x86-64

2008-10-06T21:35:54

The Buildbot has detected a new failure of Ubuntu-7.10-x86-64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Ubuntu-7.10-x86-64/builds/302 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-7.10-x86 Build Reason: Build Source Stamp: HEAD Blamelist: etxrab,gerald BUILD FAILED: failed compile sincerely, -The Buildbot

buildbot failure in Wireshark (release) onWindows-XP-x86

2008-10-06T20:54:17

The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark (release). Full details are available at: http://buildbot.wireshark.org/release/builders/Windows-XP-x86/builds/0 Buildbot URL: http://buildbot.wireshark.org/release/ Buildslave for this Build: windows-xp-x86 Build Reason: Build Source Stamp: HEAD Blamelist: gerald BUILD FAILED: failed shell_5 sincerely, -The Buildbot

buildbot failure in Wireshark (development) onOSX-10.5-x86

2008-10-06T20:19:42

The Buildbot has detected a new failure of OSX-10.5-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-x86/builds/884 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason: Build Source Stamp: HEAD Blamelist: etxrab BUILD FAILED: failed compile sincerely, -The Buildbot

buildbot failure in Wireshark (release) onOSX-10.5-x86

2008-10-06T19:42:31

The Buildbot has detected a new failure of OSX-10.5-x86 on Wireshark (release). Full details are available at: http://buildbot.wireshark.org/release/builders/OSX-10.5-x86/builds/0 Buildbot URL: http://buildbot.wireshark.org/release/ Buildslave for this Build: osx-10.5-x86 Build Reason: Build Source Stamp: HEAD Blamelist: gerald BUILD FAILED: failed compile sincerely, -The Buildbot

buildbot failure in Wireshark (release) onUbuntu-7.10-x86-64

2008-10-06T19:37:50

The Buildbot has detected a new failure of Ubuntu-7.10-x86-64 on Wireshark (release). Full details are available at: http://buildbot.wireshark.org/release/builders/Ubuntu-7.10-x86-64/builds/2 Buildbot URL: http://buildbot.wireshark.org/release/ Buildslave for this Build: ubuntu-7.10-x86 Build Reason: Build Source Stamp: HEAD Blamelist: gerald BUILD FAILED: failed compile sincerely, -The Buildbot

Re: SCPS dissector.

Guy Harris — 2008-10-06T16:44:44

On Oct 6, 2008, at 8:09 AM, Cosmin Craciunescu wrote: SCPS compressed TCP, that is (according to the SCPS-NS specification). I.e., the connection starts out using TCP (protocol 6) and then switches to compressed-header TCP (protocol 105)? Does the initial SYN always have SCPS options? If so, dissect_tcpopt_scps() in the TCP dissector could attach the relevant information to the conversation for the TCP connection, and the SCPS dissector could look for the TCP conversation and use that information. If not, the TCP dissector might have to have an option to create a conversation and attach the relevant data (if it already does so, it probably needs to have that controlled by an option, so that a TCP capture with a SYN flood doesn't cause a lot of conversations to be allocated - that was an issue with tcpdump, which allocates a conversation data structure by default).

SCPS dissector.

Cosmin Craciunescu — 2008-10-06T15:09:26

Hello everyone, I've written a SCPS-TP dissector for the compressed segment format. I'd like to commit this someday, but first I need to clean up the code, and fix a few problems. One problem is in order to dissect IP protocol 0x69 (SCPS) I need to have access to information from the TCP packet with the SYN flag for this connection (it's a convoluted protocol). For the life of me, I can't figure out how to tap packets. Even if I do manage to tap the packet, I need the SCPS connection id, which is inside a TCP option, and therefore not available in tap_data, unless packet-tcp is also modified. The short story is, does someone more experienced with wireshark than me want to work with me? I'd do most of the work, but I need help with some of the finer details. Thanks a bunch, Cosmin Craciunescu

Re: New dissector for AYIYA

Bill Meier — 2008-10-05T20:58:21

A dissector for the AYIYA protocol was just committed to the Wireshark development source repository on September 29 .... See: http://anonsvn.wireshark.org/viewvc/trunk/epan/dissectors/packet-ayiya.c from the Wireshark development tree. It sounds like it's time for Plan B :)

Re: New dissector for AYIYA

Jaap Keuter — 2008-10-05T20:50:05

Hi, Good that you check the list for it, because Jelmer Vernooij beat you to the punch. His dissector was committed a few days ago and available in the development build. See https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2898 and http://anonsvn.wireshark.org/wireshark/trunk/epan/dissectors/packet-ayiya.c Thanx, Jaap muxxdevel-KvP5wT2u2U0< at >public.gmane.org wrote:

New dissector for AYIYA

2008-10-05T02:51:51

Hello everyone! I have a student research project where I got the task to write a plugin for wireshark. It should be a dissector for the AYIYA protocol. The wireshark docs recommend to ask the developer mailing list before starting a new development task. The plugin will become a part of my seminar paper, so I hope, there is nobody who is already writing such a plugin. Otherwise this would be a useful information for me. sincerely yours Max Tandetzky

buildbot failure in Wireshark (development) onWindows-XP-x86

2008-10-05T02:58:24

The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/4924 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason: Build Source Stamp: HEAD Blamelist: sahlberg BUILD FAILED: failed shell_13 sincerely, -The Buildbot

buildbot failure in Wireshark (development) onOSX-10.5-x86

2008-10-05T00:44:52

The Buildbot has detected a new failure of OSX-10.5-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-x86/builds/874 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason: Build Source Stamp: HEAD Blamelist: sahlberg BUILD FAILED: failed compile sincerely, -The Buildbot

Re: [Wireshark-commits] rev 26342:/trunk/epan/dissectors/ /trunk/epan/dissectors/:packet-dcerpc-samr.c /trunk/epan/dissectors/pidl/: samr.idl

Joerg Mayer — 2008-10-04T22:24:35

Oh, finally a replacement for the "samr update(s)" commit message ;-> Ciao Joerg

Re: new plugin for SIMULCRYPT protocol readyforcontribution - can anyone check for code quality etc /helpwith submission as build-in?

2008-10-03T15:39:30

Re: Making a dissector for a text proto using ISO10646 (Unicode) in UCS-2(was: Using external DTD)

Luis EG Ontanon — 2008-10-03T14:17:03

About XML/DTD: The XML dissector would need far more than FT_STRING_UNICODE to handle XML with multibyte encoded chars . The tvbparse API (on which the xml dissector) would need to be exteded to handle multi-byte chars. And some parts of how to do it aren't clear to me. What about multibyte chars in entities data and/or entity/element/attribute names in DTDs? That means that the DTD parser needs to be extended as well. \Lego PS: In theory for adding support for an XML protocol all you need is to write a DTD. On Fri, Oct 3, 2008 at 11:59 AM, Anders Broman public.gmane.org> wrote:

buildbot failure in Wireshark (development) onUbuntu-7.10-x86-64

2008-10-03T15:11:46

The Buildbot has detected a new failure of Ubuntu-7.10-x86-64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Ubuntu-7.10-x86-64/builds/292 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-7.10-x86 Build Reason: Build Source Stamp: HEAD Blamelist: stig BUILD FAILED: failed compile sincerely, -The Buildbot

Re: help

Anders Broman — 2008-10-03T15:01:06

help

Cao Guopeng — 2008-10-03T08:01:06

Re: oracle sql dissector

Alexey Eropkin — 2008-10-03T11:02:34

Re: Making a dissector for a text proto using ISO10646 (Unicode) in UCS-2(was: Using external DTD)

Anders Broman — 2008-10-03T09:59:18