Re: [Wireshark-dev] Patch submitted for IPFIX file format support

2010-09-21 Thread Hadriel Kaplan
Agree - updated/replacement diff patch has been attached to the bug, which now does a 2-level-deep sanity checking, for multiple records in the file before calling it good, with an environment variable for changing the number of records to check. (based on ERF model) Thanks for the tip! -hadri

[Wireshark-dev] writing batch application using wireshark and its dissectors

2010-09-21 Thread Iftikhar Rathore
Hi Sorry, if it has been asked before, I could not find any info on making an application that uses several dissectors provided by wireshark. In other words I need to write an application that doe's analysis and measures timing on a capture. I cannot use the plugin architecture because I need to be

Re: [Wireshark-dev] Encapsulated IP

2010-09-21 Thread Ronald Howe
I understand that there is no guarantee. All I really want to do is change the display for source and destination not change anything to do with the packet. The packet is a UDP which gets haded to my dissector with some information from our protocol. I use that then tvb_new_subset and call_disse

Re: [Wireshark-dev] Encapsulated IP

2010-09-21 Thread Guy Harris
On Sep 21, 2010, at 9:51 AM, Ronald Howe wrote: > ok Can I then use SET_ADDRESS to put the Source and Destination fields back > to the original IP address not the encapsulated Address? We make no guarantee whatsoever that dissectors for protocols running atop the encapsulated IP will work cor

Re: [Wireshark-dev] Patch submitted for IPFIX file format support

2010-09-21 Thread Jeff Morriss
Hadriel Kaplan wrote: > Howdy, > I've submitted bug 5242 with an attached patch diff for supporting the IPFIX > file format, per RFC 5655. > https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5242 > > The one open issue/question I have regards a heuristic for determining if > it's the right fil

Re: [Wireshark-dev] Encapsulated IP

2010-09-21 Thread Ronald Howe
ok Can I then use SET_ADDRESS to put the Source and Destination fields back to the original IP address not the encapsulated Address? That would be more useful to the guys using the tool. thanks Ron ge: 5 Date: Mon, 20 Sep 2010 17:16:39 -0700 From: Ronal

[Wireshark-dev] Patch submitted for IPFIX file format support

2010-09-21 Thread Hadriel Kaplan
Howdy, I've submitted bug 5242 with an attached patch diff for supporting the IPFIX file format, per RFC 5655. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5242 The one open issue/question I have regards a heuristic for determining if it's the right file type. Unfortunately, the IPFIX fi

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

2010-09-21 Thread buildbot-no-reply
The Buildbot has detected a new failure of OSX-10.5-PowerPC on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-PowerPC/builds/1043 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-ppc Build Reas

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

2010-09-21 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/1144 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-XP-x86

2010-09-21 Thread buildbot-no-reply
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/1095 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason

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

2010-09-21 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/1186 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-21 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/782 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.6-x64 Build Reason: Buil

Re: [Wireshark-dev] [Wireshark-commits] rev 34167: /trunk/gtk/ /trunk/gtk/: menus.c

2010-09-21 Thread Stig Bjørlykke
On Tue, Sep 21, 2010 at 7:24 AM, wrote: >  Wrong signature used for a GtkToggleActionEntry callback. "Show Resolved" still does not work, and I get this warning at startup: Gtk-CRITICAL **: gtk_ui_manager_get_widget: assertion `GTK_IS_UI_MANAGER (self)' failed In menus_init() you seem to use ui

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

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