# iperf mit Homebrew, apk, apt, dnf, Nix, pacman, zypper installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für iperf in AI-Agent-Workflows.

## Installation

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

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install iperf
```

  Evidenz: local Homebrew formula metadata

### Linux

- apk (92%):

```sh
sudo apk add iperf
```

  Evidenz: 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
```

  Evidenz: 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
```

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

- Nix (92%):

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

  Evidenz: 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
```

  Evidenz: 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
```

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

## Paketfakten

- **Paketschlüssel:** brew:iperf
- **Paketmanager:** Homebrew
- **Version:** 2.2.1
- **Quellzusammenfassung:** Tool to measure maximum TCP and UDP bandwidth
- **Homepage:** <https://sourceforge.net/projects/iperf2/>
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- iperf (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 2.2.1
## Projektgeschichte und Nutzung

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.

### Projektgeschichte

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.

### Adoptionsgeschichte

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.

### Wie es verwendet wird

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.

### Warum Paket-Nerds sich dafür interessieren

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.

### Zeitleiste

- 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.

### Quellen

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


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals

## Andere Paketmanager-Einträge

- 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-5.fc45: normalized package name match | Fedora Rawhide package metadata: iperf from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-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.4: normalized package name match | openSUSE Tumbleweed package metadata: iperf from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | A tool to measure network performance | https://github.com/esnet/iperf
- zypper - iperf-devel - 3.21-1.4: normalized package name match | openSUSE Tumbleweed package metadata: iperf-devel from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | A tool to measure network performance | https://github.com/esnet/iperf
- zypper - libiperf0 - 3.21-1.4: normalized package name match | openSUSE Tumbleweed package metadata: libiperf0 from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | A library to measure network performance | https://github.com/esnet/iperf


## Combined YAML source

View the package source record on GitHub. [combined/iperf.yml](https://github.com/mxcl/pkgdb/blob/main/combined/iperf.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph