iperf 3.9
* Notable user-visible changes
* A --timestamps flag has been added, which prepends a timestamp to
each output line. An optional argument to this flag, which is a
format specification to strftime(3), allows for custom timestamp
formats.
* A --server-bitrate-limit flag has been added as a server-side
command-line argument. It allows a server to enforce a maximum
throughput rate; client connections that specify a higher bitrate
or exceed this bitrate during a test will be terminated. The
bitrate is expressed in bits per second, with an optional trailing
slash and integer count that specifies an averaging interval over
which to enforce the limit.
* A bug that caused increased CPU usage with the --bidir option has
been fixed.
* Notable developer-visible changes
* Fixed various minor memory leaks.
iperf 3.8.1 2020-06-10
----------------------
* Notable user-visible changes
* A regression with "make install", where the libiperf shared
library files were not getting installed, has been fixed.
iperf 3.8 2020-06-08
--------------------
* Notable user-visible changes
* Profiled libraries and binaries are no longer built by default.
* A minimal Dockerfile has been added.
* A bug with burst mode and unlimited rate has been fixed
* Configuring with the --enable-static-bin flag will now cause
a statically-linked iperf3 binary to be built.
* Configuring with the --without-sctp flag will now prevent SCTP
from being auto-detected. This flag allows building a
static binary (see above item) on a CentOS system with SCTP
installed, because no static SCTP libraries are available.
* Clock skew between the iperf3 client and server will no longer
skew the computation of jitter during UDP tests.
* A possible buffer overflow in the authentication feature has been
fixed. This was only relevant when configuration authentication
using the libiperf3 API, and did not affect command-line usage.
Various other improvements and fixes in this area were also made.
* Notable developer-visible changes
* The embedded version of cJSON has been updated to 1.3.17.
* Some server authentication functions have been added to the API.
* API access has been added to the connection timeout parameter.
* Tests for some authentication functions have been added.
* Various compiler errors and warnings have been fixed.
3.7:
iperf 3.6 adds the --bidir flag for bidirectional tests, includes some minor enhancements, and fixes a number of bugs. More details can be found in the release notes.
Note: Documentation for the --bidir flag was inadvertently omitted from the manual page. This will be fixed in a future release.
3.6:
iperf 3.6 adds the --extra-data and --repeating-payload options and fixes some minor bugs.
3.5:
iperf 3.5 fixes a bug that could over-count data transfers (and hence measured bitrate).
3.4:
iperf 3.4 fixes a number of minor bugs and adds a few enhancements.
3.3:
New minor release of iperf 3.3, fixing a number of minor bugs.
3.2:
New minor release of iperf 3.2, with new features, bugfixes, and enhancements.
fixes and new functionality, made since iperf 3.1.5.
* User-visible changes
* Specifying --fq-rate or --no-fq-socket-pacing on a system where
these options are not supported now generate an error instead of a
warning. This change makes diagnosing issues related to pacing
more apparent.
* Fixed a bug where two recently-added diagnostic messages spammed
the JSON output on UDP tests.
congestion window on each test interval.
Also fix the FreeBSD version to do the same (wrong variable
in the tcp_info struct was used...).
Bump PKGREVISION.
Iperf3 is a tool for active measurements of the maximum achievable
bandwidth on IP networks. It supports tuning of various parameters
related to timing, protocols, and buffers. For each test it reports
the bandwidth, loss, and other parameters.
This version, sometimes referred to as iperf3, is a redesign of an
original version developed at NLANR/DAST. iperf3 is a new
implementation from scratch, with the goal of a smaller, simpler code
base, and a library version of the functionality that can be used in
other programs. Iperf3 also has a number of features found in other tools
such as nuttcp and netperf, but were missing from the original iperf.
These include, for example, a zero-copy mode and optional JSON output.
Note that iperf3 is NOT backwards compatible with the original iperf.
