DAST: Iperf - alex_edwards2000 --at-- hotmail.com
>Date: Wed, 10 Nov 2004 12:28:37 -0600
>From: Apache <apache --at-- ncsa.uiuc.edu>
>To: alex_edwards2000 --at-- hotmail.com
>Subject: DAST: Iperf - alex_edwards2000 --at-- hotmail.com
>
>
>Contacting DAST re: Request for information about Iperf
>From: Alex Edwards <alex_edwards2000 --at-- hotmail.com>
>
>Question/Comment:
>When using iperf with a Windows OS, does the -w option (iperf TCP)
actually change the TCP Window Size?
>
>On Windows, the TCP Window Size is a registry value. The registry value
would have to be changed and the PC rebooted for it to take effect. On my
particular setup (Windows 2000), the registry values were not even in their
allocated location in the registry. I had to find a document which gave the
name of the registry value used by Windows for the TCP Window Size, add the
value into the required location in the registry
(HKEY_LOCATION_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters),
and then reboot. After all this, I'm not even sure the change took effect!
>
>So, I'm curious to know how iperf achieves this with just an additional
parameter!
>
>Thanks
>
>
--
Mitch Kutzko | mitch --at-- dast.nlanr.net | mitch --at-- ncsa.uiuc.edu | 217-333-1199
Project: http://dast.nlanr.net/ | Personal: http://hobbes.ncsa.uiuc.edu/