[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-XP-x86

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/1588 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason

[Wireshark-dev] buildbot failure in Wireshark (development) on Solaris-10-SPARC

The Buildbot has detected a new failure of Solaris-10-SPARC on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Solaris-10-SPARC/builds/1193 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: solaris-10-sparc Build

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

Stephen Fisher wrote: > On Thu, Nov 18, 2010 at 01:15:47PM -0800, buildbot-no-re...@wireshark.org > wrote: > >> The Buildbot has detected a new failure of Windows-7-x64 on Wireshark >> (development). > >> BUILD FAILED: failed virus-scan.cmd > > The log file contents on the buildbot state that

[Wireshark-dev] buildbot failure in Wireshark 1.4 on Windows-7-x64

The Buildbot has detected a new failure of Windows-7-x64 on Wireshark 1.4. Full details are available at: http://buildbot.wireshark.org/trunk-1.4/builders/Windows-7-x64/builds/134 Buildbot URL: http://buildbot.wireshark.org/trunk-1.4/ Buildslave for this Build: windows-7-x64 Build Reason: Buil

[Wireshark-dev] buildbot failure in Wireshark (development) on Ubuntu-10.04-x64

The Buildbot has detected a new failure of Ubuntu-10.04-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Ubuntu-10.04-x64/builds/756 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-10.04-x64 Build R

[Wireshark-dev] buildbot failure in Wireshark 1.2 on Windows-7-x64

The Buildbot has detected a new failure of Windows-7-x64 on Wireshark 1.2. Full details are available at: http://buildbot.wireshark.org/trunk-1.2/builders/Windows-7-x64/builds/28 Buildbot URL: http://buildbot.wireshark.org/trunk-1.2/ Buildslave for this Build: windows-7-x64 Build Reason: Build

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

On Thu, Nov 18, 2010 at 01:15:47PM -0800, buildbot-no-re...@wireshark.org wrote: > The Buildbot has detected a new failure of Windows-7-x64 on Wireshark > (development). > BUILD FAILED: failed virus-scan.cmd The log file contents on the buildbot state that it found 61 files infected with Heuri

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

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/437 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-7-x64 Build Reason: B

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-XP-x86

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/1581 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason

[Wireshark-dev] Problem loading dissector plugin dll on Windows

Hi, I'm new to wireshark development and wrote a dissector plugin for a proprietary protocol. I'm using Windows XP and MSVC2008EE. Generally the plugin is working fine, but when I copy the dissector .dll to another PC which has already installed and run Wireshark before I always get the followi

Re: [Wireshark-dev] Call register_stat_menu_item from a plugin

Thanks for the replies. I did read up on the statistics tree functionality, but since I need full control over the form (I am trying to display the “last transmitted state” of a protocol, with each subsequent packet representing the current state), I didn’t think it was suitable, since it only

Re: [Wireshark-dev] Filter for generated items

On Thu, Nov 18, 2010 at 06:16:52PM +0100, Helge Kruse wrote: > Am 16.11.2010 21:45, schrieb Stephen Fisher: > > Yes, then making DLL of your plugin for version 1.2.x and 1.4.x > > would be the way to go. > > I doubt that this is true. I started to compare these versions and > found some differe

Re: [Wireshark-dev] Problems with dissecting fragmented packets

Yosi Saggi wrote: > Hi , > > I'm writing a dissector for our LTE PHY packets. I have started working > on fragmented packets. These are Ethernet packets that are fragmented > with some proprietary limitation. Nevertheless we have a PI header > (under the Ethernet header) that is always there in

Re: [Wireshark-dev] Decode As Option

Will Barker wrote: > I’m trying to determine why the “Decode As” context menu option > > 1) is sometimes grayed out My guess is that you don't have a field (or protocol layer) selected which has something (e.g., a TCP port field) that can be used to as a filter/selector for Decode-As. >

Re: [Wireshark-dev] Filter for generated items

Am 16.11.2010 21:45, schrieb Stephen Fisher: > On Tue, Nov 16, 2010 at 09:13:57PM +0100, Helge Kruse wrote: > >> But I cannot convince anybody to update there 1.2.x installations to >> 1.4.x. >> >> So I must now decide if I have to provide a DLL compile with the 1.2.x >> header and libs and an addi

Re: [Wireshark-dev] adding an encap_type_info element

The USER DLTs are really for temporary or experimental or at least internal-only use. If you intend to use your layer for a long time or publish it, it's quite easy to request a new DLT (by emailing the tcpdump-workers list at tcpdump.org). Just be sure that you register one instead of just u

Re: [Wireshark-dev] adding an encap_type_info element

I solved it using WTAP_ENCAP_USER0. ..I think a better solution was it if i could declare a really new "link type". But I think it is going well this way. Von: wireshark-dev-boun...@wireshark.org [wireshark-dev-boun...@wireshark.org] im Auftrag von Lange Jan-Eri

[Wireshark-dev] adding an encap_type_info element

Hello, I want to dissect a packet that is not ethernet compliant. In the following I decribe the strategy to realize this. Can you tell me where I'm wrong? 1. I have to add a new encap_type_info element to the encap_table_base[] struct in the wtap.c file. /* WTAP_ENCAP_MYPHYLAYER */ { "My Phy

Re: [Wireshark-dev] foo dissector of the dev guide

Thanks for the info. I'll try it. But for now the hex editor is Ok. Von: wireshark-dev-boun...@wireshark.org [wireshark-dev-boun...@wireshark.org] im Auftrag von Helge Kruse [helge.kruse-nos...@gmx.net] Gesendet: Donnerstag, 18. November 2010 13:16 An: Dev

Re: [Wireshark-dev] foo dissector of the dev guide

Original-Nachricht > Datum: Thu, 18 Nov 2010 11:22:19 +0100 > Von: Lange Jan-Erik > An: Developer support list for Wireshark > Betreff: Re: [Wireshark-dev] foo dissector of the dev guide > You're right. I captured UDP Frames from my network. Now I'm working with > these Frames

Re: [Wireshark-dev] Problems creating the OsX App

On Thu, Nov 18, 2010 at 11:10 AM, Dirk Jagdmann wrote: > Next I tried a "make osx-app". This is also making without errors and then I > see a Wireshark.app directory is created in packaging/macosx/. However I can > not start it. Trying to start it with the "wireshark" script in > packaging/maco

Re: [Wireshark-dev] Decode As Option

I'm trying to determine why the "Decode As" context menu option 1) is sometimes grayed out 2) does not present all the available protocols in its list Is there an override possible somehow? If the user is certain that protocol FOO starts at offset X then it would be good t

Re: [Wireshark-dev] foo dissector of the dev guide

You're right. I captured UDP Frames from my network. Now I'm working with these Frames an modify them in a HEX Editor for testing.. Thank you very much Von: wireshark-dev-boun...@wireshark.org [wireshark-dev-boun...@wireshark.org] im Auftrag von Guy Harris [...@

[Wireshark-dev] Problems creating the OsX App

Hello Wireshark Developers, I'm completely new to Apple development. I want to test my changes to Wireshark and want to compile on the three major platforms: Linux/BSD, Windows and now Mac. So I have a OsX 10.6, installed Xcode 3 and have used MacPorts 1.9.2 to install the gtk environment. Eve