Iperf Ejemplos

08/10/14 IPERF - The Easy Tutorial
Ne twork ing Ipe rf

Last update : 10-12-2010
TOTA L
Since de c 2006
Se arch
1'942'871 Visitors
4'218'042 Page s
If you lik e our tutorials, don't he sitate to support us and visit our sponsors!
Si vous aim e z nos tutoriaux , n'hé site z pas à nous supporte r e t visite r nos sponsors! Nov 2010 Stats
82'909 Visitors
146'476 Page s
OpenManiak 196 countrie s
Full statistics
Me gusta 1878
Settings Measurements Diagram Diamond wedding ring sets He lp us translate

our tutorials!
JO IN the
Ipe rf is a tool to m e asure the bandwidth and the quality of a ne twork link . Jpe rf can be O pe nManiak Te am .
associate d with Ipe rf to provide a graphical fronte nd writte n in Java.
The ne twork link is de lim ite d by two hosts running Ipe rf. OM TEA M
Director:
The quality of a link can be te ste d as follows: Blaise C arre ra
- Late ncy (re sponse tim e or R TT): can be m e asure d with the Ping com m and. Tutorials creation:
- Jitte r (late ncy variation): can be m e asure d with an Ipe rf UDP te st. Blaise C arre ra
- Datagram loss: can be m e asure d with an Ipe rf UDP te st. Translaters:
Giovanni Fre dducci
The bandwidth is m e asure d through TC P te sts. Ange l C hraniotis
Moham . H. Karvan
To be cle ar, the diffe re nce be twe e n TC P (Transm ission C ontrol Protocol) and UDP (Use r Ale x andro Silva
Datagram Protocol) is that TC P use proce sse s to che ck that the pack e ts are corre ctly se nt to the Blaise C arre ra
re ce ive r whe re as with UDP the pack e ts are se nt without any che ck s but with the advantage of Andre i C he rtolyas
be ing quick e r than TC P. Se rgiy Uvarov
Ipe rf use s the diffe re nt capacitie s of TC P and UDP to provide statistics about ne twork link s. Nick ola Kole v
Łuk asz
Finally, Ipe rf can be installe d ve ry e asily on any UNIX/Linux or Microsoft W indows syste m . O ne Nowatk owsk i
host m ust be se t as clie nt, the othe r one as se rve r. Ivo R aisr
C atalin Bivolaru
Bogdan A. C oste a
Kirill Sim onov
O live r Mucafir
Jae Young Je on
Se ungyoon Le e
Jie Yu & Si C he ng
Tao W e i
Yuk iAle x
Fum ihito Yoshida
Muham m ad Tak dir
He re is a diagram whe re Ipe rf is installe d on a Linux and Microsoft W indows m achine .
Ç ağdaş Tüle k
Linux is use d as the Ipe rf clie nt and W indows as the Ipe rf se rve r. O f course , it is also possible
A uditors
to use two Linux box e s.
Le slie Luthi
Joe Ande rson
Je nnife r O ck we ll
Nige l Title y
Alison R e e s
Sabrina Barbe y
Webmaster:
Blaise C arre ra
Iperf tests:
no arg. De fault se ttings -p, -t, -i Port, tim ing and inte rval
-b Data form at -u, -b UDP te sts, bandwidth se ttings
-r Bi-dire ctional bandwidth -m Max im um Se gm e nt Size display
-d Sim ultane ous bi-dire ctional bandwidth -M Max im um Se gm e nt Size se ttings
-w TC P W indow size -P Paralle l te sts
-h he lp
Jperf:
no arg. De fault se ttings

-d Sim ultane ous bi-dire ctional bandwidth
-u, -b UDP te sts, bandwidth se ttings
De fault Ipe rf se ttings:

Also che ck "Jpe rf se ction.
By de fault, the Ipe rf clie nt conne cts to the Ipe rf se rve r on the TC P port 5001 and the bandwidth
openmaniak.com/iperf.php 1/11
displaye d by Ipe rf is the bandwidth from the clie nt to the se rve r.
If you want to use UDP te sts, use the -u argum e nt.
The -d and -r Ipe rf clie nt argum e nts m e asure the bi-dire ctional bandwidths. (Se e furthe r on this
tutorial)
C lie nt side :
#iperf -c 10.1.1.1
------------------------------------------------------------
Client connecting to 10.1.1.1, TCP port 5001
TCP window size: 16384 Byte (default)
------------------------------------------------------------
[ 3] local 10.6.2.5 port 33453 connected with 10.1.1.1 port 5001
[ 3] 0.0-10.2 sec 1.26 MBytes 1.05 Mbits/sec
Se rve r side :
#iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 8.00 KByte (default)
------------------------------------------------------------
[852] local 10.1.1.1 port 5001 connected with 10.6.2.5 port 33453
[ ID] Interval Transfer Bandwidth
[852] 0.0-10.6 sec 1.26 MBytes 1.03 Mbits/sec
Data form atting: (-f argum e nt)
The -f argum e nt can display the re sults in the de sire d form at: bits(b), byte s(B), k ilobits(k ),
k ilobyte s(K), m e gabits(m ), m e gabyte s(M), gigabits(g) or gigabyte s(G).
Ge ne rally the bandwidth m e asure s are displaye d in bits (or Kilobits, e tc ...) and an am ount of
data is displaye d in byte s (or Kilobyte s, e tc ...).
As a re m inde r, 1 byte is e qual to 8 bits and, in the com pute r scie nce world, 1 k ilo is e qual to
1024 (2^10).
For e x am ple : 100'000'000 byte s is not e qual to 100 Mbyte s but to 100'000'000/1024/1024 =
95.37 Mbyte s.
C lie nt side :
#iperf -c 10.1.1.1 -f b
------------------------------------------------------------
TCP window size: 16384 Byte (default)
------------------------------------------------------------
[ 3] 0.0-10.2 sec 1359872 Bytes 1064272 bits/sec
Se rve r side :
#iperf -s
------------------------------------------------------------
------------------------------------------------------------
[852] 0.0-10.6 sec 920 KBytes 711 Kbits/sec
Top of the page
Bi-dire ctional bandwidth m e asure m e nt: (-r argum e nt)
The Ipe rf se rve r conne cts back to the clie nt allowing the bi-dire ctional bandwidth m e asure m e nt.
By de fault, only the bandwidth from the clie nt to the se rve r is m e asure d.
If you want to m e asure the bi-dire ctional bandwidth sim ultane ously, use the -d k e yword. (Se e
ne x t te st.)
C lie nt side :
#iperf -c 10.1.1.1 -r
------------------------------------------------------------
------------------------------------------------------------
------------------------------------------------------------
------------------------------------------------------------
[ 5] 0.0-10.0 sec 1.12 MBytes 936 Kbits/sec
Se rve r side :
#iperf -s
------------------------------------------------------------
------------------------------------------------------------
[852] 0.0-10.1 sec 1.15 MBytes 956 Kbits/sec
------------------------------------------------------------
------------------------------------------------------------
Top of the page
Sim ultane ous bi-dire ctional bandwidth m e asure m e nt: (-d argum e nt)
Also che ck the "Jpe rf" se ction.
To m e asure the bi-dire ctional bandwidths sim ultane ouse ly, use the -d argum e nt. If you want to
te st the bandwidths se que ntially, use the -r argum e nt (se e pre vious te st).
By de fault (ie : without the -r or -d argum e nts), only the bandwidth from the clie nt to the se rve r
is m e asure d.
C lie nt side :
#iperf -c 10.1.1.1 -d
------------------------------------------------------------
------------------------------------------------------------
------------------------------------------------------------
------------------------------------------------------------
Se rve r side :
#iperf -s
------------------------------------------------------------
------------------------------------------------------------
------------------------------------------------------------
------------------------------------------------------------
Top of the page
TC P W indow size : (-w argum e nt)
The TC P window size is the am ount of data that can be buffe re d during a conne ction without a
validation from the re ce ive r.
It can be be twe e n 2 and 65,535 byte s.
O n Linux syste m s, whe n spe cifying a TC P buffe r size with the -w argum e nt, the k e rne l allocate s
double as m uch as indicate d.
C lie nt side :
#iperf -c 10.1.1.1 -w 2000
WARNING: TCP window size set to 2000 bytes. A small window size
will give poor performance. See the Iperf documentation.
------------------------------------------------------------
TCP window size: 3.91 KByte (WARNING: requested 1.95 KByte)
------------------------------------------------------------
[ 3] 0.0-10.1 sec 704 KBytes 572 Kbits/sec
Se rve r side :
#iperf -s -w 4000
------------------------------------------------------------
TCP window size: 3.91 KByte
------------------------------------------------------------
[852] 0.0-10.1 sec 704 KBytes 570 Kbits/sec
Top of the page
C om m unication port (-p), tim ing (-t) and inte rval (-i):
The Ipe rf se rve r com m unication port can be change d with the -p argum e nt. It m ust be
configure d on the clie nt and the se rve r with the sam e value , de fault is TC P port 5001.
The -t argum e nt spe cifie s the te st duration tim e in se conds, de fault is 10 se cs.
The -i argum e nt indicate s the inte rval in se conds be twe e n pe riodic bandwidth re ports.
C lie nt side :
#iperf -c 10.1.1.1 -p 12000 -t 20 -i 2
------------------------------------------------------------
------------------------------------------------------------
[ 3] 0.0- 2.0 sec 224 KBytes 918 Kbits/sec
[ 3] 2.0- 4.0 sec 368 KBytes 1.51 Mbits/sec
[ 3] 10.0-12.0 sec 344 KBytes 1.41 Mbits/sec
[ 3] 18.0-20.0 sec 264 KBytes 1.08 Mbits/sec
Se rve r side :
#iperf -s -p 12000
------------------------------------------------------------
------------------------------------------------------------
Top of the page
UDP te sts: (-u), bandwidth se ttings (-b)

Also che ck the "Jpe rf" se ction.
The UDP te sts with the -u argum e nt will give invaluable inform ation about the jitte r and the
pack e t loss. If you don't spe cify the -u argum e nt, Ipe rf use s TC P.
To k e e p a good link quality, the pack e t loss should not go ove r 1 %. A high pack e t loss rate will
ge ne rate a lot of TC P se gm e nt re transm issions which will affe ct the bandwidth.
The jitte r is basically the late ncy variation and doe s not de pe nd on the late ncy. You can have
high re sponse tim e s and a ve ry low jitte r. The jitte r value is particularly im portant on ne twork
link s supporting voice ove r IP (VoIP) be cause a high jitte r can bre ak a call.
The -b argum e nt allows the allocation if the de sire d bandwidth.
C lie nt side :
#iperf -c 10.1.1.1 -u -b 10m
------------------------------------------------------------
Client connecting to 10.1.1.1, UDP port 5001
Sending 1470 byte datagrams
UDP buffer size: 108 KByte (default)
------------------------------------------------------------
[ 3] Sent 8409 datagrams
[ 3] Server Report:
[ 3] 0.0-10.0 sec 11.8 MBytes 9.86 Mbits/sec 2.617 ms 9/ 8409 (0.11%)
Se rve r side :
#iperf -s -u -i 1
------------------------------------------------------------
Server listening on UDP port 5001
Receiving 1470 byte datagrams
UDP buffer size: 8.00 KByte (default)
------------------------------------------------------------
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[904] 0.0- 1.0 sec 1.17 MBytes 9.84 Mbits/sec 1.830 ms 0/ 837 (0%)
[904] 1.0- 2.0 sec 1.18 MBytes 9.94 Mbits/sec 1.846 ms 5/ 850 (0.59%)
[904] 9.0-10.0 sec 1.19 MBytes 10.0 Mbits/sec 1.801 ms 0/ 851 (0%)
[904] 0.0-10.0 sec 11.8 MBytes 9.86 Mbits/sec 2.618 ms 9/ 8409 (0.11%)
Top of the page
Max im um Se gm e nt Size (-m argum e nt) display:
The Max im um Se gm e nt Size (MSS) is the large st am ount of data, in byte s, that a com pute r can
support in a single , unfragm e nte d TC P se gm e nt.
It can be calculate d as follows:
MSS = MTU - TC P & IP he ade rs
The TC P & IP he ade rs are e qual to 40 byte s.
The MTU or Max im um Transm ission Unit is the gre ate st am ount of data that can be transfe rre d
in a fram e .
He re are som e de fault MTU size for diffe re nt ne twork topology:
Ethe rne t - 1500 byte s: use d in a LAN.
PPPoE - 1492 byte s: use d on ADSL link s.
Tok e n R ing (16Mb/se c) - 17914 byte s: old te chnology de ve lope d by IBM.
Dial-up - 576 byte s
Ge ne rally, a highe r MTU (and MSS) brings highe r bandwidth e fficie ncy
C lie nt side :
#iperf -c 10.1.1.1 -m
------------------------------------------------------------
------------------------------------------------------------
[ 3] MSS size 1448 bytes (MTU 1500 bytes, ethernet)
He re the MSS is not e qual to 1500 - 40 but to 1500 - 40 - 12 (Tim e stam ps option) = 1448
Se rve r side :
#iperf -s
Top of the page
Max im um Se gm e nt Size (-M argum e nt) se ttings:
Use the -M argum e nt to change the MSS. (Se e the pre vious te st for m ore e x planations about
the MSS)
#iperf -c 10.1.1.1 -M 1300 -m
WARNING: attempt to set TCP maximum segment size to 1300, but got 536
------------------------------------------------------------
------------------------------------------------------------
[ 3] MSS size 1288 bytes (MTU 1328 bytes, unknown interface)
Se rve r side :
#iperf -s
Top of the page
Paralle l te sts (-P argum e nt):
Use the -P argum e nt to run paralle l te sts.
C lie nt side :
#iperf -c 10.1.1.1 -P 2
------------------------------------------------------------
------------------------------------------------------------
[SUM] 0.0-10.1 sec 2.70 MBytes 2.24 Mbits/sec
Se rve r side :
#iperf -s
Top of the page
Ipe rf he lp:
#iperf -h
Usage: iperf [-s|-c host] [options]

iperf [-h|--help] [-v|--version]
Client/Server:
-f --format [kmKM] format to report: Kbits, Mbits, KBytes, MBytes
-i --interval # seconds between periodic bandwidth reports
-l --len #[KM] length of buffer to read or write (default 8 KB)
-m --print_mss print TCP maximum segment size (MTU - TCP/IP header)
-p --port # server port to listen on/connect to
-u --udp use UDP rather than TCP
-w --window #[KM] TCP window size (socket buffer size)
-B --bind "host" bind to "host", an interface or multicast address
-C --compatibility for use with older versions does not sent extra msgs
-M --mss # set TCP maximum segment size (MTU - 40 bytes)
-N --nodelay set TCP no delay, disabling Nagle's Algorithm
-V --IPv6Version Set the domain to IPv6
Server specific:
-s --server run in server mode
-U --single_udp run in single threaded UDP mode
-D --daemon run the server as a daemon
Client specific:
-b --bandwidth #[KM] for UDP, bandwidth to send at in bits/sec (default 1 Mbit/sec, implies -u)
-c --client "host" run in client mode, connecting to "host"
-d --dualtest Do a bidirectional test simultaneously
-n --num #[KM] number of bytes to transmit (instead of -t)
-r --tradeoff Do a bidirectional test individually
-t --time # time in seconds to transmit for (default 10 secs)
-F --fileinput "name" input the data to be transmitted from a file
-I --stdin input the data to be transmitted from stdin
-L --listenport # port to recieve bidirectional tests back on
-P --parallel # number of parallel client threads to run
-T --ttl # time-to-live, for multicast (default 1)
Miscellaneous:
-h --help print this message and quit
-v --version print version information and quit
Top of the page
JPER F
Jpe rf is a graphical fronte nd for Ipe rf writte n in Java.
1. Installation:
Download Jpe rf.
Linux
Uncom pre ss the downloade d file :
#tar -xvf jperf2.0.0.zip
Launch Jpe rf.
#cd jperf2.0.0
#./jperf.sh
If you have the following m e ssage , it m e ans that you ne e d to install Ipe rf with: "apt-ge t install
ipe rf"
Iperf is probably not in your Path!

Please download it here 'http://dast.nlanr.net/Projects/Iperf/'
and put the executable in your PATH environment variable.
Microsoft W indows
Uncom pre ss the downloade d file with your favorite program .

Acce ss the uncom pre sse d folde r calle d by de fault "jpe rf2.0.0" and double -click on "jpe rf.bat".
Note that the ipe rf utility is alre ady pre se nt in the /bin folde r.
2. Ex am ple s:
De fault se ttings, bandwidth m e asure m e nt:

Also che ck "Ipe rf" se ction for m ore de tails.
- Linux clie nt:
- W indows se rve r:
Top of the page Jpe rf
Sim ultane ous bi-dire ctional bandwidth m e asure m e nt:

- Linux clie nt:
Jitte r m e asure m e nt:

- Linux clie nt:
If you lik e d our tutorials, don't he sitate to support us and visit our sponsors!
Si vous aim e z nos tutoriaux , n'hé site z pas à nous supporte r e t visite r nos sponsors!

Iperf Ejemplos

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Iperf Ejemplos

Încărcat de

Drepturi de autor:

Formate disponibile

08/10/14 IPERF - The Easy Tutorial

Ne twork ing Ipe rf

Settings Measurements Diagram Diamond wedding ring sets He lp us translate

no arg. De fault se ttings

De fault Ipe rf se ttings:

Data form atting: (-f argum e nt)

Top of the page

Bi-dire ctional bandwidth m e asure m e nt: (-r argum e nt)

Top of the page

Top of the page

TC P W indow size : (-w argum e nt)

#iperf -c 10.1.1.1 -w 2000

Top of the page

#iperf -c 10.1.1.1 -p 12000 -t 20 -i 2

Top of the page

UDP te sts: (-u), bandwidth se ttings (-b)

#iperf -c 10.1.1.1 -u -b 10m

Top of the page

Max im um Se gm e nt Size (-m argum e nt) display:

Top of the page

Max im um Se gm e nt Size (-M argum e nt) se ttings:

#iperf -c 10.1.1.1 -M 1300 -m

Top of the page

Paralle l te sts (-P argum e nt):

Use the -P argum e nt to run paralle l te sts.

Top of the page

Usage: iperf [-s|-c host] [options]

Top of the page

Jpe rf is a graphical fronte nd for Ipe rf writte n in Java.

Download Jpe rf.

Uncom pre ss the downloade d file :

#tar -xvf jperf2.0.0.zip

Launch Jpe rf.

Iperf is probably not in your Path!

Uncom pre ss the downloade d file with your favorite program .

De fault se ttings, bandwidth m e asure m e nt:

- Linux clie nt:

Top of the page Jpe rf

Sim ultane ous bi-dire ctional bandwidth m e asure m e nt:

- Linux clie nt:

Top of the page Jpe rf

Jitte r m e asure m e nt:

- Linux clie nt:

Top of the page Jpe rf

S-ar putea să vă placă și