uwsys.net runs IPERF3 servers in madison and milwaukee 

madison     = [iperf-1.uwsys.net].  
milwaukee = [iperf-2.uwsys.net].  

iperf lists on v4/v6 udp/tcp on port 5001

TCP vs UDP testing

Iperf uses TCP by default. TCP has built in congestion avoidance. If TCP detects any packet loss, it assumes that the link capacity has been reached, and it slows down. This works very well, unless there is packet loss caused by something other than congestion. If there is packet loss due to errors, TCP will back off even if there is plenty of capacity. iperf allows TCP to send as fast as it can, which generally works to fill a clean, low latency link with packets. If a path is not clean/error free or has high latency, TCP will have a difficult time filling it. For testing higher capacity links and for links with higher latency, you will want to adjust the window size (-w option). See the KB article on TCP performance for more background.

By using the -u option, you have told iperf to use UDP packets, rather than TCP. UDP has no built in congestion avoidance, and iperf doesn't implement it either. When doing a UDP test, iperf requires that the bandwidth of the test be specified. If it isn't, it defaults to 1Mb/s. You can use the -b option to specify bandwidth to test. iperf will then send packets at the request rate for the requested period of time. The other end measures how many packets are received vs how many were sent and reports its results.

Keywords:IPERF   Doc ID:41947
Owner:Michael H.Group:University of Wisconsin System Network
Created:2014-07-17 12:16 CDTUpdated:2019-04-18 09:04 CDT
Sites:University of Wisconsin System Network
Feedback:  1   0