buildbot | 1 Feb 05:02 2009

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

Buildbot URL: http://buildbot.wireshark.org/trunk/

Buildslave for this Build: windows-xp-x86

Build Reason: 
Build Source Stamp: HEAD
Blamelist: guy

BUILD FAILED: failed virus-scan.cmd

sincerely,
 -The Buildbot

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

michele | 1 Feb 11:59 2009
Picon

Re: compare two capture files and io graph

michele wrote:

> I need to compare two different capture files, looking for similarities
> in both of them. Using a modified version of IO Graph and a new field
> which counts the cumulative frames length, I'm plotting a cumulative
> graph of bytes over time. Now I want to (graphically) compare two
> different dumps; this means having two normalized curves [1] plotted in
> the same graph area.
> 
> Do you have any implementation suggestion?

I try to respond to myself.

The capture A contains the packets exchanged during the access to three 
different web sites, say 1, 2 and 3.
The capture B contains the packets exchanged during the access of the 
web site 1.

(The modified version of file.c I'm using, performs a cumulative count 
of frame length, separating the three different site downloads using a 
delta value for the relative time field.)

The graphic comparison can be done in the following way:

- merge captures A and B
- (normalize the time of the two captures)
- try to find a match between A and B moving the horizontal scroll bar 
of IOGraph window (a second new horizontal scroll bar must be added).

Is this reasonable for you?
(Continue reading)

Martin Visser | 1 Feb 21:25 2009
Picon

Re: compare two capture files and io graph

Another alternative is to basically allow two separate instances of Wireshark (with 2 separate capture files), to have their IOGraph windows be displayed adjacent to each other. You might then have a tool, either graphical or via a filter, to be able to synchronise point in the graph. You could also then have the common horizonal scroller. You might also optionally overlay the graphs. The problem with merging the captures files is that you really still have to keep them separate to make all of the other deconding and detailed analysis is consistent.

Regards, Martin

MartinVisser99-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org


On Sun, Feb 1, 2009 at 9:59 PM, michele <michele-6g3A5WUR4fE@public.gmane.orgt> wrote:
michele wrote:

> I need to compare two different capture files, looking for similarities
> in both of them. Using a modified version of IO Graph and a new field
> which counts the cumulative frames length, I'm plotting a cumulative
> graph of bytes over time. Now I want to (graphically) compare two
> different dumps; this means having two normalized curves [1] plotted in
> the same graph area.
>
> Do you have any implementation suggestion?

I try to respond to myself.

The capture A contains the packets exchanged during the access to three
different web sites, say 1, 2 and 3.
The capture B contains the packets exchanged during the access of the
web site 1.

(The modified version of file.c I'm using, performs a cumulative count
of frame length, separating the three different site downloads using a
delta value for the relative time field.)

The graphic comparison can be done in the following way:

- merge captures A and B
- (normalize the time of the two captures)
- try to find a match between A and B moving the horizontal scroll bar
of IOGraph window (a second new horizontal scroll bar must be added).

Is this reasonable for you?








___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev-IZ8446WsY0/dtAWm4Da02A@public.gmane.org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request-IZ8446WsY0/dtAWm4Da02A@public.gmane.org?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe
buildbot | 1 Feb 22:08 2009

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

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

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

buildbot | 1 Feb 22:24 2009

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

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

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

buildbot | 1 Feb 23:14 2009

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

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 checkapi

sincerely,
 -The Buildbot

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

buildbot | 1 Feb 23:38 2009

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

Buildbot URL: http://buildbot.wireshark.org/trunk/

Buildslave for this Build: osx-10.5-x86

Build Reason: 
Build Source Stamp: HEAD
Blamelist: guy

BUILD FAILED: failed compile

sincerely,
 -The Buildbot

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

buildbot | 1 Feb 23:56 2009

buildbot failure in Wireshark (development) on Ubuntu-7.10-x86-64

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

Buildbot URL: http://buildbot.wireshark.org/trunk/

Buildslave for this Build: ubuntu-7.10-x86

Build Reason: 
Build Source Stamp: HEAD
Blamelist: etxrab,guy

BUILD FAILED: failed compile

sincerely,
 -The Buildbot

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

Stig Bjørlykke | 2 Feb 09:03 2009

Re: [Wireshark-commits] rev 27345: /trunk/gtk/ /trunk/gtk/: capture_dlg.h capture_if_dlg.c main_welcome.c

2009/2/1  <guy@...>:
> Log:
>  Add (preliminary, and a bit hacky) support for interface-type icons on OS X.

Is it possible to determine virtual interfaces and loopback interfaces
and have special icons for them?

--

-- 
Stig Bjørlykke
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

Guy Harris | 2 Feb 09:45 2009
Picon

Re: [Wireshark-commits] rev 27345: /trunk/gtk/ /trunk/gtk/: capture_dlg.h capture_if_dlg.c main_welcome.c


On Feb 2, 2009, at 12:03 AM, Stig Bjørlykke wrote:

> Is it possible to determine virtual interfaces and loopback interfaces
> and have special icons for them?

Loopback interfaces - yes; either look for interface beginning with  
"lo" ("lo" or "loN"), or, at least on some OSes, look for the  
IFF_LOOPBACK flag.

Virtual interfaces - what makes an interface "virtual"?
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe


Gmane