Re: [Wireshark-dev] Using find_conversation with multiple conversations conducted over the same UDP address / port pairs

On Sun, Jun 28, 2009 at 01:19:49PM +1000, kelvin.proc...@au.schneider-electric.com wrote: > Graham Bloice also mentioned raising a bug so I can attach pcap files > etc... for testing - Is this still the right approach now that I have > a proposed patch? Yes, in fact please attach the patch to

Re: [Wireshark-dev] Using find_conversation with multiple conversations conducted over the same UDP address / port pairs

s...@euronet.nl wrote on 27/06/2009 09:52:26 AM: > Hi Kelvin, > > The radius dissectors uses a hash table to store multiple sessions > per conversation. You might want to have a look at it (epan/ > dissectors/packet-radius.c). If you need a tracefile to work with, > showing multiple requests/re

Re: [Wireshark-dev] [Wireshark-bugs] [Bug 3611] New: Buildbot crash output: fuzz-2009-06-26-23834.pcap

Hi, Le samedi 27 juin 2009 à 10:55 -0400, Bill Meier a écrit : > bugzilla-dae...@wireshark.org wrote: > > > > > > > -- > > Problems have been found with the following capture file: > > > > http://www.wireshark.org/download/automated/captures/fuzz-2009-06-26-23834.pcap > > > > stderr: > > Unhan

[Wireshark-dev] snaplen used by text2pcap

Dear all, text2pcap currently uses 102400 as the snaplen in the pcap file header. Wireshark can not currently handle packets longer than WTAP_MAX_PACKET_SIZE, which is currently 1<<16. We had protection code in the pcapng reader code which stopped reading a file when the snaplen was larger than W

Re: [Wireshark-dev] [Wireshark-bugs] [Bug 3611] New: Buildbot crash output: fuzz-2009-06-26-23834.pcap

bugzilla-dae...@wireshark.org wrote: > > > -- > Problems have been found with the following capture file: > > http://www.wireshark.org/download/automated/captures/fuzz-2009-06-26-23834.pcap > > stderr: > Unhandled exception (group=1, code=6) > > [ no debug trace ] > > AFAIK this fuzz'd fil

[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/1864 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: solaris-10-sparc Build

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

The Buildbot has detected a new failure of Windows-XP-Win64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-XP-Win64/builds/774 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-win64 Build R

[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/6406 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-ppc

The Buildbot has detected a new failure of OSX-10.5-ppc on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-ppc/builds/1414 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-ppc Build Reason: Bui

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

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/2741 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason: Bui