iperf · Issues· 238 open
Open on GitHubLocally synced open issues (discussions stay on GitHub)
- #2076
iperf3.21 server end stuck in ESTABLISHED state when disconnected network
Updated Sep 14, 2026 - #2072
get_results() passes 0 as max_size to JSON_read(), so a misread control-channel byte can trigger a multi-GB allocation instead of a clean error
Updated Aug 31, 2026 - #2037
Separate UDP GSO and GRO controls for Linux (--gso and --gro options)
Updated Aug 29, 2026 - #2064
dependency on cJSON?
Updated Aug 4, 2026 - #2063
iperf_parse_arguments() spuriously fails on 2nd+ call in the same process: stale i_errno from previous run's normal completion misread as new parse failure
Updated Jul 29, 2026 - #2055
UDP loss figures incorrect and self-inconsistent against pre-3.13 peers (omitted_* substitution)
Updated Jul 18, 2026 - #2060
Build failure on platforms without `<stdatomic.h>` due to use of non-standard `u_int64_t`
Updated Jul 14, 2026 - #2059
iperf 3.21: UDP server with multiple IP aliases may send replies from unexpected addresses
Updated Jul 10, 2026 - #836
Upstream receiver end intervals reporting wrong seconds value
bugUpdated Jul 2, 2026 - #2051
JSON output (-J) emits two top-level "error" keys on server-relayed errors
Updated Jul 2, 2026 - #510
DSCP bit appearing in different frame in iperf2 and iperf3-current
Help Wantedbug:tosUpdated Jun 10, 2026 - #748
iperf3 client does NOT report cpu_utilization_percent to server
enhancementUpdated Jun 7, 2026 - #768
iperf3 3.5 TCP option -n not working
bugbug:test-dataUpdated Jun 5, 2026 - #2036
iperf3 server does not honour the bind command for sending data - sends from incorrect interface
Updated May 20, 2026 - #1986
Server hangs endlessly (0.00 Mbits/sec) on sudden client disconnect – Works in 3.14, broken in 3.16+
Updated May 16, 2026