Lines Matching refs:iperf3
8 * A new --repeating-payload option makes iperf3 use a payload pattern
27 * Functions related to authenticated iperf3 connections have been
36 * iperf3 no longer counts data received after the end of a test in
51 * iperf3 now builds on systems lacking a daemon(3) library call
71 ephemeral port number allocation that can make multi-stream iperf3
77 * iperf3 now builds on (some) macOS systems older than 10.7 (#607).
87 * iperf3 can now be built --without-openssl on systems where OpenSSL
101 * A bug that could cause iperf3 to overwrite the PID file of an
102 already-existing iperf3 process has been fixed (#623).
104 * iperf3 will now ignore nonsensical TCP MSS values (from the TCP
118 iperf3 server (#517).
129 * iperf3 now uses the correct "bitrate" phraseology rather than
166 data is used. Note that iperf3 now requires the /dev/urandom
169 * Prior versions of iperf3 doing UDP tests used to overcount packet
174 * iperf3 no longer prints results from very small intervals (10% of
181 * Compatiblity note: Users running iperf3 3.2 or newer from the
229 prior versions of iperf3 (through 3.1.4) due to the new default UDP
244 equivalent to --fq-rate=0. iperf3 now reacts more gracefully if
255 * iperf3 now chooses a more sane default UDP send size (#496, #498).
260 iperf3 now attempts to use the MSS of the control connection to
284 iperf3 now keeps track of the congestion control algorithm and
294 the context of iperf3.
311 fixed upstream, so was addressed in iperf3 by importing a newer
318 * On supported platforms (recent Linux), iperf3 can use
328 iperf3 server will no longer exit after five consecutive errors,
399 iperf3 server in daemon mode (issue #119).
415 * A potential crash in the iperf3 server has been fixed (issue #257,
435 * Added -1 / --one-off flag, which causes the iperf3 server to
581 * The iperf3 project has been moved to GitHub, and various URLs in
584 * iperf3 now builds on Linux systems that do not support
585 TCP_CONGESTION. Most notably this allows iperf3 to work on CentOS