macOS
brew install iperf3provider-native install command
brew / rank 497
Update of iperf: measures TCP, UDP, and SCTP bandwidth. Version 3.21 via Homebrew; verified 2026-06-22.
install
brew install iperf3provider-native install command
overview
Update of iperf: measures TCP, UDP, and SCTP bandwidth
history
iperf3 is ESnet and Lawrence Berkeley National Laboratory's redesigned iperf implementation for active measurement of achievable bandwidth on IP networks, adding a smaller code base, library use, SCTP support, zero-copy mode, and JSON output.
iperf3 was built as a clean rewrite of the original NLANR/DAST iperf. Its README says it shares the measurement domain with iperf2 but is not backward compatible, which made the separate `iperf3` executable and package name necessary.
The project is developed by ESnet/Lawrence Berkeley National Laboratory and distributed under a three-clause BSD license. ESnet's download archive shows public 3.0.x tarballs in 2014, while the GitHub repository was created in February 2014.
The README identifies perfSONAR as one of iperf3's primary uses and notes use by ESnet, other research and education networks, the broader networking community, and commercial products.
Package adoption is broad because the tool gives automation-friendly output and a stable `iperf3` command without colliding with legacy iperf2 installations. Homebrew, Linux distributions, Windows package managers, and other ecosystems ship it under the iperf3 name.
The basic workflow remains the classic iperf model: run a server endpoint, run a client against it, select protocol and timing parameters, and read bandwidth, loss, and related measurements.
The package is especially useful in scripted diagnostics because iperf3 offers JSON output, explicit client/server compatibility with other iperf3 builds, and documented behavior around supported platforms and known issues.
iperf3 matters because it is not just a version bump of `iperf`: it is a parallel implementation with its own ABI, CLI behavior, output formats, and release train. Package managers preserve that distinction by shipping `iperf` and `iperf3` separately.
For network engineers, the package is part of the small toolkit used to turn vague throughput complaints into repeatable measurements. For maintainers, it is a canonical example of a command-line tool whose packaging name encodes compatibility.
security posture
narrow executable package without higher-risk signals.
green risk · low confidence · appliance
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
iperf3 | executable | indexed executable | Discovered from the local executable index. |
freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
install metadata
| Package key | brew:iperf3 |
|---|---|
| Version | 3.21 |
| Package manager | Homebrew |
| Homepage | https://github.com/esnet/iperf |
| Repository | https://github.com/esnet/iperf |
| Last updated | 2026-06-22T14:03:47-07:00 |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source trail
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
View the package source record on GitHub.