Hi,
Are there any packages (or Wireshark options that I've missed) that can
follow a TCP stream and determine the limiting factor on throughput. E.g
Latency, packet loss, out of sequence packets, window size, or even just
the senders rate onto the wire. I know how to analyse a trace by hand
f
One potentially useful piece of software that is a work in progress is
called Pcapdiff. (http://www.eff.org/testyourisp/pcapdiff/)
Written by Seth Schoen and Steven Lucy it's a pretty useful piece of
software. While still in a relative infant stage I think it could mature
into a very useful tool t
A bit more googling has found the Web100 projects NDT
(http://e2epi.internet2.edu/ndt/). I'm currently making a Linux VM that
can run it. It's useful, but I'm still really after something that can
do it's type of analysis from a packet capture.
Sam
Sam Stickland wrote:
Hi,
Are there any pac
> Date: Tue, 15 Jul 2008 11:05:34 +0100
> From: Sam Stickland <[EMAIL PROTECTED]>
>
> Hi,
>
> Are there any packages (or Wireshark options that I've missed) that can
> follow a TCP stream and determine the limiting factor on throughput. E.g
> Latency, packet loss, out of sequence packets, windo
Wireshark can show the throughput on a bits/sec or pps, by IP, etc. This is
under IO Graphs. You'll want to change the time display format of the main
decode window to Seconds Since Beginning of Capture to sync up time with the
graph.
At least that way, you can just focus on the dips in through
Kevin Oberman es.net> writes:
> tcptrace is old and pretty basic, but it can provide a LOT if
> information. Combined with xplot, the graphs often point to the exact
> nature of a TCP problem, but you need a really good understanding of TCP
> to figure anything out.
Wireshark also provides tcptr
Most of the data and studies I have found on this topic are a bit out
of date.
I would be interested in find out what the average packet size people
are seeing on their backbones is at this point and time? Also for
those in the DC space what is average packet size you are seeing for
web f
This is all from netflow. The results are from two different routers.
IP packet size distribution (43046M total packets):
1-32 64 96 128 160 192 224 256 288 320 352 384 416 448
480
.000 .382 .077 .043 .022 .012 .011 .006 .007 .004 .004 .005 .003 .003
.003
512 544 576 10
On Tue, 15 Jul 2008 16:44:48 PDT, Sean Hafeez said:
> I would be interested in find out what the average packet size people
> are seeing on their backbones is at this point and time?
I predict that if you graph it, there's a ton of packets that are right
around the MTU of the network. almost eq
Please consider to contribute and encourage your team members and fellow
scientists to contribute to the following federated events.
Thanks for forwarding the information on this Call for Submissions to those
potentially interested to submit.
= Call for Submissions ===
InfoSys 2009, Apr
10 matches
Mail list logo
