#1 Improve -S failure message on Windows

open
nobody
5
2014-08-16
2006-07-24
Anonymous
No

It appears that by default Windows (XP SP2 tested and
others) does not allow user programs to set the Type
of Service (ToS) bits (also DSCP) in the IP header.

This causes "iperf -c x.x.x.x -S 184" to emit
the message:-
"getpeername failed: Socket is not connected"

This can be resolved by setting the registry key

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001
\Services\Tcpip\Parameters\ DisableUserTOSSetting
as a REG_DWORD with a value of Zero.

Details are in:-
http://support.microsoft.com/default.aspx?scid=kb;EN-
US;q248611

The message emitted by IPERF is however not
particularly helpful and even though I have
done it before it took me a couple of hours
to get to the bottom of it (Again).

I feel that some potential users of iperf may
have more difficulty in overcoming this limitation.

I realise that adding Windows specifics
in the code may cause you dificulty but
I thought it worth presenting the issue
to you.

The referenced article says:-
"On Windows 2000, Windows XP, and Windows
Server 2003, the ToS bits marking
functionality in Winsock applications
and the ping utility is disabled by default."

Thanks for Iperf it is very nice. I am
converted from ttcp:-))

Discussion

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks