Martin T | 22 Aug 11:49 2014
Picon

Re: Iperf client 2.0.5 shows unrealistic bandwidth results if Iperf server is unreachable

Hi,

> The report shall report  that the receiver did not see the generated packets.

The Iperf client reports this by saying that "WARNING: did not receive
ack of last datagram after 3 tries".
What I find weird are those unrealistic sent traffic results printed
by Iperf client. If I execute "iperf -c 10.10.10.1 -fm -t 600 -i60 -u
-b 500m" and 10.10.10.1 is firewalled/non-reachable, then I expect
output like this:

root <at> vserver:~#  iperf -c 10.10.10.1 -fm -t 600 -i60 -u -b 500m
------------------------------------------------------------
Client connecting to 10.10.10.1, UDP port 5001
Sending 1470 byte datagrams
UDP buffer size: 0.22 MByte (default)
------------------------------------------------------------
[  3] local 192.168.1.2 port 38755 connected with 10.10.10.1 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-60.0 sec  3613 MBytes   505 Mbits/sec
[  3] 60.0-120.0 sec  3620 MBytes   506 Mbits/sec
[  3] 120.0-180.0 sec  3618 MBytes   506 Mbits/sec
etc

In other words Iperf client should send traffic despite the fact that
10.10.10.1 is unreachable because UDP is connectionless and amount of
bandwidth sent should be ~500Mbps because this is determined during
the execution of client with the "-b" flag.

regards,
(Continue reading)

Martin T | 22 Aug 11:19 2014
Picon

How does Iperf server detect that the client has stopped transmitting and it should send the server report?

Hi,

if I execute "iperf -c 10.10.10.1 -fm -t 10 -u -b 50m", then am I
correct that the last datagram sent by the Iperf client includes a
special pattern which is an indication for Iperf server to send the
server report? First bytes of the last datagram should be like
ff:ff:fc:ac:53:f6:f1:57:00:04:93:b4,
ff:ff:ff:a9:53:f7:09:8e:00:0e:34:ac, etc while non-last datagrams
begin with bytes 00:00:00:53:53:f7:09:8e:00:0d:7c:ee,
00:00:00:03:53:f7:09:8d:00:0e:64:0f, etc.

thanks,
Martin

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Iperf-users mailing list
Iperf-users@...
https://lists.sourceforge.net/lists/listinfo/iperf-users

Martin T | 21 Aug 15:53 2014
Picon

Iperf client sends out less UDP traffic than determined with "-b" flag

Hi,

if I executed "iperf -c 10.10.10.1 -fm -t 600 -i 60 -u -b 500m" in a
virtual-machine with GigE vNIC, then Iperf client(version 2.0.5) under
Debian sent traffic at 120Mbps during all the intervals. If I replaced
the OS in virtual-server with CentOS, the same Iperf release with the
same command was able to send traffic at 500Mbps. Does Iperf client
count packets it successfully manages to send and calculates the
amount of data sent by knowing the datagram size? What are the
theoretical possibilities to low bandwidth rate printed by Iperf
client other than very little CPU time(Iperf process is not able to
send out packets with sufficient rate)?

regards,
Martin

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Iperf-users mailing list
Iperf-users@...
https://lists.sourceforge.net/lists/listinfo/iperf-users

Martin T | 21 Aug 15:12 2014
Picon

Iperf client 2.0.5 shows unrealistic bandwidth results if Iperf server is unreachable

Hi,

if I execute "iperf -c 10.10.10.1 -fm -t 600 -i 60 -u -b 500m" and
10.10.10.1 is behind the firewall so that Iperf client is not able to
reach it, then I will see following results printed by Iperf client:

[  ID]   Interval                Transfer                   Bandwidth
[   3]   0.0 - 60.0 sec      422744 MBytes       59104 Mbits/sec
[   3]   60.0 - 120.0 sec  435030 MBytes       60822 Mbits/sec
etc

Why does Iperf client behave like that? Is this a know bug?

thanks,
Martin

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Iperf-users mailing list
Iperf-users@...
https://lists.sourceforge.net/lists/listinfo/iperf-users

Martin T | 21 Aug 14:17 2014
Picon

transfered data and bandwidth in Iperf client output do not match

Hi,

after an Iperf test, I got following results:

[root <at>  ~]# iperf -c 192.168.2.1 -u -fm -t60 -d -b 10m
------------------------------------------------------------
Server listening on UDP port 5001
Receiving 1470 byte datagrams
UDP buffer size: 0.04 MByte (default)
------------------------------------------------------------
------------------------------------------------------------
Client connecting to 192.168.2.1, UDP port 5001
Sending 1470 byte datagrams
UDP buffer size: 0.01 MByte (default)
------------------------------------------------------------
[  4] local 192.168.1.1 port 32284 connected with 192.168.2.1 port 5001
[  3] local 192.168.1.1 port 5001 connected with 192.168.2.1 port 52428
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-60.0 sec  71.5 MBytes  10.0 Mbits/sec
[  4] Sent 51021 datagrams
[  4] Server Report:
[  4]  0.0-59.9 sec  69.8 MBytes  9.77 Mbits/sec   0.112 ms 1259/51020 (2.5%)
[  4]  0.0-59.9 sec  1 datagrams received out-of-order
[  3]  0.0-60.0 sec  69.8 MBytes  9.77 Mbits/sec   0.030 ms 1200/51021 (2.4%)
[  3]  0.0-60.0 sec  1 datagrams received out-of-order
[root <at>  ~]#

How did Iperf calculate, that it sent 71.5 MBytes? I mean it says it
has sent 51021 datagrams and one datagram is 1470B so I should have
sent 75MB instead(51021*1470/10^6). Or if I calculate transferred data
(Continue reading)

Sijo Joy | 12 Aug 20:56 2014
Picon

Iperf report interval granularity in milliseconds

Hi,

Iperf can report throughput in a step of 0.5 second (specified via - i option). Can it use a even smaller interval, such as in the order of milliseconds or 10 milliseconds? Is there any other tools which can reach that granularity? Thanks for your inputs in advance.

Best Regards,
Sijo
------------------------------------------------------------------------------
_______________________________________________
Iperf-users mailing list
Iperf-users@...
https://lists.sourceforge.net/lists/listinfo/iperf-users
Bruce A. Mah | 28 Jul 21:03 2014
Picon

iperf-3.0.6 is available


ESnet (Energy Sciences Network) is proud to announce the public
release of iperf-3.0.6.  This version is a maintenance release with a
few bug fixes and enhancements, notably:

* Several problems with the -B option have been fixed.  Also, API
  calls have been added to libiperf to extend this functionality to
  API clients.

* Some portability fixes for OpenBSD and Solaris have been merged from
  the mainline.

More information on changes can be found in the RELEASE_NOTES
file in the source distribution.

iperf3 is a tool for measuring the maximum TCP and UDP performance
along a path, allowing for the tuning of various parameters and
reporting measurements such as throughput, jitter, and datagram packet
loss.

The original iperf was implemented by NLANR / DAST.  Version 3 is a
complete reimplementation, with the goals of a smaller, simpler code
base, and a library that can be used by other programs.  It also adds
new functionality, such as CPU utilization measurements, zero copy TCP
support, and JSON output.  Note that iperf3 clients and servers are
not compatible with, and will not interoperate with, earlier versions
of iperf.

iperf3 is fully supported on Linux, FreeBSD, and MacOS X.  It may run
on other platforms as well, although it has not received the same
attention and testing.

The source code for iperf 3.0.6 is available at:

http://downloads.es.net/pub/iperf/iperf-3.0.6.tar.gz

SHA256 hash:

3c5909c9b286b6503ffa141a94cfc588915d6e67f2aa732b08df0af73e21938b  iperf-3.0.6.tar.gz

iperf3 is freely-redistributable under a 3-clause BSD license.  More
information can be found in the LICENSING file inside the source
distribution.

Additional documentation for iperf3 can be found at:

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

The mailing list for iperf3 development is:

iperf-dev@...

To see the list archives or join the mailing list, visit:

http://groups.google.com/group/iperf-dev

arrows Himma | 21 Jul 20:58 2014
Picon

Threading

Hi,
This is arrows.
I want to have multiple simultaneous connections from different clients  to a single server using -P in iperf . but first , i am  required to enable threading in the client and the server.
How to do it?

I appreciate your help
Thank you,
Siham
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Iperf-users mailing list
Iperf-users@...
https://lists.sourceforge.net/lists/listinfo/iperf-users
Freeman (Xiaoguang) Wang | 8 Jul 04:59 2014

Different iperf UDB behaviour on Fedora 14 and 18

Hi

 

We were test iperf UDP and found with old releases like Fedora 14, iperf TX side does not know the limitation of the link and keeps send at a data rage specified by the command line, so at the TX side we observe lots of packet drops. However, with Fedora 18 and above, it seems iperf UDP traffic is self-regulated and automatically find out the best data rate, and the RX side hardly shows any packet drop.

 

Anybody know the reason? It looks we actually ran the same version of iperf 2.0.5 on both systems.

 

Thanks

FRW

 

------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Iperf-users mailing list
Iperf-users@...
https://lists.sourceforge.net/lists/listinfo/iperf-users
Bruce A. Mah | 16 Jun 20:14 2014
Picon

iperf-3.0.5 is available


ESnet (Energy Sciences Network) is proud to announce the public
release of iperf-3.0.5.  This version is a maintenance release with a
few bug fixes and enhancements, notably:

* A timing issue which caused measurement intervals to be wrong with
  TCP tests on lossy networks has been fixed.

* It is now possible to get (most of) the server-side output at
  the client by using the --get-server-output flag.

* A number of bugs with --json output have been fixed.

More information on changes can be found in the RELEASE_NOTES
file in the source distribution.

Note:  An iperf 3.0.4 release was planned and tagged, but not
officially released.

Related project news:

* Project documentation is in the process of being moved from project
  wiki on GitHub to GitHub Pages at this URL:

  http://software.es.net/iperf/

* Source tarballs are now available at:

  http://downloads.es.net/public/iperf/

iperf3 is a tool for measuring the maximum TCP and UDP performance
along a path, allowing for the tuning of various parameters and
reporting measurements such as throughput, jitter, and datagram packet
loss.

The original iperf was implemented by NLANR / DAST.  Version 3 is a
complete reimplementation, with the goals of a smaller, simpler code
base, and a library that can be used by other programs.  It also adds
new functionality, such as CPU utilization measurements, zero copy TCP
support, and JSON output.  Note that iperf3 clients and servers are
not compatible with, and will not interoperate with, earlier versions
of iperf.

iperf3 is fully supported on Linux, FreeBSD, and MacOS X.  It may run
on other platforms as well, although it has not received the same
attention and testing.

The source code for iperf 3.0.5 is available at:

http://downloads.es.net/pub/iperf/iperf-3.0.5.tar.gz

SHA256 hash:

e1e1989985b17a4c03b0fa207004ad164b137e37ab0682fecbf5e93bcaa920a6  iperf-3.0.5.tar.gz

iperf3 is freely-redistributable under a 3-clause BSD license.  More
information can be found in the LICENSING file inside the source
distribution.

Additional documentation for iperf3 can be found at:

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

The mailing list for iperf3 development is:

iperf-dev@...

To see the list archives or join the mailing list, visit:

http://groups.google.com/group/iperf-dev

Sergey Naumov | 22 Apr 14:30 2014
Picon

Win32 bad UDP handling

Hello.

I noticed in the source code that in Win32 case iperf uses single threaded mode for UDP traffic because 'WIN32 does bad UDP handling so run single threaded' as stated in comments.

Could somebody explain a bit more why it is handled bad? I faced a problem with UDP handling under WinXP for iperf compiled under cygwin (on Win7). On Win7 everything was good, but on WinXP it looks like some race condition happens - sometimes iperf reports traffic and sometimes does not. I've managed to make it work by introducing some if defined(__CYGWIN__) in Listerer.cpp,

but want to know 2 things:
1. What WinXP doos bad with UDP.
2. How performance could be affected by running iperf in single threaded mode.

Thanks,
Sergey Naumov.
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
Iperf-users mailing list
Iperf-users@...
https://lists.sourceforge.net/lists/listinfo/iperf-users

Gmane