For When You Can't Have The Real Thing
[ start | index | login ]
start > iperf


Created by dave. Last edited by dave, 11 years and 252 days ago. Viewed 2,485 times. #3
[diff] [history] [edit] [rdf]
(14 August 2012)

Notes on iperf

Available on rpmforge.

Basic throughput testing, TCP:

  • run the server
# iperf -s
  • run the client
# iperf -c
Client connecting to, TCP port 5001
TCP window size: 16.0 KByte (default)
[  3] local port 46617 connected with port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec  1.10 GBytes    944 Mbits/sec

It is popular to use iperf in udp mode to detect dropped packets. To do this:

  • run the server in udp mode:
# iperf -s -u
  • run the client in udp mode, rate-limited to 100 Mb/s:
# iperf -c -u -b 100m -i 1

Beware that when using UDP, the client will send at either its local maximum rate or the defined rate -- even if the server can't deal with that volume of data, and what the server can't deal with will be reported as lost packets. This is not necessarily a problem with your network. (UDP packets get lost. That's life.)

no comments | post comment
This is a collection of techical information, much of it learned the hard way. Consider it a lab book or a /info directory. I doubt much of it will be of use to anyone else.

Useful: | Copyright 2000-2002 Matthias L. Jugel and Stephan J. Schmidt