-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' into output-json-stream
- Loading branch information
Showing
74 changed files
with
11,778 additions
and
6,898 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -14,19 +14,20 @@ FreeBSD, and macOS. Support may be provided on a best-effort basis to | |
other UNIX-like platforms. We cannot provide support for building | ||
and/or running iperf3 on Windows, iOS, or Android. | ||
|
||
Before asking for help, please use your favorite search engine or | ||
questions site (such as Stack Overflow) to see if your question might | ||
have been asked (and maybe even answered) before. | ||
https://fasterdata.es.net/ has some information on the use of various | ||
bandwidth measurement tools, including iperf3. The iperf3 | ||
documentation Web site at http://software.es.net/iperf/ contains | ||
various bits of helpful information, including a list of | ||
Before asking for help, please check with your favorite search engine | ||
or the | ||
[iperf3 Discussions site on GitHub](http://github.com/esnet/iperf/discussions) | ||
to see if your question might have been asked (and maybe even | ||
answered) before. https://fasterdata.es.net/ has some information on | ||
the use of various bandwidth measurement tools, including iperf3. The | ||
iperf3 documentation Web site at http://software.es.net/iperf/ | ||
contains various bits of helpful information, including a list of | ||
[frequently-asked questions](http://software.es.net/iperf/faq.html). | ||
|
||
We specifically discourage the use of the issue tracker on the iperf3 | ||
GitHub project page for asking questions. Questions posted in the | ||
form of issues may go unanswered. Please use a questions site | ||
such as [Stack Overflow](http://www.stackoverflow.com) | ||
form of issues may go unanswered. Please use the | ||
[iperf3 Discussions site on GitHub](http://github.com/esnet/iperf/discussions) | ||
to ask questions of the community or | ||
alternatively use the iperf3 mailing list at | ||
[email protected] (posting requires joining the list). | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,10 @@ | ||
_NOTE: The iperf3 issue tracker is for registering bugs, enhancement | ||
requests, or submissions of code. It is not a means for asking | ||
questions about building or using iperf3. Those are best directed | ||
towards the iperf3 mailing list at [email protected] or | ||
question sites such as Stack Overflow | ||
(http://www.stackoverflow.com/). A list of frequently-asked questions | ||
towards the Discussions section for this project at | ||
https://github.com/esnet/iperf/discussions | ||
or to the iperf3 mailing list at [email protected]. | ||
A list of frequently-asked questions | ||
regarding iperf3 can be found at http://software.es.net/iperf/faq.html._ | ||
|
||
# Context | ||
|
@@ -23,7 +24,9 @@ iperf3 on Windows, iOS, or Android._ | |
libraries, cross-compiling, etc.): | ||
|
||
_Please fill out one of the "Bug Report" or "Enhancement Request" | ||
sections, as appropriate._ | ||
sections, as appropriate. Note that submissions of bug fixes, new | ||
features, etc. should be done as a pull request at | ||
https://github.com/esnet/iperf/pulls_ | ||
|
||
# Bug Report | ||
|
||
|
@@ -35,8 +38,6 @@ sections, as appropriate._ | |
|
||
* Possible Solution | ||
|
||
_Please submit patches or code changes as a pull request._ | ||
|
||
# Enhancement Request | ||
|
||
* Current behavior | ||
|
@@ -45,5 +46,3 @@ _Please submit patches or code changes as a pull request._ | |
|
||
* Implementation notes | ||
|
||
_If submitting a proposed implementation of an enhancement request, | ||
please use the pull request mechanism._ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
name: test | ||
on: [push, pull_request] | ||
jobs: | ||
cppcheck-test: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: actions/checkout@v3 | ||
- name: install dependencies | ||
run: | | ||
sudo apt-get -y update && sudo apt-get install -y cppcheck && \ | ||
cppcheck . --force --inline-suppr | ||
build-test-latest: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: actions/checkout@v3 | ||
- name: install dependencies | ||
run: | | ||
sudo apt-get -y update && sudo apt-get install -y build-essential | ||
- name: build | ||
run: | | ||
./configure && make && make check | ||
timeout 300 src/iperf3 -s & | ||
./test_commands.sh localhost | ||
build-test-ubuntu-20_04: | ||
runs-on: ubuntu-20.04 | ||
steps: | ||
- uses: actions/checkout@v3 | ||
- name: install dependencies | ||
run: | | ||
sudo apt-get -y update && sudo apt-get install -y build-essential | ||
- name: build | ||
run: | | ||
./configure && make && make check | ||
timeout 300 src/iperf3 -s & | ||
./test_commands.sh localhost |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -30,3 +30,4 @@ examples/.libs | |
examples/Makefile | ||
examples/mic | ||
examples/mis | ||
.vscode/ |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -18,7 +18,7 @@ such as nuttcp and netperf, but were missing from the original iperf. | |
These include, for example, a zero-copy mode and optional JSON output. | ||
Note that iperf3 is *not* backwards compatible with the original iperf. | ||
|
||
Primary development for iperf3 takes place on CentOS Linux, FreeBSD, | ||
Primary development for iperf3 takes place on Ubuntu Linux, FreeBSD, | ||
and macOS. At this time, these are the only officially supported | ||
platforms, however there have been some reports of success with | ||
OpenBSD, NetBSD, Android, Solaris, and other Linux distributions. | ||
|
@@ -30,6 +30,10 @@ For more information see: https://software.es.net/iperf | |
|
||
Source code and issue tracker: https://github.com/esnet/iperf | ||
|
||
Discussion forums: https://github.com/esnet/iperf/discussions | ||
|
||
Reporting security vulnerabilities: [email protected] | ||
|
||
Obtaining iperf3 | ||
---------------- | ||
|
||
|
@@ -60,7 +64,7 @@ Invoking iperf3 | |
iperf3 includes a manual page listing all of the command-line options. | ||
The manual page is the most up-to-date reference to the various flags and parameters. | ||
|
||
For sample command line usage, see: | ||
For sample command line usage, see: | ||
|
||
https://fasterdata.es.net/performance-testing/network-troubleshooting-tools/iperf/ | ||
|
||
|
@@ -76,8 +80,8 @@ These flags include: | |
-Z, --zerocopy use a 'zero copy' sendfile() method of sending data | ||
-A, --affinity n/n,m set CPU affinity | ||
|
||
Bug Reports | ||
----------- | ||
Bug and Security Reports | ||
------------------------ | ||
|
||
Before submitting a bug report, please make sure you're running the | ||
latest version of the code, and confirm that your issue has not | ||
|
@@ -97,36 +101,20 @@ sensitive information. | |
If you have a question about usage or about the code, please do *not* | ||
submit an issue. Please use one of the mailing lists for that. | ||
|
||
If you suspect there is a potential security issue, please contact the | ||
developers at: | ||
|
||
[email protected] | ||
|
||
Relation to iperf 2.x | ||
--------------------- | ||
|
||
Note that iperf2 is no longer being developed by its original | ||
maintainers. However, beginning in 2014, another developer began | ||
fixing bugs and enhancing functionality, and generating releases of | ||
iperf2. Both projects (as of late 2017) are currently being developed | ||
actively, but independently. The continuing iperf2 development | ||
Although iperf2 and iperf3 both measure network performance, | ||
they are not compatible with each other. | ||
The projects (as of mid-2021) are in active, but separate, development. | ||
The continuing iperf2 development | ||
project can be found at https://sourceforge.net/projects/iperf2/. | ||
|
||
iperf3 contains a number of options and functions not present in | ||
iperf2. In addition, some flags are changed from their iperf2 | ||
counterparts: | ||
|
||
-C, --linux-congestion set congestion control algorithm (Linux only) | ||
(-Z in iperf2) | ||
--bidir bidirectional testing mode | ||
(-d in iperf2) | ||
|
||
Some iperf2 options are not available in iperf3: | ||
|
||
-r, --tradeoff Do a bidirectional test individually | ||
-T, --ttl time-to-live, for multicast (default 1) | ||
-x, --reportexclude [CDMSV] exclude C(connection) D(data) M(multicast) | ||
S(settings) V(server) reports | ||
-y, --reportstyle C report as a Comma-Separated Values | ||
|
||
Also removed is the ability to set the options via environment | ||
variables. | ||
|
||
Known Issues | ||
------------ | ||
|
||
|
@@ -149,7 +137,7 @@ responsibility for the content of these pages. | |
Copyright | ||
--------- | ||
|
||
iperf, Copyright (c) 2014-2021, The Regents of the University of | ||
iperf, Copyright (c) 2014-2023, The Regents of the University of | ||
California, through Lawrence Berkeley National Laboratory (subject | ||
to receipt of any required approvals from the U.S. Dept. of | ||
Energy). All rights reserved. | ||
|
Oops, something went wrong.