Downloads:

32,209

Downloads of v 3.1.3:

31,202

Last Update:

22 Jun 2016

Package Maintainer(s):

Software Author(s):

  • Jon Dugan
  • Seth Elliott
  • Bruce A. Mah
  • Jeff Poskanzer
  • Kaustubh Prabhu

Tags:

iperf admin iperf3

iPerf3 - The TCP, UDP and SCTP network bandwidth measurement tool

3.1.3 | Updated: 22 Jun 2016

Downloads:

32,209

Downloads of v 3.1.3:

31,202

Maintainer(s):

Software Author(s):

  • Jon Dugan
  • Seth Elliott
  • Bruce A. Mah
  • Jeff Poskanzer
  • Kaustubh Prabhu

iPerf3 - The TCP, UDP and SCTP network bandwidth measurement tool 3.1.3

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install iPerf3 - The TCP, UDP and SCTP network bandwidth measurement tool, run the following command from the command line or from PowerShell:

>

To upgrade iPerf3 - The TCP, UDP and SCTP network bandwidth measurement tool, run the following command from the command line or from PowerShell:

>

To uninstall iPerf3 - The TCP, UDP and SCTP network bandwidth measurement tool, 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

  • 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://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

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade iperf3 -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 iperf3 -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 iperf3 installed
  win_chocolatey:
    name: iperf3
    state: present
    version: 3.1.3
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'iperf3' do
  action    :install
  version  '3.1.3'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: iperf3,
    Version: 3.1.3,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller iperf3
{
   Name     = 'iperf3'
   Ensure   = 'Present'
   Version  = '3.1.3'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'iperf3':
  provider => 'chocolatey',
  ensure   => '3.1.3',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install iperf3 version="3.1.3" 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.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator dtgm on 23 Jun 2016.

Description

Package fix release to include x86 build.

iPerf3 is a tool for active measurements of the maximum achievable bandwidth on IP networks. It supports tuning of various parameters related to timing, buffers and protocols (TCP, UDP, SCTP with IPv4 and IPv6). For each test it reports the bandwidth, loss, and other parameters. This is a new implementation that shares no code with the original iPerf and also is not backwards compatible. iPerf was orginally developed by NLANR/DAST. iPerf3 is principally developed by ESnet / Lawrence Berkeley National Laboratory. It is released under a three-clause BSD license.


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';

$packageName = 'iPerf3'
$url = 'https://iperf.fr/download/windows/iperf-3.1.3-win32.zip'
$url64 = 'https://iperf.fr/download/windows/iperf-3.1.3-win64.zip'
$checksum = '36229bacfda9ad0a05d7eba9e3843b18b94046da'
$checksum64 = 'c63d306daac82987839ed94cd8705a1121af0181'
$checksumType = 'sha1'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

Install-ChocolateyZipPackage -packageName "$packageName" -url "$url" -unzipLocation "$toolsDir" -checksum $checksum -checksumType $checksumType -url64bit "$url64" -checksum64 $checksum64

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
iPerf3 - The TCP, UDP and SCTP network bandwidth measurement tool 3.1.2.20160324 345 Thursday, March 24, 2016 Approved
iPerf3 - The TCP, UDP and SCTP network bandwidth measurement tool 3.1.2 239 Tuesday, March 22, 2016 Approved
iPerf3 3.0.11 423 Tuesday, December 29, 2015 Approved

2016-06-08: Security Issue: iperf-3.1.3, iperf-3.0.12 released

  These releases address a security issue that could cause a crash of an iperf3 process (it could theoretically lead to a remote code execution). Although the risk for common use cases is believed to be low, all users are encouraged to update to these versions or newer as soon as possible. More information on the security vulnerability can be found in the following ESnet Software Security Advisory:

  iperf-3.1.3 also includes support for fair-queueing, per-socket based pacing of tests on platforms that support it (currently recent Linux distributions), as well as several other fixes.

  (http://software.es.net/iperf/news.html)

== 2016-02-01: iperf-3.1.2 released ==

  • This release fixes a couple of minor bugs, including one that results in invalid JSON being emitted for UDP tests.

== 2015-11-19: iperf-3.1.1 released ==

  • This release fixes a few minor bugs.

== iperf 3.1 2015-10-16 ==

The release notes for iperf 3.1 describe changes and new
functionality in iperf 3.1, but not present in 3.0.11 or any earlier
3.0.x release.

  • Selected user-visible changes

    • SCTP support has been added (with the --sctp flag), on Linux,
      FreeBSD, and Solaris (issue #131).

    • Setting CPU affinity now works on FreeBSD.

    • Selection of TCP congestion now works on FreeBSD, and is now
      called --congestion (the old --linux-congestion option works
      but is now deprecated).

    • A new -I option for the server causes it to write a PID file,
      mostly useful for daemon mode (issue #120).

    • A --logfile argument can now force all output to go to a file,
      rather than to a file. This is especially useful when running an
      iperf3 server in daemon mode (issue #119).

    • Various compatibility fixes for Android (issue #184, issue #185), iOS (issue #288), NetBSD (issue #248), Solaris (issue #175, issue #178, issue #180, issue #211), vxWorks (issue #268).

    • A --udp-counters-64bit flag has been added to support very
      long-running UDP tests, which could cause a counter to overflow
      (issue #191).

    • A --cport option to specify the client-side port has been added
      (issue #207, issue #209, issue #239).

    • Some calculation errors with the -O feature have been fixed (issue #236).

    • A potential crash in the iperf3 server has been fixed (issue #257,
      issue #258).

    • Many miscellaneous bug fixes.

  • Selected developer-visible changes

    • Consumers of libiperf can now get the JSON output for a
      just-completed test (issue #147).

    • Detection of various optional features has been improved to check
      for the presence or absence of platform functionality, not the name
      of platforms.

    • Out-of-tree builds now work (issue #265).


This package has no dependencies.

Discussion for the iPerf3 - The TCP, UDP and SCTP network bandwidth measurement tool Package

Ground Rules:

  • This discussion is only about iPerf3 - The TCP, UDP and SCTP network bandwidth measurement tool and the iPerf3 - The TCP, UDP and SCTP network bandwidth measurement tool 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 iPerf3 - The TCP, UDP and SCTP network bandwidth measurement tool, 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.
comments powered by Disqus