gmane.network.wireshark.devel

Windows build for VS 2008

Nathan Jennings — 2008-07-25T03:51:04

Hello, For some reason I've found myself on Windows with VS 2008! Where, oh where, is my FreeBSD partition? ;-) I think it's a gravitational force field of some sort from another dimension that's inescapable for me. :-) I spent a bit of time last night with my Windows build environment which is Visual Studio 2008 Pro and I had a couple of thoughts. I disabled most of the optional packages, but did find ADNS ran into a compile error... something about a struct type redefinition; but I commented that package out and was able to compile everything else OK. I ended up modifying some lines like below in "Makefile.nmake" to get Wireshark to run and avoid the initialization error from the non-existent manifests; which basically means adding the MSVC variant so mt.exe gets executed for wireshark and all the other instances of lines where I found "mt.exe": Was: !IF "$(MSVC_VARIANT)" == "MSVC2005" || "$(MSVC_VARIANT)" == "MSVC2005EE" || "$(MSVC_VARIANT)" == "DOTNET20" mt.exe -nologo -manifest "wiresha

display filter for expert/tcp analysis info

Nathan Jennings — 2008-07-25T03:12:15

Hello, Is there a way to use the display filter syntax to filter packets based on the expert/tcp analysis output (strings)? What I'd like to do is construct a display filter that matches an expert/tcp analysis string like "TCP segment lost", or something similar. I could then use this filter in the IO Graph window to show/highlight the affected packets in the line graph. I looked at the wishlist on the Wiki but didn't see anything. Any ideas on how difficult this might be to implement? Maybe point me to where I might get started? Thanks, -Nathan

interesting issues with multiple calls to dissector

Roger Wu — 2008-07-25T01:05:52

Out of Memory issue

Kumar, Hemant — 2008-07-25T00:12:26

Plugin Dissector with multiple .c files

Jason Dick — 2008-07-24T22:45:30

I have a plugin dissector I am working on that dissects a custom protocol with about a dozen main message types. In order to manage it easier I have broken the code into multiple .c files. I seems that when I do that though, the actual functions I call in the 2nd .c file have problems with the ett subtree array. When compiled and run I see the following errors for all packets dissected in the 2nd .c file. Dissector bug, protocol BLAH: proto.c:3640: failed assertion "idx >=0 && idx < num_tree_types" Here is the snippet of code: dissect_keep_alive(tvbuff_t *tvb, packet_info *pinfo, int offset, proto_tree *tree, int message_length) { proto_item *ti = NULL; proto_tree *keepalive_tree = NULL; if (tree) { ti = proto_tree_add_text(tree, tvb, offset, message_length, "KeepAlive"); ti = proto_tree_add_text(tree, tvb, offset, message_length, "ett_keepalive %d",ett_keepalive); keepalive_tree = proto_item_add_subtree(ti, ett_keepalive); p

Getting rid of proto_tree_add_*_hidden()

Jeff Morriss — 2008-07-23T21:14:08

I ran checkAPIs on the dissectors today and was amazed at how few warnings came out. :-) One of the things I noticed was there were no warnings about dissectors using the proto_tree_add_*_hidden() functions. I just cleaned up a couple spots the tool missed and Wireshark now compiles fine without those functions. Any reason not to remove them (and may they RIP)? The only risk I see is that private dissectors/plugins may still use the functions but I'm comfortable with that.

[PATCH] bugfix for Ethernet POWERLINK dissector

Daniel Krueger — 2008-07-23T19:20:21

Hi, the attached patch fixes a bug in the dissection of the StatusResponse, where device-specific error code is only 6 Bytes long instead of 8 Bytes. Additionally, I changed the spelling (i.e. the case) of "Ethernet POWERLINK" to the new preferred one of the EPSG. cu Daniel Index: epan/dissectors/packet-epl.c =================================================================== --- epan/dissectors/packet-epl.c(revision 25515) +++ epan/dissectors/packet-epl.c(working copy) < at >< at > -1,6 +1,6 < at >< at > /* packet-epl.c - * Routines for "Ethernet Powerlink 2.0" dissection - * (ETHERNET Powerlink V2.0 Communication Profile Specification Draft Standard Version 1.0.0) + * Routines for "Ethernet POWERLINK 2.0" dissection + * (Ethernet POWERLINK V2.0 Communication Profile Specification Draft Standard Version 1.0.0) * * Copyright (c) 2006: Zurich University of Applied Sciences Winterthur (ZHW) * Institute of Embedded Systems (InES) < at >< at > -970,8 +970,8 < at >< at > proto_tree_add_item(epl_seb_tree, hf

Using ptvcursor in a Plugin

DeRosa, Anthony — 2008-07-23T17:13:29

I'd like to use ptvcursor in a plugin I am writing (in Windows with VS8), but the ptvcursor API does not seem to be available to plugins. That is, when I do 'dumpbin /exports epan\libwireshark.lib', the ptvcursor API is not present, and I get link errors (unresolved external symbol _ptvcursor*) when I build my plugin. However, the file README.plugins states that, "In fact all of the functions described in README.developer can be used in the plugins exactly as they are used in standard dissectors." Is this statement false, or am I doing something wrong? Thanks, Anthony DeRosa This e-mail and any files transmitted with it may be proprietary and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the sender. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of ITT Corporation. The recipient should check this e-mail and any attachme

Bug 2581 - Filter autocompletion

Abhik Sarkar — 2008-07-23T11:33:23

Hi Bahaa / Martin, Ever since I have seen this enhancement request raised, I have been eager to try it out. But, now that I have compiled the latest SVN version... it doesn't seem to work (that is, no pop-up menu appears with the suggested values) . Must I do anything special to enable the feature? Thanks, Abhik. PS: Build information Version 1.0.99-AS (SVN Rev 25800) Copyright 1998-2008 Gerald Combs public.gmane.org> and contributors. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled with GTK+ 2.12.11, with GLib 2.16.5, with WinPcap (version unknown), with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8, with ADNS, with Lua 5.1, with GnuTLS 2.3.8, with Gcrypt 1.4.1, with MIT Kerberos, with PortAudio V19-devel (built Jul 23 2008), with AirPcap. Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.0.2 (packet.dll versio

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

2008-07-23T03:29:25

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/4590 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason: Build Source Stamp: HEAD Blamelist: wmeier BUILD FAILED: failed shell_12 sincerely, -The Buildbot

Dissector Registration Query

Kumar, Hemant — 2008-07-23T00:11:25

Decoding an incoming message into an array

Sachin Kumar Verma — 2008-07-22T06:41:21

Accessing SCTP data chunk length etc

Gastermann, Bernd Christian — 2008-07-21T13:20:20

wireshark to sql

Saeed Akhtar — 2008-07-22T12:49:12

sudhanshu gautam wants to chat

sudhanshu gautam — 2008-07-22T12:35:50

I've been using Google Talk and thought you might like to try it out. We can use it to call each other for free over the internet. Here's an invitation to download Google Talk. Give it a try! ----------------------------------------------------------------------- sudhanshu gautam wants to stay in better touch using some of Google's coolest new products. If you already have Gmail or Google Talk, visit: http://mail.google.com/mail/b-6e7bf380eb-3d1ab094ec-aecc989fc3fa1c4f You'll need to click this link to be able to chat with sudhanshu gautam. To get Gmail - a free email account from Google with over 2,800 megabytes of storage - and chat with sudhanshu gautam, visit: http://mail.google.com/mail/a-6e7bf380eb-3d1ab094ec-c751ec941a Gmail offers: - Instant messaging right inside Gmail - Powerful spam protection - Built-in search for finding your messages and a helpful way of organizing emails into "conversations" - No pop-up ads or untargeted banners - just text ads and related information that are relevan

Text2pcap and bidirectional traffic

Barnes, Pat — 2008-07-22T04:50:25

I don't have any traffic to test my dissector against, because the components in the system that will be generating that traffic aren't ready yet. Until then, I've used text2pcap to construct some capture files from scratch. There is a bit of a problem though: The -T (add TCP headers) option results in packets only going in one direction. As a bit of hack, I've put this code in the process_directive function: static void process_directive (char *str) { guint32 tmp; str += 11; //Strip off the #TEXT2PCAP and first space if (strncmp("INVERT", str, 6) == 0) { if (hdr_ip) { tmp = HDR_IP.src_addr; HDR_IP.src_addr = HDR_IP.dest_addr; HDR_IP.dest_addr = tmp; } if (hdr_tcp || hdr_udp) { tmp = hdr_src_port; hdr_src_port = hdr_dest_port; hdr_dest_port = tmp; } fprintf(stdout, "Inverted source and destination \n"); } else { fprintf(stderr, "\n--- Directive [%s] currently unsupported ---\n", str-11); } } Such that a '#TEXT2PCAP INVERT' will switch the directions around. The only

help with tcp_dissect_pdus

Kwan Ng [LAVA] — 2008-07-21T19:51:07

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

2008-07-21T19:31:22

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/4583 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason: Build Source Stamp: HEAD Blamelist: etxrab BUILD FAILED: failed shell_5 sincerely, -The Buildbot

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

2008-07-21T18:36:22

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/407 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

New GTK packages

Anders Broman — 2008-07-21T10:06:50

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

2008-07-20T20:57:11

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/402 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