<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to bugs</title><link href="https://sourceforge.net/p/iperf/bugs/" rel="alternate"/><link href="https://sourceforge.net/p/iperf/bugs/feed.atom" rel="self"/><id>https://sourceforge.net/p/iperf/bugs/</id><updated>2022-08-24T14:11:44.859000Z</updated><subtitle>Recent changes to bugs</subtitle><entry><title>#69 -b option was changed</title><link href="https://sourceforge.net/p/iperf/bugs/69/?limit=25#830a" rel="alternate"/><published>2022-08-24T14:11:44.859000Z</published><updated>2022-08-24T14:11:44.859000Z</updated><author><name>Rurre</name><uri>https://sourceforge.net/u/rurre/</uri></author><id>https://sourceforge.netbf55d260e05f39dbff40dec59abf0cec766eab46</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;To correct the missing mutiplication symbols:&lt;br/&gt;
new iperf:&lt;br/&gt;
-b xM -&amp;gt; x* 1,024 * 1,024 Mbps is sent&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>-b option was changed</title><link href="https://sourceforge.net/p/iperf/bugs/69/" rel="alternate"/><published>2022-08-24T14:04:20.306000Z</published><updated>2022-08-24T14:04:20.306000Z</updated><author><name>Rurre</name><uri>https://sourceforge.net/u/rurre/</uri></author><id>https://sourceforge.net5795d5b3552b05c07da7e1e597f99f2eade7b21a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I have 2 Linux servers,  one with iperf v2.0.9, the other with iperf v2.1.4&lt;br/&gt;
I observed that there is a change in the new iperf as regards to the usage of option -b:&lt;/p&gt;
&lt;p&gt;old iperf:&lt;br/&gt;
-b xM -&amp;gt; x Mbps is sent&lt;/p&gt;
&lt;p&gt;new iperf:&lt;br/&gt;
-b xM  -&amp;gt; x&lt;em&gt;1,024&lt;/em&gt;1,024 Mbps is sent&lt;/p&gt;
&lt;p&gt;For instance in case of -b100M:&lt;br/&gt;
1) old iperf sends 100Mbps&lt;br/&gt;
&lt;span&gt;[ ID]&lt;/span&gt; Interval       Transfer     Bandwidth&lt;br/&gt;
&lt;span&gt;[  3]&lt;/span&gt;  0.0- 1.0 sec  11.9 MBytes   100 Mbits/sec&lt;br/&gt;
&lt;span&gt;[  3]&lt;/span&gt;  1.0- 2.0 sec  11.9 MBytes   100 Mbits/sec&lt;br/&gt;
&lt;span&gt;[  3]&lt;/span&gt;  2.0- 3.0 sec  11.9 MBytes   100 Mbits/sec&lt;/p&gt;
&lt;p&gt;2) new iperf sends 105Mbps:&lt;br/&gt;
&lt;span&gt;[  1]&lt;/span&gt; 0.00-1.00 sec  12.5 MBytes   105 Mbits/sec&lt;br/&gt;
&lt;span&gt;[  1]&lt;/span&gt; 1.00-2.00 sec  12.5 MBytes   105 Mbits/sec&lt;br/&gt;
&lt;span&gt;[  1]&lt;/span&gt; 2.00-3.00 sec  12.5 MBytes   105 Mbits/sec&lt;br/&gt;
&lt;span&gt;[  1]&lt;/span&gt; 3.00-4.00 sec  12.5 MBytes   105 Mbits/sec&lt;/p&gt;
&lt;p&gt;Please set back as it was originally, users want to see the value they write in -b option.&lt;br/&gt;
I find strange why someone decided to change something that has been  working fine for many years.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#68 Iperf has stopped working</title><link href="https://sourceforge.net/p/iperf/bugs/68/?limit=25#ad71" rel="alternate"/><published>2018-06-27T05:13:44.585000Z</published><updated>2018-06-27T05:13:44.585000Z</updated><author><name>SeungYoul, Heo</name><uri>https://sourceforge.net/u/syheo/</uri></author><id>https://sourceforge.net39dbc07e862943100bdc46d99a9ccea443ea6683</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;do you know what make it happen?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Iperf has stopped working</title><link href="https://sourceforge.net/p/iperf/bugs/68/" rel="alternate"/><published>2018-06-27T01:41:59.770000Z</published><updated>2018-06-27T01:41:59.770000Z</updated><author><name>SeungYoul, Heo</name><uri>https://sourceforge.net/u/syheo/</uri></author><id>https://sourceforge.netce59104a114b3b719e078471e678ada84359114c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi, &lt;br/&gt;
 "iperf has stopped working" message is seen during long use.&lt;br/&gt;
the version is 2.0.9&lt;br/&gt;
OS:  windows 7&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#67 iperf3 does not support Multicast</title><link href="https://sourceforge.net/p/iperf/bugs/67/?limit=25#d825" rel="alternate"/><published>2017-11-29T15:15:48.671000Z</published><updated>2017-11-29T15:15:48.671000Z</updated><author><name>Chris Speidel</name><uri>https://sourceforge.net/u/cspeidel/</uri></author><id>https://sourceforge.net8b2fc94e37f5e78f3441a7f02a50bf9297157d88</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This version of iperf (2.0.5) is no longer being maintained.&lt;/p&gt;
&lt;p&gt;Updates to the original iperf are being made under the iperf2 project:&lt;br/&gt;
&lt;a href="https://sourceforge.net/projects/iperf2/"&gt;https://sourceforge.net/projects/iperf2/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Iperf3 is a separate rewrite of iperf. Tickets may be opened at the iperf3 github page:&lt;br/&gt;
&lt;a href="https://github.com/esnet/iperf" rel="nofollow"&gt;https://github.com/esnet/iperf&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;There is already an existing ticket for multicast support in iperf3: &lt;a href="https://github.com/esnet/iperf/issues/27#issuecomment-341117168" rel="nofollow"&gt;https://github.com/esnet/iperf/issues/27#issuecomment-341117168&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>iperf3 does not support Multicast</title><link href="https://sourceforge.net/p/iperf/bugs/67/" rel="alternate"/><published>2017-09-15T10:17:59.607000Z</published><updated>2017-09-15T10:17:59.607000Z</updated><author><name>vinayak</name><uri>https://sourceforge.net/u/vinu693693/</uri></author><id>https://sourceforge.net7fd03ce74f43671f2d8f706362605b3e32d7d9c2</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;iperf3 is not supporting Multicast like iperf2&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#12 Memory Leak in Iperf 2.02</title><link href="https://sourceforge.net/p/iperf/bugs/12/?limit=25#b46c" rel="alternate"/><published>2017-08-31T23:02:47.283000Z</published><updated>2017-08-31T23:02:47.283000Z</updated><author><name>nick black</name><uri>https://sourceforge.net/u/nickblack/</uri></author><id>https://sourceforge.net11baa12d36b109b705f9d27e07ed6179bf3f3f7f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The cause of the nmap -sV memory pressure is the following in Settings_GenerateClientSettings:&lt;/p&gt;
&lt;p&gt;(client)-&amp;gt;mThreads = ntohl(hdr-&amp;gt;numThreads);&lt;/p&gt;
&lt;p&gt;which is then used to allocate client-&amp;gt;mThreads items a bit later. With iperf2 2.0.9 and nmap 7.60, this results in a mThreads value of 1929256211 and a rapid OOM. Note that this happens even if --disable-threads is used with configure.&lt;/p&gt;
&lt;p&gt;On our builds, I've added the following:&lt;/p&gt;
&lt;p&gt;--- iperf-2.0.9-orig/src/Settings.cpp   2017-08-31 15:33:53.583021939 -0400&lt;br/&gt;
+++ iperf-2.0.9/src/Settings.cpp    2017-08-31 15:33:45.306958987 -0400&lt;br/&gt;
@@ -808,6 +808,10 @@&lt;br/&gt;
                                       client_hdr &lt;em&gt;hdr ) {&lt;br/&gt;
     int flags = ntohl(hdr-&amp;gt;flags);&lt;br/&gt;
     if ( (flags &amp;amp; HEADER_VERSION1) != 0 ) {&lt;br/&gt;
+        if ( ntohl(hdr-&amp;gt;numThreads) != 1 ) {&lt;br/&gt;
+          &lt;br/&gt;
&lt;/em&gt;client = NULL;&lt;br/&gt;
+            return;&lt;br/&gt;
+        }&lt;br/&gt;
&lt;em&gt;client = new thread_Settings;&lt;br/&gt;
         memcpy(&lt;/em&gt;client, server, sizeof( thread_Settings ));&lt;br/&gt;
         setCompat( (*client) );&lt;/p&gt;
&lt;p&gt;Since we only ever use singly-threaded clients, this works for us.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#66 [Bug] iperf - "speed" display in CSV report</title><link href="https://sourceforge.net/p/iperf/bugs/66/?limit=25#a8cf" rel="alternate"/><published>2016-07-27T10:53:43.192000Z</published><updated>2016-07-27T10:53:43.192000Z</updated><author><name>Atul Singh MandLA</name><uri>https://sourceforge.net/u/amandla/</uri></author><id>https://sourceforge.netab529c14735b8331e05a256af99acfd087a9f359</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Want to report this bug.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>[Bug] iperf - "speed" display in CSV report</title><link href="https://sourceforge.net/p/iperf/bugs/66/" rel="alternate"/><published>2016-07-27T10:52:54.572000Z</published><updated>2016-07-27T10:52:54.572000Z</updated><author><name>Atul Singh MandLA</name><uri>https://sourceforge.net/u/amandla/</uri></author><id>https://sourceforge.nete69666cfce3de8c3a25daaa2faeb08ba5fb1b27c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi all,&lt;/p&gt;
&lt;p&gt;I would like to report this bug.&lt;br/&gt;
 Some parameters displayed in the CSV reports are declared as uint64_t, but the printf format doesn't reflect this, I would like to know if the issue is addressed anywhere else I can submit the patch which will take care of the same.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#23 Daemon mode does not allow return traffic when using UDP</title><link href="https://sourceforge.net/p/iperf/bugs/23/?limit=25#33f8" rel="alternate"/><published>2016-06-08T08:23:23.922000Z</published><updated>2016-06-08T08:23:23.922000Z</updated><author><name>Dave Kruger</name><uri>https://sourceforge.net/u/vuader/</uri></author><id>https://sourceforge.netc33887d6e8d5354f3bc919fb0ad52a0dc5518fa6</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I am also seeing this in 2.0.5. @bjoernh did you ever manage to find a workaround?&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>