On Tue, Aug 30, 2011 at 2:39 PM, Kevin Johnson <kevin.john...@noaa.gov>wrote:
>
> Actual: 4260724 packets (5515523064 bytes) sent in 117.95 seconds.
> Rated: 46761536.0 bps, 356.76 Mbps, 36123.14 pps
>
> We noticed that 356MB/s is actually greater than the top speed which can be
> achieved over a GB network ... for my test, I just had a single cat-5e cable
> going from eth0 on one machine to eth0 on the other and both configured with
> private LAN addresses.
>
First, it looks like you're using a somewhat older version of tcpreplay (I
was similarly confused with the output from that version).
The first number (46761536.0) is actually the *Bytes* per second, it should
be labeled as Bps and is in the latest version I believe. The second number
(356.76) is the speed in *bits* per second, however in your version the
calculation is incorrect (using 1024*1024 instead of 1000*1000 for the units
conversion).
So, you sent 5515523064 Bytes in 117.95 seconds, this translates into:
5515523064 Bytes / 117.95 seconds = 46761535.09 Bytes per second and
(46761535.09 Bytes * 8 bits/Byte) / (1000*1000) = 374.09 Megabits per
second.
--
Michael J Schultz
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Tcpreplay-users mailing list
Tcpreplay-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tcpreplay-users
Support Information: http://tcpreplay.synfin.net/trac/wiki/Support
