# Install iperf with Homebrew, apk, apt, dnf, Nix, pacman, zypper

Tool to measure maximum TCP and UDP bandwidth. Version 2.2.1 via Homebrew; verified from local package data.

## Install

```sh
sudo av install brew:iperf
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install iperf
```

  Evidence: local Homebrew formula metadata

### Linux

- apk (92%):

```sh
sudo apk add iperf
```

  Evidence: Alpine Linux edge package indexes: iperf from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz

- Debian apt (92%):

```sh
sudo apt install iperf
```

  Evidence: Debian stable package indexes: iperf from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz

- dnf (92%):

```sh
sudo dnf install iperf
```

  Evidence: Fedora Rawhide package metadata: iperf from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/e5ca8ce900cd68f5419e1c39ae517343100b306336cbaeb70a3c153121d95094-primary.xml.zst

- Nix (92%):

```sh
nix profile install nixpkgs#iperf
```

  Evidence: nixpkgs package indexes: iperf from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix

- pacman (92%):

```sh
sudo pacman -S iperf
```

  Evidence: Arch Linux sync databases: iperf from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

- zypper (92%):

```sh
sudo zypper install iperf
```

  Evidence: openSUSE Tumbleweed package metadata: iperf from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst

## Package facts

- **Package key:** brew:iperf
- **Package manager:** Homebrew
- **Package manager page:** <https://formulae.brew.sh/formula/iperf>
- **Version:** 2.2.1
- **Source summary:** Tool to measure maximum TCP and UDP bandwidth
- **Homepage:** <https://sourceforge.net/projects/iperf2/>
- **Repository:** <https://sourceforge.net/p/iperf2/code>
- **Upstream docs:** <https://iperf2.sourceforge.io/IperfCompare.html>
- **License:** BSD-3-Clause
- **Source archive:** <https://downloads.sourceforge.net/project/iperf2/iperf-2.2.1.tar.gz>
- **Generated:** 2026-07-08T18:08:21+00:00

## Executables

- iperf (cli)
- iperf (alias)

## Install behavior

- Post-install hook: not defined
- Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux

## Freshness

- Page generated: 2026-07-08
- Package-manager version: 2.2.1
- Local data: ok
- Upstream repository: https://sourceforge.net/projects/iperf2/
- info: No package-manager update timestamp was available.
- info: Release/tag comparison is only available for GitHub repositories.
## Project history and usage

Iperf 2 is the maintained version of the original iperf line, a command-line network test tool for measuring TCP and UDP throughput, latency, jitter, packet loss, and related socket-level behavior.

### Project history

The iperf family began as an NLANR/DAST tool for measuring maximum TCP and UDP bandwidth. The SourceForge iperf2 project preserves that lineage while making clear that version 2 is maintained separately from the original developers and from ESnet's iperf3 rewrite.

The iperf2 documentation emphasizes continued divergence from iperf3: both tools measure network performance, but they do not interoperate and have different feature sets. Iperf 2 retained the traditional `iperf` command name, the classic client/server model, and a broad set of traffic-shaping and reporting options.

### Adoption history

Iperf 2 became a standard Unix package because it gives operators a small, scriptable way to create repeatable traffic between two hosts. Its availability in Homebrew and common Linux package managers reflects that role as a baseline troubleshooting tool rather than an application framework.

After iperf3 appeared, iperf2 kept a distinct user base around features such as multicast, CSV-style output, TCP and UDP latency measurements, full-duplex traffic, port ranges, and large parallel tests.

### How it is used

Typical use is split between a receiver started with `iperf -s` and a sender started with `iperf -c host`, with options selecting TCP or UDP, target bandwidth, test duration, reporting interval, parallelism, and enhanced measurements.

Package users tend to reach for iperf2 when they need the traditional `iperf` executable, compatibility with existing scripts, or iperf2-only features documented in the comparison table.

### Why package nerds care

For package maintainers, `iperf` is the old-name counterpart to `iperf3`: both are useful, both are active, and the executable names intentionally differ so they can coexist. That split is why Homebrew's `iperf` formula maps to Iperf 2 rather than ESnet iperf3.

The package is a good example of a long-lived networking utility whose version line matters more than the generic project name. Choosing `iperf` versus `iperf3` changes protocol compatibility, output format, and feature coverage.

### Timeline

- NLANR/DAST era: Original iperf created as a modern TCP and UDP bandwidth measurement tool.
- SourceForge era: Iperf 2 continued as the maintained version of the original iperf line.
- 2026: Iperf 2 documentation describes the 2.2.2 comparison point with iperf3 and lists both projects as active but independent.

### Related projects

- iperf3 is ESnet's separate rewrite and does not interoperate with Iperf 2.
- nuttcp and netperf occupy nearby network benchmarking territory and are referenced by iperf3 documentation as related tools.

### Sources

- <https://iperf2.sourceforge.io/IperfCompare.html>
- <https://iperf2.sourceforge.io/iperf-manpage.html>
- <https://sourceforge.net/projects/iperf2/>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals

## Source Database Details

- **Source Database:** Homebrew formula API
- **Tap:** homebrew/core
- **Full Name:** iperf
- **Version Scheme:** 0
- **Revision:** 0
- **Bottle Stable Root URL:** <https://ghcr.io/v2/homebrew/core>
- **Deprecated:** no
- **Disabled:** no
- **Keg Only:** no
- **URL Keys:** stable

## Other Package-Manager Records

- Debian apt - iperf - 2.2.1+dfsg-1: normalized package name match | Debian stable package indexes: iperf from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | Internet Protocol bandwidth measuring tool | https://sourceforge.net/projects/iperf2/
- Nix - iperf: normalized package name match | nixpkgs package indexes: iperf from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix
- Ubuntu apt - iperf - 2.1.9+dfsg-1: normalized package name match | Ubuntu 24.04 LTS package indexes: iperf from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Internet Protocol bandwidth measuring tool | https://sourceforge.net/projects/iperf2/
- apk - iperf - 2.2.1-r0: normalized package name match | Alpine Linux edge package indexes: iperf from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | A tool to measure IP bandwidth using UDP or TCP | https://sourceforge.net/projects/iperf2/
- apk - iperf-doc - 2.2.1-r0: normalized package name match | Alpine Linux edge package indexes: iperf-doc from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | A tool to measure IP bandwidth using UDP or TCP (documentation) | https://sourceforge.net/projects/iperf2/
- apk - iperf-openrc - 2.2.1-r0: normalized package name match | Alpine Linux edge package indexes: iperf-openrc from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | A tool to measure IP bandwidth using UDP or TCP (OpenRC init scripts) | https://sourceforge.net/projects/iperf2/
- dnf - iperf - 2.2.1-4.fc44: normalized package name match | Fedora Rawhide package metadata: iperf from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/e5ca8ce900cd68f5419e1c39ae517343100b306336cbaeb70a3c153121d95094-primary.xml.zst | Measurement tool for TCP/UDP bandwidth performance | http://sourceforge.net/projects/iperf2
- pacman - iperf - 2.2.1-2: normalized package name match | Arch Linux sync databases: iperf from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | A tool to measure maximum TCP bandwidth | https://sourceforge.net/projects/iperf2/
- zypper - iperf - 3.21-1.2: normalized package name match | openSUSE Tumbleweed package metadata: iperf from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst | A tool to measure network performance | https://github.com/esnet/iperf
- zypper - iperf-devel - 3.21-1.2: normalized package name match | openSUSE Tumbleweed package metadata: iperf-devel from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst | A tool to measure network performance | https://github.com/esnet/iperf
- zypper - libiperf0 - 3.21-1.2: normalized package name match | openSUSE Tumbleweed package metadata: libiperf0 from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst | A library to measure network performance | https://github.com/esnet/iperf


## Related links

- [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata.
- [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata.
- [Homebrew utility packages](https://www.automicvault.com/pkg/brew-utility-packages/) - Matched Homebrew package provider.
- [iperf3](https://www.automicvault.com/pkg/brew/iperf3/) - Package name indicates the same formula family.
- [nuttcp](https://www.automicvault.com/pkg/brew/nuttcp/) - Shares av.db curated category or tags: cli, networking, performance-testing, tcp, throughput.
- [flowgrind](https://www.automicvault.com/pkg/brew/flowgrind/) - Shares av.db curated category or tags: cli, networking, performance-testing, tcp.
- [thrulay](https://www.automicvault.com/pkg/brew/thrulay/) - Shares av.db curated category or tags: cli, networking, tcp, throughput, udp.
- [ip_relay](https://www.automicvault.com/pkg/brew/ip-relay/) - Shares av.db curated category or tags: bandwidth, cli, networking, tcp.
- [netcat](https://www.automicvault.com/pkg/brew/netcat/) - Shares av.db curated category or tags: cli, networking, tcp, udp.
- [speedbump](https://www.automicvault.com/pkg/brew/speedbump/) - Shares av.db curated category or tags: cli, latency, networking, tcp.
- [stone](https://www.automicvault.com/pkg/brew/stone/) - Shares av.db curated category or tags: cli, networking, tcp, udp.

## Combined YAML source

View the package source record on GitHub. [combined/iperf.yml](https://github.com/automic-vault/db/blob/main/combined/iperf.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- package-page enrichment
- curated package history
- package version freshness
- av.db category and tag curation
- package relationship graph
- external package-manager database matches
- cross-ecosystem install command graph
