Downloads:
7,071
Downloads of v 2.1.3:
33
Last Update:
01 Dec 2021
Package Maintainer(s):
Software Author(s):
- Mark Gates
- Alex Warshavsky
- Ajay Tirumala
- Jim Ferguson
- Jon Dugan
- Feng Qin
- Kevin Gibbs
- John Estabrook
- Andrew Gallatin
- Stephen Hemminger
- Nathan Jones
- Gerrit Renker
- Robert J. McMahon
- Tim Auckland
Tags:
iperf2 iperf network networking benchmarkingiPerf2
Downloads:
7,071
Downloads of v 2.1.3:
33
Maintainer(s):
Software Author(s):
- Mark Gates
- Alex Warshavsky
- Ajay Tirumala
- Jim Ferguson
- Jon Dugan
- Feng Qin
- Kevin Gibbs
- John Estabrook
- Andrew Gallatin
- Stephen Hemminger
- Nathan Jones
- Gerrit Renker
- Robert J. McMahon
- Tim Auckland
iPerf2
- 1
- 2
- 3
Some Checks Are Exempted or Have Failed
Not All Tests Have Passed
This package was rejected on 01 Dec 2021. The reviewer TheCakeIsNaOH has listed the following reason(s):
A network traffic tool for measuring TCP and UDP performance. The goals include maintaining an active iperf 2 code base (code originated from iperf 2.0.5), preserving interoperability with iperf 2.0.5 clients and servers, preserving the output for scripts (new enhanced output requires -e), adopt known 2.0.x bug fixes, maintain broad platform support, as well as add some essential feature enhancements mostly driven by WiFi testing needs. Also added python code to centralize test control.
Iperf 2 vs iperf 3 major differences: Iperf 2 here has timing related stats including end/end packet latency w/histograms (clocks assumed to be synced); supports multicast including SSM; supports threaded operation; supports L2 length checks. Iperf3 is a "cleaner" code base per a rewrite; supports json output; uses a test connection; is single threaded.
Iperf2 and iperf3 do not interoperate.
md5: 571314C3D6098D814393E51D6A2FD410 | sha1: D459422FDDDD3F5825396CFF58228878E7D86D3A | sha256: D7C701997578D4E19DC6C779CFD2DCC44AFE3C6941A4F3DCD39A9B669BB53847 | sha512: C323B63CAB5E85D35BEC82C99B5063A8EBF0A5BA61398965785E2656E5B213104B27F5A8D002C3245769ABD9D682973D54A9DE5FF61B88CD83CD2C2E8151D1C5
From: https://sourceforge.net/p/iperf2/code/ci/master/tree/doc/ui_license.html
LICENSE
<HTML>
<HEAD>
<TITLE>Iperf Copyright</TITLE>
<!-- $Id: ui_license.html,v 1.1.1.1 2004/05/18 01:50:44 kgibbs Exp $ -->
</HEAD>
<BODY BGCOLOR="#FFFFFF" LINK="#006633" VLINK="#669900" ALINK="#669966">
<CENTER>
<P><IMG SRC="dast.gif"
ALT="Distributed Applications Support Team"></P>
</CENTER>
<H1 ALIGN=CENTER>Iperf Copyright</H1>
<HR><!-- ----- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- -->
<CENTER>
Copyright (c) 1999,2000,2001,2002,2003,2004,2005 The Board of Trustees of the University of Illinois<br>
All Rights Reserved.
<P>
<a href="http://dast.nlanr.net/Projects/Iperf">Iperf performance test</a><BR>
Mark Gates<BR>
Ajay Tirumala<br>
Jim Ferguson<br>
Jon Dugan<br>
Feng Qin<br>
Kevin Gibbs<br>
John Estabrook<BR>
National Laboratory for Applied Network Research <BR>
National Center for Supercomputing Applications <BR>
University of Illinois at Urbana-Champaign <BR>
<a href="http://www.ncsa.uiuc.edu">http://www.ncsa.uiuc.edu</a>
</center>
<P>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software (Iperf)
and associated documentation files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following conditions:
<p>
<ul>
<li>Redistributions of source code must retain the above copyright notice, this list of
conditions and the following disclaimers.
<p>
<li>Redistributions in binary form must reproduce the above copyright notice, this list
of conditions and the following disclaimers in the documentation and/or other
materials provided with the distribution.
<p>
<li>Neither the names of the University of Illinois, NCSA, nor the names of its
contributors may be used to endorse or promote products derived from this
Software without specific prior written permission.
</ul>
<p>
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE CONTIBUTORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
USE OR OTHER DEALINGS IN THE SOFTWARE.
</pre>
<HR><!-- ----- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- -->
<CENTER>
<P><FONT FACE="helvetica,arial" SIZE="2">
<A HREF="mailto:[email protected]">[email protected]</A>
Last modified: Jan 5, 2004<br>
<A HREF="http://www.nlanr.net">NLANR</a> ||
<A HREF="http://dast.nlanr.net">applications support</a> ||
<A HREF="http://ncne.nlanr.net">engineering support</a> ||
<A HREF="http://moat.nlanr.net">measurement and operations</a>
</FONT></P>
</CENTER>
</BODY>
</HTML>
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
Package can be verified like this:
1. Go to
x32: https://sourceforge.net/projects/iperf2/files/iperf-2.1.3-win.exe/download
to download the exe.
2. You can use one of the following methods to obtain the SHA256 checksum:
- Use powershell function 'Get-FileHash'
- Use Chocolatey utility 'checksum.exe'
checksum32: D7C701997578D4E19DC6C779CFD2DCC44AFE3C6941A4F3DCD39A9B669BB53847
checksumType32: SHA256
Log in or click on link to see number of positives.
- iperf2.2.1.3.nupkg (55d305bbfa32) - ## / 62
- iperf2.exe (d7c701997578) - ## / 67
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
iPerf2 2.1.9 | 1119 | Thursday, March 16, 2023 | Approved | |
iPerf2 2.1.8 | 146 | Friday, March 10, 2023 | Approved | |
iPerf2 2.1.7 | 29 | Friday, March 10, 2023 | Approved | |
iPerf2 2.1.6 | 24 | Friday, March 10, 2023 | Approved | |
iPerf2 2.1.4 | 1256 | Friday, November 19, 2021 | Approved | |
iPerf2 2.1.1 | 87 | Friday, November 19, 2021 | Approved | |
iPerf2 2.1.1-dev-20210622 | 101 | Tuesday, July 6, 2021 | Exempted | |
iPerf2 2.1.1-dev-20210407 | 102 | Friday, April 9, 2021 | Exempted | |
iPerf2 2.1.1-dev-202100622 | 83 | Tuesday, July 6, 2021 | Exempted | |
iPerf2 2.1.0-rc02 | 119 | Friday, February 12, 2021 | Approved | |
iPerf2 2.1.0-rc01 | 107 | Thursday, January 7, 2021 | Approved | |
iPerf2 2.0.14.1001-alpha20210104 | 89 | Monday, January 4, 2021 | Approved | |
iPerf2 2.0.14.1001-alpha20201223 | 117 | Wednesday, December 23, 2020 | Approved | |
iPerf2 2.0.14.1001-alpha20201216 | 106 | Wednesday, December 16, 2020 | Approved | |
iPerf2 2.0.14.1001-alpha20201212 | 100 | Saturday, December 12, 2020 | Approved | |
iPerf2 2.0.14.1001-alpha20201211 | 89 | Friday, December 11, 2020 | Approved | |
iPerf2 2.0.14.1001-alpha20201204 | 115 | Friday, December 4, 2020 | Approved | |
iPerf2 2.0.14.1001-alpha20201203 | 116 | Thursday, December 3, 2020 | Approved | |
iPerf2 2.0.14.1001-alpha20201130 | 103 | Monday, November 30, 2020 | Approved | |
iPerf2 2.0.14.1001-alpha20201125 | 121 | Wednesday, November 25, 2020 | Approved | |
iPerf2 2.0.14.1001-alpha20201122 | 90 | Tuesday, November 24, 2020 | Approved | |
iPerf2 2.0.14.1001-alpha20201119 | 104 | Friday, November 20, 2020 | Approved | |
iPerf2 2.0.14.1001-alpha20201022 | 116 | Friday, October 23, 2020 | Exempted | |
iPerf2 2.0.14.1 | 2064 | Monday, March 25, 2019 | Approved | |
iPerf2 2.0.13 | 187 | Friday, October 23, 2020 | Approved | |
iPerf2 2.0.12 | 88 | Friday, October 23, 2020 | Approved | |
iPerf2 2.0.10 | 92 | Friday, October 23, 2020 | Approved | |
iPerf2 2.0.8 | 153 | Friday, October 23, 2020 | Approved |
2021 The Board of Trustees of the University of Illinois
This package has no dependencies.
Ground Rules:
- This discussion is only about iPerf2 and the iPerf2 package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or iPerf2, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
TheCakeIsNaOH (maintainer) on 19 Nov 2021 18:03:36 +00:00:
User 'TheCakeIsNaOH' (maintainer) submitted package.
chocolatey-ops (reviewer) on 19 Nov 2021 18:36:56 +00:00:
iperf2 has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 19 Nov 2021 19:36:38 +00:00:
iperf2 has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/8eb43a903d4532ca634aaa67334f7e5f for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 19 Nov 2021 21:01:23 +00:00:
iperf2 has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has greater than 10 VirusTotal detections associated with it.
This package is now in a waiting state while you review the findings and provide an updated package, or send a message in the package review box on the package page.
TheCakeIsNaOH (maintainer) on 01 Dec 2021 22:53:48 +00:00:
User 'TheCakeIsNaOH' (maintainer) submitted package.
chocolatey-ops (reviewer) on 01 Dec 2021 23:29:51 +00:00:
iperf2 has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
TheCakeIsNaOH (maintainer) on 01 Dec 2021 23:48:15 +00:00:
High virus count on this version for some reason. Just rejecting it, as 2.1.4 is approved.
Status Change - Changed status of package from 'submitted' to 'rejected'.