Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.
Moderation
Every version of each package undergoes a rigorous moderation process before it goes live that typically includes:
- Security, consistency, and quality checking
- Installation testing
- Virus checking through VirusTotal
- Human moderators who give final review and sign off
More detail at Security and Moderation.
Organizational Use
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
Disclaimer
Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Learn more...
- Passing
- Failing
- Pending
- Unknown / Exempted

Downloads:
1,978
Downloads of v 2.1.0-rc01:
29
Last Update:
07 Jan 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 benchmarking
iPerf2
This is a prerelease version of iPerf2.
Downloads:
1,978
Downloads of v 2.1.0-rc01:
29
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
Edit Package
To edit the metadata for a package, please upload an updated version of the package.
Chocolatey's Community Package Repository currently does not allow updating package metadata on the website. This helps ensure that the package itself (and the source used to build the package) remains the one true source of package metadata.
This does require that you increment the package version.
All Checks are Passing
2 Passing Test
To install iPerf2, run the following command from the command line or from PowerShell:
To upgrade iPerf2, run the following command from the command line or from PowerShell:
To uninstall iPerf2, run the following command from the command line or from PowerShell:
NOTE: This applies to both open source and commercial editions of Chocolatey.
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
- Download the Package Download
- Follow manual internalization instructions
-
Package Internalizer (C4B)
- Run
choco download iperf2 --internalize --version=2.1.0-rc01 --source=https://community.chocolatey.org/api/v2
(additional options) - Run
choco push --source="'http://internal/odata/repo'"
for package and dependencies - Automate package internalization
- Run
3. Enter your internal repository url
(this should look similar to https://community.chocolatey.org/api/v2)
4. Choose your deployment method:
choco upgrade iperf2 -y --source="'STEP 3 URL'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade iperf2 -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Ensure iperf2 installed
win_chocolatey:
name: iperf2
state: present
version: 2.1.0-rc01
source: STEP 3 URL
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'iperf2' do
action :install
version '2.1.0-rc01'
source 'STEP 3 URL'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
Chocolatey::Ensure-Package
(
Name: iperf2,
Version: 2.1.0-rc01,
Source: STEP 3 URL
);
Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.
cChocoPackageInstaller iperf2
{
Name = 'iperf2'
Ensure = 'Present'
Version = '2.1.0-rc01'
Source = 'STEP 3 URL'
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'iperf2':
provider => 'chocolatey',
ensure => '2.1.0-rc01',
source => 'STEP 3 URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
salt '*' chocolatey.install iperf2 version="2.1.0-rc01" source="STEP 3 URL"
See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.
5. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved as a trusted package on 07 Jan 2021.
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.
Note:
The actual version should be 2.0.14-alphaYYYYMMDD
not 2.0.14.1001-alphaYYYYMMDD
This is because I previously misunderstood version 2.0.14a
as 2.0.14.1
instead of what it actually is, namely 2.0.14-alpha
.
Please Note: This is an automatically updated package. If you find it is
out of date by more than a day or two, please contact the maintainer(s) and
let them know the package is no longer updating correctly.
md5: 926F7D5290C152EF4CA42760BFFBA7E4 | sha1: 4F06626434F64E8FD8D0802E9C101B4E042103A8 | sha256: B58EBEE070F092BB0ADB52308C5FD82DB5419ED9DF6A420268B7FB48F1C29733 | sha512: B0F730F382B9759BD178DC9943E579F5B060CBB947DBE9FAD70F77E91464C957A90997BF5349C16F3905A1538BA39173120C03675626B78A6D199CF02AFA0DF8
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.0-rc-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: B58EBEE070F092BB0ADB52308C5FD82DB5419ED9DF6A420268B7FB48F1C29733
Log in or click on link to see number of positives.
- iperf2.2.1.0-rc01.nupkg (983a743b90b9) - ## / 66
- iperf2.exe (b58ebee070f0) - ## / 70
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.
Version | Downloads | Last Updated | Status |
---|---|---|---|
iPerf2 2.1.1-dev-20210407 | 5 | Friday, April 9, 2021 | Exempted |
iPerf2 2.1.0-rc02 | 29 | Friday, February 12, 2021 | Approved |
iPerf2 2.1.0-rc01 | 29 | Thursday, January 7, 2021 | Approved |
iPerf2 2.0.14.1001-alpha20210104 | 18 | Monday, January 4, 2021 | Approved |
iPerf2 2.0.14.1001-alpha20201223 | 21 | Wednesday, December 23, 2020 | Approved |
iPerf2 2.0.14.1001-alpha20201216 | 31 | Wednesday, December 16, 2020 | Approved |
iPerf2 2.0.14.1001-alpha20201212 | 18 | Saturday, December 12, 2020 | Approved |
iPerf2 2.0.14.1001-alpha20201211 | 14 | Friday, December 11, 2020 | Approved |
iPerf2 2.0.14.1001-alpha20201204 | 23 | Friday, December 4, 2020 | Approved |
iPerf2 2.0.14.1001-alpha20201203 | 23 | Thursday, December 3, 2020 | Approved |
iPerf2 2.0.14.1001-alpha20201130 | 18 | Monday, November 30, 2020 | Approved |
iPerf2 2.0.14.1001-alpha20201125 | 28 | Wednesday, November 25, 2020 | Approved |
iPerf2 2.0.14.1001-alpha20201122 | 13 | Tuesday, November 24, 2020 | Approved |
iPerf2 2.0.14.1001-alpha20201119 | 19 | Friday, November 20, 2020 | Approved |
iPerf2 2.0.14.1001-alpha20201022 | 26 | Friday, October 23, 2020 | Exempted |
iPerf2 2.0.14.1 | 1587 | Monday, March 25, 2019 | Approved |
iPerf2 2.0.13 | 22 | Friday, October 23, 2020 | Approved |
iPerf2 2.0.12 | 17 | Friday, October 23, 2020 | Approved |
iPerf2 2.0.10 | 21 | Friday, October 23, 2020 | Approved |
iPerf2 2.0.8 | 16 | 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.