perfsonar-user - Re: [perfsonar-user] [Iperf-users] iperf-3.10 is available
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Bob McMahon <>
- To: "Bruce A. Mah" <>
- Cc: , iPerf User Group <>, ,
- Subject: Re: [perfsonar-user] [Iperf-users] iperf-3.10 is available
- Date: Tue, 1 Jun 2021 14:14:22 -0700
Hi Bruce,
We used the %<dev> for both tx and and rx device binding in iperf 2. Just something to consider for consistency between the two tools.
To affect the physical output interface (e.g. dual homed systems) either use -c <host>%<dev> (requires root) which bypasses this host route table lookup, or configure policy routing per each -B source address and set the output interface appropriately in the policy routes. On the server or receive, only packets destined to -B IP address will be received. It's also useful for multicast. For example, iperf -s -B 224.0.0.1%eth0 will only accept ip multicast packets with dest ip 224.0.0.1 that are received on the eth0 interface, while iperf -s -B 224.0.0.1 will receive those packets on any interface, Finally, the device specifier is required for v6 link-local, e.g. -c [v6addr]%<dev> -V, to select the output interface.
Bob
To affect the physical output interface (e.g. dual homed systems) either use -c <host>%<dev> (requires root) which bypasses this host route table lookup, or configure policy routing per each -B source address and set the output interface appropriately in the policy routes. On the server or receive, only packets destined to -B IP address will be received. It's also useful for multicast. For example, iperf -s -B 224.0.0.1%eth0 will only accept ip multicast packets with dest ip 224.0.0.1 that are received on the eth0 interface, while iperf -s -B 224.0.0.1 will receive those packets on any interface, Finally, the device specifier is required for v6 link-local, e.g. -c [v6addr]%<dev> -V, to select the output interface.
Bob
On Tue, Jun 1, 2021 at 11:07 AM Bruce A. Mah <> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
ESnet (Energy Sciences Network) is proud to announce the availability
of iperf 3.10. This release is primarily a bugfix release. A few new
features, controlled by various new command-line flags, have been
added (--time-skew-threshold, --bind-dev, --rcv-timeout,
- --dont-fragment). More information can be found in the iperf-3.10
release notes, which are contained in the RELNOTES.md file in the
distribution.
iperf 3.10 should be fully backward-compatible with prior iperf3
releases, that is, iperf 3.10 clients and servers should interoperate
correctly with all 3.x clients and servers.
iperf3 is a tool for measuring the maximum TCP, UDP, and SCTP
throughput along a path, allowing for the tuning of various parameters
and reporting measurements such as throughput, jitter, and datagram
packet loss. It is fully supported on Linux, FreeBSD, and macOS. It
may run on other platforms as well, although it has not received the
same attention and testing. Note that iperf3 is not compatible with,
and will not interoperate with, version 2 or earlier of iperf,
although the two versions can co-exist on the same hosts and networks.
The source code for iperf 3.10 is available at:
https://downloads.es.net/pub/iperf/iperf-3.10.tar.gz
SHA256 hash:
4390982928542256c17d6dd1f56eede9092649ebfd8a97c8cecfad12d238ad57
iperf3 is freely-redistributable under a 3-clause BSD license. More
information can be found in the LICENSE file inside the source
distribution.
Additional documentation for iperf3 can be found at:
https://software.es.net/iperf
More information about iperf3 (including the issue tracker, source
code repository access, and mailing list) can be found on the iperf3
page on GitHub at:
https://github.com/esnet/iperf
User questions can go to the iperf users list (which is more-or-less
shared between iperf2 and iperf3):
Mailing list information and archives can be found at:
https://lists.sourceforge.net/lists/listinfo/iperf-users
The mailing list for iperf3 development is:
To see the list archives or join the mailing list, visit:
http://groups.google.com/group/iperf-dev
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEE+Fo4IENp9xo01E6DSYSRCoyq7ooFAmCu5NQACgkQSYSRCoyq
7opv6wf9FtXz7HtWz4er0Tyre3maBj3mvn2/NYFAKsZnhdLZW4EOVU9JD7XSrrX7
lKPqQV2FM0PS412ttJgnn6Hoby0lVvUqOsNBxN3BtefxUSpQyWrmG0a0b12vz10Q
dgJ0q2XYtmFgVEi2+9kzuPdPeAw/IwJ1pg0RZNIWupKqhflPdFJw8nDls/eeN26h
abf5XpLsNIDLAJi58mwsTr+94t34RkYaWj/MDT5fjYru9LjXcEHMh00JnD2RAwyg
OOQT5qIXyQIaFK1akxu2lOwlKgZp401LFVnYyyP9LMDhTlmCqLbnWwB1mNiOk1jH
tCnjDwITiBRCVRN2E6/kzNtrj//KpQ==
=CZRC
-----END PGP SIGNATURE-----
_______________________________________________
Iperf-users mailing list
https://lists.sourceforge.net/lists/listinfo/iperf-users
This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
- [perfsonar-user] iperf-3.10 is available, Bruce A. Mah, 06/01/2021
- Re: [perfsonar-user] [Iperf-users] iperf-3.10 is available, Bob McMahon, 06/01/2021
- Re: [perfsonar-user] [Iperf-users] iperf-3.10 is available, Bruce A. Mah, 06/02/2021
- Re: [perfsonar-user] [Iperf-users] iperf-3.10 is available, Bob McMahon, 06/01/2021
Archive powered by MHonArc 2.6.24.