Hi Bernd,

May I know the reason for choosing Iperf 2.0.4 as the server?

It would be better if you use the Iperf 1.7.0 as a client as well as a
server for a dual test.

Regards,
Anand

-----Original Message-----
From: Bernd Prager [mailto:be...@prager.ws] 
Sent: Wednesday, December 17, 2008 1:27 AM
To: iperf-users@lists.sourceforge.net
Subject: [Iperf-users] dual mode settings

Hi everybody,

I am new to iperf and new to this list, please bear with me.

I am trying to design a test for a network with extremely poor performance.
Before I deploy that test I wanted to figure out what parameter I could
use.
I played around and ended up with some transfer of 50 KByte. That sounded
reasonable.

But when I run the test in dual mode (option -d) the server does not reply
with the same settings.
It transmits some 500MByte back. That would annihilate the current target
network.

Is there a way that I can limit the server response?
I am running iperf version 2.0.4 as server and iperf version 1.7.0 on the
client side.

Thanks a lot for your help,
-- Bernd

(I attached the test I run in my local network for testing.)

./iperf.exe -c host -P 1 -i 5 -p 5001 -w 1k -l 1k -f k -t 50 -d -L 5001
WARNING: TCP window size set to 1024 bytes. A small window size
will give poor performance. See the Iperf documentation.
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 1.00 KByte
------------------------------------------------------------
------------------------------------------------------------
Client connecting to nysdarc01, TCP port 5001
TCP window size: 1.00 KByte
------------------------------------------------------------
[1732] local xxx.xxx.xxx.xxx port 1285 connected with xxx.xxx.xxx.xxx port
5001
[ ID] Interval       Transfer     Bandwidth iperf version 2.0.4
[1732]  0.0- 5.0 sec  51.0 KBytes  83.6 Kbits/sec
[1732]  5.0-10.0 sec  50.0 KBytes  81.9 Kbits/sec
[1732] 10.0-15.0 sec  50.0 KBytes  81.9 Kbits/sec
[1732] 15.0-20.0 sec  50.0 KBytes  81.9 Kbits/sec
[1732] 20.0-25.0 sec  50.0 KBytes  81.9 Kbits/sec
[1732] 25.0-30.0 sec  50.0 KBytes  81.9 Kbits/sec
[1732] 30.0-35.0 sec  50.0 KBytes  81.9 Kbits/sec
[1732] 35.0-40.0 sec  50.0 KBytes  81.9 Kbits/sec
[1732] 40.0-45.0 sec  50.0 KBytes  81.9 Kbits/sec
[1732] 45.0-50.0 sec  50.0 KBytes  81.9 Kbits/sec
[1732]  0.0-50.0 sec   502 KBytes  82.2 Kbits/sec
[1960] local xxx.xxx.xxx.xxx port 5001 connected with xxx.xxx.xxx.xxx port
46227
[ ID] Interval       Transfer     Bandwidth
[1960]  0.0- 5.0 sec  54860 KBytes  89883 Kbits/sec
[1960]  5.0-10.0 sec  53835 KBytes  88203 Kbits/sec
[1960] 10.0-15.0 sec  53795 KBytes  88138 Kbits/sec
[1960] 15.0-20.0 sec  53570 KBytes  87769 Kbits/sec
[1960] 20.0-25.0 sec  54600 KBytes  89457 Kbits/sec
[1960] 25.0-30.0 sec  54738 KBytes  89683 Kbits/sec
[1960] 30.0-35.0 sec  54769 KBytes  89734 Kbits/sec
[1960] 35.0-40.0 sec  55103 KBytes  90281 Kbits/sec
[1960] 40.0-45.0 sec  54536 KBytes  89352 Kbits/sec
[1960]  0.0-50.0 sec  543782 KBytes  89145 Kbits/sec



----------------------------------------------------------------------------
--
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Iperf-users mailing list
Iperf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iperf-users


------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Iperf-users mailing list
Iperf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iperf-users

Reply via email to