Open GoogleCodeExporter opened 9 years ago
[deleted comment]
In response to Comment #1 (which I got in my email but don't see on this web
page):
I don't see the information you describe at the site
http://openmaniak.com/iperf.php#iperf-b. This issue is related to the "-b"
(bandwidth) option, which seems to be unique in how the "K" and "M" symbols are
interpreted. From the iperf man page:
-b, --bandwidth n[KM]
set target bandwidth to n bits/sec (default 1 Mbit/sec). This
setting requires UDP (-u).
It would seem from this docuemntation that the "M" indicates Mbit/sec, so it
stands
to reason that "K" indicates Kbit/sec, not Kbyte/sec.
Furthermore, when you actually run jperf in UDP mode with the bandwidth set to
512
Kbytes/sec, you can see from the iperf output that the badwidth used is 512
kbits/sec, not 512 Kbytes/sec.
Original comment by dennytr...@gmail.com
on 8 May 2009 at 12:59
even i faced the same problem ,i have struggled for 1 week whether i am doing
my work
wrong or some thing wrong with the jperf,same problem has been for me,there is
maistake in KILOBYTES AND KILOBITS,even u give KILOBYTES its taking the
bandwidth as
kilobits,i have checked 200 times really which wasted a week of time
Original comment by bangaral...@gmail.com
on 27 Jun 2009 at 10:24
can any one give me the reason why it happened,pls reply to
bangaraluri@yahoo.com
Original comment by bangaral...@gmail.com
on 27 Jun 2009 at 10:27
Yes, iperf use bits/sec as the UDP bandwidth unit.
Here is a patch to fix this.
Original comment by solrex
on 22 Jul 2009 at 4:44
Attachments:
Hi all, I fixed this error and put binary packets on my site. You can download
deb/jar/src packets of modified jperf 2.0.2 from http://share.solrex.cn/ibuild/.
NOTE: I have packed all *.jar in lib/ into the final jar file, so you can start
jperf
simply by typing: java -jar jperf-2.0.2-solrex1.jar (in case you are not a
Debian user).
Original comment by solrex
on 22 Jul 2009 at 9:56
please, anyone could compile and upload it to anywhere?
Original comment by txe...@gmail.com
on 27 Jan 2011 at 4:12
Original issue reported on code.google.com by
dennytr...@gmail.com
on 12 Jan 2009 at 2:04