Iperf Example

As you might expect, running iperf in UDP mode only generates traffic in one direction (other than the server report packet, which is a single UDP packet at the end of the test). In this example, using iperf 2.0.2 (Threads), note the counting error - iperf reports only 3 datagrams sent and received whereas in fact there were 4 test packets.

Client-side console

Running a UDP test, date rate 10kbps, duration 2 seconds, to port 5003
[admin@mp1.fra.de.geant2.net ~]$iperf -c mp1.mil.it.geant2.net -u -b 10k -t 2 -p 5003
------------------------------------------------------------
Client connecting to mp1.mil.it.geant2.net, UDP port 5003
Sending 1470 byte datagrams
UDP buffer size:   105 KByte (default)
------------------------------------------------------------
[  3] local 62.40.122.10 port 53255 connected with 62.40.122.19 port 5003
[  3]  0.0- 3.0 sec  4.31 KBytes  11.8 Kbits/sec
[  3] Sent 3 datagrams
[  3] Server Report:
[  3]  0.0- 3.0 sec  4.31 KBytes  11.8 Kbits/sec  0.002 ms    0/    3 (0%)

Client-side tcpdump

[admin@mp1.fra.de.geant2.net ~]$tcpdump host mp1.mil.it.geant2.net
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
11:57:42.112605 IP ge0-vlan71.srv3.fra.de.geant2.net.53255 > fe0-vlan71.srv3.mil.it.geant2.net.5003: UDP, length 1470
11:57:43.112885 IP ge0-vlan71.srv3.fra.de.geant2.net.53255 > fe0-vlan71.srv3.mil.it.geant2.net.5003: UDP, length 1470
11:57:44.112618 IP ge0-vlan71.srv3.fra.de.geant2.net.53255 > fe0-vlan71.srv3.mil.it.geant2.net.5003: UDP, length 1470
11:57:45.112618 IP ge0-vlan71.srv3.fra.de.geant2.net.53255 > fe0-vlan71.srv3.mil.it.geant2.net.5003: UDP, length 1470
11:57:45.146464 IP fe0-vlan71.srv3.mil.it.geant2.net.5003 > ge0-vlan71.srv3.fra.de.geant2.net.53255: UDP, length 1470

Server-side console

------------------------------------------------------------
Server listening on UDP port 5003
Receiving 1470 byte datagrams
UDP buffer size:   105 KByte (default)
------------------------------------------------------------
[  3] local 62.40.122.19 port 5003 connected with 62.40.122.10 port 53255
[  3]  0.0- 3.0 sec  4.31 KBytes  11.8 Kbits/sec  0.003 ms    0/    3 (0%)

Server-side tcpdump

[admin@mp1.mil.it.geant2.net ~]$tcpdump host mp1.fra.de.geant2.net
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
11:57:42.126242 IP ge0-vlan71.srv3.fra.de.geant2.net.53255 > fe0-vlan71.srv3.mil.it.geant2.net.5003: UDP, length 1470
11:57:43.126508 IP ge0-vlan71.srv3.fra.de.geant2.net.53255 > fe0-vlan71.srv3.mil.it.geant2.net.5003: UDP, length 1470
11:57:44.126273 IP ge0-vlan71.srv3.fra.de.geant2.net.53255 > fe0-vlan71.srv3.mil.it.geant2.net.5003: UDP, length 1470
11:57:45.126290 IP ge0-vlan71.srv3.fra.de.geant2.net.53255 > fe0-vlan71.srv3.mil.it.geant2.net.5003: UDP, length 1470
11:57:45.132785 IP fe0-vlan71.srv3.mil.it.geant2.net.5003 > ge0-vlan71.srv3.fra.de.geant2.net.53255: UDP, length 1470

-- TobyRodwell - 25 Apr 2008

Topic revision: r1 - 2008-04-25 - TobyRodwell
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2004-2009 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.