Package: iperf / 2.0.5-3
Metadata
Package | Version | Patches format |
---|---|---|
iperf | 2.0.5-3 | 3.0 (quilt) |
Patch series
view the series filePatch | File delta | Description |
---|---|---|
001 cast to max_size_t instead of int.patch | (download) |
src/Settings.cpp |
2 1 + 1 - 0 ! |
iperf does not handle right large time values Reported by Eugene Butan <eugene@mikrotik.com> When I invoke 'iperf' with '-t 100000000' argument from an ordinary shell prompt it immediately exits displaying incorrect bandwidth. If I supply smaller time value, iperf works as expected. |
002 typo recieve.patch | (download) |
man/iperf.1 |
2 1 + 1 - 0 ! |
fix receive typo |
003 fix hyphen used as minus sign.patch | (download) |
man/iperf.1 |
78 39 + 39 - 0 ! |
fix hyphen used as minus sign in manpages |
005 iperf die on bind fail.patch | (download) |
src/Listener.cpp |
2 1 + 1 - 0 ! |
iperf die on bind fail When iperf encounters a fatal error when binding to a port, such as the port being already in use or lacking permission, it fails to give fatal error, but instead pretends to continue to listen on the port. |
006 bidirectional tcp server.patch | (download) |
src/Client.cpp |
2 2 + 0 - 0 ! |
fix bidirectional tcp server exiting after the test iperf bidirectional test using parameter -r or -d doesn't work as expected, the server exits after the test, but it should continue listening for new connections. |
010 fix format security ftbfs.patch | (download) |
compat/Thread.c |
2 1 + 1 - 0 ! |
iperf format string ftbfs with -werror=format-security Reported by Didier Raboud <odyx@debian.org> |
011 ipv6_mcast_check.patch | (download) |
src/PerfSocket.cpp |
2 1 + 1 - 0 ! |
fix improper check for ipv6 family when sending multicast This patch fixes the proper behavior of -T (hop-limit setting) when sending IPv6 multicast packets. Due to this bug, it was always fixed to 1. . SetSocketOptions() is called before socket connection, thus sa_family is still set to 0. This is causing the if-branch in the multicast check to always assume a non-IPv6 socket. Checking the remote-peer family works reliably, instead. |