gmane.network.wireshark.devel

buildbot failure in Wireshark (development) onUbuntu-7.10-x86-64

2008-12-01T15:20:32

The Buildbot has detected a new failure of Ubuntu-7.10-x86-64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Ubuntu-7.10-x86-64/builds/473 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-7.10-x86 Build Reason: Build Source Stamp: HEAD Blamelist: jmayer,sfisher,stig BUILD FAILED: failed svn sincerely, -The Buildbot

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

2008-12-01T10:50:15

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/1285 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason: Build Source Stamp: HEAD Blamelist: jmayer BUILD FAILED: failed compile sincerely, -The Buildbot

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

2008-12-01T09:33:14

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

Re: Problem in wireshark pcap

Sake Blok — 2008-12-01T07:56:40

Well, as the IP length field is 0 instead of the proper length of the IP datagram, I think the whole dissection of the IP payload is not done. This makes the whole TCP segment look like a ethernet trailer, including a FCS. Which of course will be incorrect... So the question is: Why is the IP length field set to 0? Cheers, Sake On Mon, Dec 01, 2008 at 11:16:35AM +1100, Martin Visser wrote:

Re: Problem in wireshark pcap

Martin Visser — 2008-12-01T00:16:35

Wireshark Menu development

shaan ahmed — 2008-11-30T20:42:59

buildbot failure in Wireshark (release) onUbuntu-8.04-x64

2008-11-30T16:50:42

The Buildbot has detected a new failure of Ubuntu-8.04-x64 on Wireshark (release). Full details are available at: http://buildbot.wireshark.org/release/builders/Ubuntu-8.04-x64/builds/9 Buildbot URL: http://buildbot.wireshark.org/release/ Buildslave for this Build: ubuntu-8.04-x64 Build Reason: Build Source Stamp: HEAD Blamelist: gerald BUILD FAILED: failed compile sincerely, -The Buildbot

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

2008-11-29T22:56:43

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/84 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-ppc Build Reason: Build Source Stamp: HEAD Blamelist: etxrab BUILD FAILED: failed compile sincerely, -The Buildbot

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

2008-11-29T22:37:59

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

buildbot failure in Wireshark (development) onUbuntu-7.10-x86-64

2008-11-29T03:05:40

The Buildbot has detected a new failure of Ubuntu-7.10-x86-64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Ubuntu-7.10-x86-64/builds/465 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-7.10-x86 Build Reason: Build Source Stamp: HEAD Blamelist: jake BUILD FAILED: failed svn sincerely, -The Buildbot

Re: Problem in wireshark pcap

prashanth s — 2008-11-28T16:36:37

Re: How to find duplicate packets with timeinterval less than 2ms

Luis EG Ontanon — 2008-11-28T12:42:57

I mean: Instead of giving it a fixed 2ms time window to look for duplicates make that a parameterizable value. Plus, argument parameters are one letter only and the letter "i" is already used (for (i)nterface), the "w" is taken too (for (w)ritefile). I'd add this param/feature as a "W" for duplicate time (W)indow. e.g. $ dumpcap ... -d -W 15 for 15ms Good work, This is a very useful feature IMHO.

Re: How to find duplicate packets with timeinterval less than 2ms

Petr Janata — 2008-11-28T21:43:28

What is a parameter for the time window? Petr Luis EG Ontanon napsal(a):

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

2008-11-27T21:57:28

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/5231 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 failed slave lost sincerely, -The Buildbot

Re: How to find duplicate packets with timeinterval less than 2ms

Luis EG Ontanon — 2008-11-27T17:28:33

The issue there is that you'll need a buffer whose size is indeterminate (you can get way more than 4 packets in 2ms). So the buffer should adjust. BTW if you add a parameter for the time window it would be certainly more useful. On Fri, Nov 28, 2008 at 4:13 AM, Petr Janata public.gmane.org> wrote:

Re: How to find duplicate packets withtimeinterval less than 2ms

Petr Janata — 2008-11-28T03:13:54

Stephen Fisher napsal(a): If I compare MD5 checksum I can find duplicate packets. I 'd like to add new parameter '-di' into the editcap. The algorithm skip only pakets that are duplicated and also the time interval betwean them is less than 2ms. Petr

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

2008-11-27T16:51:31

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

buildbot failure in Wireshark (development) onUbuntu-7.10-x86-64

2008-11-27T11:22:55

The Buildbot has detected a new failure of Ubuntu-7.10-x86-64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Ubuntu-7.10-x86-64/builds/460 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-7.10-x86 Build Reason: Build Source Stamp: HEAD Blamelist: sfisher BUILD FAILED: failed svn sincerely, -The Buildbot

Re: How to find duplicate packets withtimeinterval less than 2ms

Stephen Fisher — 2008-11-27T10:55:37

According to editcap's man page, "the length and MD5 sum of the MD5 sum of the current packet are compared to the previous four packets." Do you want to change this to 2ms instead? Steve

How to find duplicate packets with time intervalless than 2ms

Petr Janata — 2008-11-27T22:43:58

Hi, I am traiyng to modify editcap, because there is parameter '-d' for skipping duplicate packets. I am going to filter those packets witche have time interval less then 2ms. Do you have any idea? Petr

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

2008-11-27T09:57:11

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