If you configure iPerf with LANconfig, the iPerf function remains permanently active. You can optionally start a temporary iPerf daemon, which remains active for just one test, by using SSH to connect to the command-line console.
To do this, start a terminal program (e.g. PuTTY) and open a connection to the device where you want to perform the iPerf test. Use the console command iperf and the appropriate option switches to start the temporary iPerf daemon. The following examples illustrate some standard commands.
Note: More information about the option switches for iperf is available in the section Commands for the console.
- Running the iPerf server in TCP mode
root@device:/Setup/Iperf/Server-Daemon > iperf -s [Iperf-TCP-Server|1526] Now listening on port 5001
Press the Enter button again or close the console window to stop the iPerf server.- Running the iPerf server in UDP mode
root@device:/Setup/Iperf/Server-Daemon > iperf -s -u [Iperf-UDP-Server|1524] Now listening on port 5001
Press the Enter button again or close the console window to stop the iPerf server.- Running the iPerf client in UDP mode
root@device:/Setup/Iperf/Server-Daemon > iperf -u -c 172.16.30.23 WARN: Using default UPD bandwidth limitation of 1 MBit/s WARN: Using default UDP payload length of 1472 bytes (for matching Ethernet MTU via IPv4) [Iperf-UDP-Client|2100] Connecting to server... [Iperf-UDP-Client|2100] Connection established to 172.16.30.23:5001 root@device:/ >
Press the Enter key to exit the test.[Iperf-UDP-Client|2100] Connection closed actively [Iperf-UDP-Client|2100] Sent 1249728 bytes within 10s (10000ms) -> 0 Mbit/s (999 Kbit/s) [Iperf-UDP-Client|2100] Server reports 1249728 bytes received within 9s (9985ms) -> 1 Mbit/s (1001 Kbit/s) [Iperf-UDP-Client|2100] Server received 849 packets (0 lost / 0 out-of-order) with 62us jitter root@device:/ >
