[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-x86

2010-09-20 Thread buildbot-no-reply
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/1182 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason: Bui

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.6-x64

2010-09-20 Thread buildbot-no-reply
The Buildbot has detected a new failure of OSX-10.6-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.6-x64/builds/778 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.6-x64 Build Reason: Buil

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-7-x64

2010-09-20 Thread buildbot-no-reply
The Buildbot has detected a new failure of Windows-7-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/1139 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-7-x64 Build Reason:

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-7-x64

2010-09-20 Thread buildbot-no-reply
The Buildbot has detected a new failure of Windows-7-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/1136 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-7-x64 Build Reason:

Re: [Wireshark-dev] Encapsulated IP

2010-09-20 Thread Guy Harris
On Sep 20, 2010, at 5:16 PM, Ronald Howe wrote: > The col_set_writable does not seem to make a difference in the source and > destination address Nope. The columns are set based on the addresses set by SET_ADDRESS, and we do not allow a dissector to prevent another dissector from setting the

Re: [Wireshark-dev] Encapsulated IP

2010-09-20 Thread Ronald Howe
The col_set_writable does not seem to make a difference in the source and destination address They seem to update when I call the ip dissector again. If I could read those columns before I call the dissector I could replace the fields when it returns but I don't see a function in column-utils.

Re: [Wireshark-dev] Virtual WireShark appliance

2010-09-20 Thread Guy Harris
On Sep 20, 2010, at 1:44 PM, john s wolter wrote: > Sake and Marco, > > but Nobody's arguing against the idea of a Wireshark virtual appliance, as far as I can tell. As Sake said: > The problem is how to get > packets to the virtual appliance. Most virtual switches that come > with the v

Re: [Wireshark-dev] Virtual WireShark appliance

2010-09-20 Thread john s wolter
Sake and Marco, but the idea is to have a software only virtual appliance that could be loaded on the likes of any Cloud service like Amazon's EC2 or HP's or IBM's virtual Cloud machines. Doing EC2 for example, you would have a minimal LINUX core setup virtual appliance. Here's the virtual i

Re: [Wireshark-dev] Virtual WireShark appliance

2010-09-20 Thread Marco van den Bovenkamp
On 20-9-2010 21:34, Sake Blok wrote: > wireshark installed, ready to deploy). The problem is how to get > packets to the virtual appliance. Most virtual switches that come > with the virtualization environment just don't do port mirroring and > such (please correct me if I'm wrong here nowadays).

Re: [Wireshark-dev] Virtual WireShark appliance

2010-09-20 Thread Sake Blok
On 20 sep 2010, at 06:58, john s wolter wrote: > WireShark needs to have software virtual appliances. This for the Cloud > computing services and for the virtual environments like Xen. A minimal > virtual WireShark appliance could be added as an observer as part of a cloud > array or Xen envi

Re: [Wireshark-dev] Encapsulated IP

2010-09-20 Thread Stephen Fisher
On Mon, Sep 20, 2010 at 10:22:45AM -0700, Ronald Howe wrote: > Hello I am new and have a question about the IP dissector. I have > written a plug-in for my work and one of the packets has encapsulated > IP. I call the IP dissector and that works fine my question is there > any way to call the

[Wireshark-dev] Encapsulated IP

2010-09-20 Thread Ronald Howe
Hello I am new and have a question about the IP dissector. I have written a plug-in for my work and one of the packets has encapsulated IP. I call the IP dissector and that works fine my question is there any way to call the dissector and not have it update the source and destination fields? Can

Re: [Wireshark-dev] Make wireshark error

2010-09-20 Thread Stephen Fisher
Guy meant the output from the configure script when it is run - the "Checking for..." type output. ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wir

Re: [Wireshark-dev] TCAP different upper layer

2010-09-20 Thread robie . die . katze
hi, thx. that was the missing parameter... i changed ssn in tcap to 146. then the the first 2 frames where displayed correct. the next 2 frames where shown as tcap. after selecting 'Service Respons Time Analyse' & 'persistent stats for SRT' in tcap the last 2 frames where also displayed correct.

Re: [Wireshark-dev] TCAP different upper layer

2010-09-20 Thread DROUIN, FLORENT (FLORENT)
Hi, Did you add the SSN 146 in the SCCP SSN list of the TCAP preferences ? Regards Florent -Message d'origine- De : wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] De la part de robie.die.ka...@gmx.at Envoyé : lundi 20 septembre 2010 15:38 À : w

Re: [Wireshark-dev] TCAP different upper layer

2010-09-20 Thread robie . die . katze
hi, thx for the tipps. i had a look to the camel2.pcap file and also camel.pcap but wireshark (1.4) showed me only sccp packets with the data block. tcap & camel where not displayed. is there anything special to configure? i switched on 'service response time analyse' for camel & tried it also for

Re: [Wireshark-dev] Building latest trunk

2010-09-20 Thread Steve
Hi, I have actually just found the problem. If you have the MS SUA installed it finds those tools first due to the path, the verify works because it finds the tools its looking for, and hence causes an issue. The verify tools does not check for the correct version and command in this instance.

Re: [Wireshark-dev] Building latest trunk

2010-09-20 Thread Jaap Keuter
Hi, Well, how nice. Could this be Yet Another slash-back slash transposition issue? The original line from the runlex shell script is: outfile=`echo "$1" | sed 's/-o(.*)/1/'` So how come these are all slashes now? Thanks, Jaap On Mon, 20 Sep 2010 08:48:25 +0100, "Steve" wrote: Hi al

[Wireshark-dev] Building latest trunk

2010-09-20 Thread Steve
Hi all, Can somebody help with the following error. I am using VS2008 env, and latest cygwin, but encounter the following error when building; build output snippet... Microsoft (R) Program Maintenance Utility Version 9.00.21022.08 Copyright (C) Microsoft Corporation. All rights reserved. 'cod