Age | Commit message (Collapse) | Author |
|
Towards #600.
|
|
|
|
|
|
Follow-up commit to #712 / #713.
|
|
Fixes #712. A subsequent commit will add some information to the libiperf manual page.
|
|
Also fix some RST formatting and add some text on FreeBSD TCP
congestion control algorithms.
Fixes #410.
|
|
Fixes #728.
|
|
This option simulates payload in iperf2, which is just repetitive pattern
(ASCII '0..9' repeating), as opposed to iperf3 where payload is random.
It might help in testing and reveal problems in networking gear with hardware
compression (including WiFi access points), where iperf2 and iperf3 perform
differently, just based on payload entropy.
|
|
|
|
Fixes #709.
|
|
Got the following error when running server side with -B option:
Server side:
./iperf3 -s -B <server_ipv4_address>
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
iperf3: error - unable to start stream listener: Bad file descriptor
-----------------------------------------------------------
Client side:
./iperf3 -c <server_ipv4_address> --sctp
iperf3: error - unable to start stream listener: No such file or directory
Similar fix as below for TCP:
commit eb1cfe5e162d08efdf18fa12cd6627cfdcd675a7
Author: Bruce A. Mah <bmah@es.net>
Date: Fri Aug 1 16:24:14 2014 -0700
Another iteration on issue #193, fixes -B with some TCP tests.
Signed-off-by: Jianwen Ji <jijianwen@gmail.com>
|
|
* Add ToS byte to iperf API
* Add function prototype to manual page
|
|
Add htonll/ntohll if not defined
|
|
|
|
|
|
Part of #707.
|
|
|
|
Towards #707.
|
|
|
|
Don't count data for tests received after the end of a test.
This prevents is from reporting an incorrect number of bytes
received at the end of the test, which doesn't match up with the
sum of the data received during the test intervals.
Log late receives if debugging mode enabled.
Fixes #692.
|
|
Fixes #701.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A few whitespace fixes in here too.
|
|
This commit also adds SCTP support for --cport.
Fixes #616.
|
|
(not yet scheduled but likely "soon").
|
|
connections. (#696)
This was caused by a stale / invalid pointer reference that didn't even
make any sense in context anyway. Fixes #686.
|
|
No effect on JSON format output or output to a file.
Submitted by @cygnus2048, fixes #688.
|
|
This can happen with multiple parallel streams or with two single
stream tests run close together in time.
The fix is to allow flow labels to be reused by multiple sockets
simultaneously or within their timeout.
Submitted by @cygnus2048 and fixes #689.
|
|
Might be useful for other platforms as well (no effects on Linux
because the semantics of listen(2) are subtly different there).
Submitted by Matt Macy. Fixes #691.
|
|
(#682)
The user-visible symptom was messages of the following form on the
server:
iperf3: the client has unexpectedly closed the connection
This bug was introduced in #597 and was present in iperf 3.2 and 3.3.
Fixes #677.
|
|
Required to avoid implicit declarations of 'signal()' and 'time()'; which
causes compilation to error out while compiling a statically linked binary.
|
|
Fixes #673.
Submitted by @FuzzyStatic, reviewed by @ralcini.
|
|
* The canonical long-form option name is "length", not "len".
* The default length for UDP should be displayed in bytes not KB.
|
|
Suggested by @beau-williamson in #27.
|
|
That mention points to the iperf3 FAQ, which contains information
about the history of iperf2 and iperf3, and a pointer to continued
iperf2 development. Suggested by a comment from @beau-williamson
in #27.
|
|
|
|
* Attempt to quiet a warning with print(3) formatting. As a part of this, factor out PRIu64 support / compatibility (added in #664) into a header file and make it more portable by taking into account the size of a long integer. Based on email conversation with: @pprindeville.
* Follow-up to pull request #669, fixing compiler warnings on platforms that don't have HAVE_TCP_CONGESTION defined.
|
|
Since iperf3 uses strtol() to parse these values, the user can specify
them with 0 prefix for octals and 0x for hex values.
|
|
|