pkglint -r --network --only "migrate"
As a side-effect of migrating the homepages, pkglint also fixed a few
indentations in unrelated lines. These and the new homepages have been
checked manually.
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.
