This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: IP_TOS possible bug?
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 5 Sep 2005 12:10:27 +0200
- Subject: Re: IP_TOS possible bug?
- References: <000001c5b1d3$8af22cf0$2e55d5a5@leemy>
- Reply-to: cygwin at cygwin dot com
On Sep 5 13:37, Yung Leem wrote:
> I am having a trouble with setting IP_TOS.
>
> Currently I am trying to send UDP packets with TOS parameter set to
> something other than the default value of 0x00.
>
> I am using cygwin version 1.5.17(0.129/4/2).
>
> I have no problem sending a UDP packet if I do not call the following
> function,
>
> int rc = setsockopt( inSettings->mSock, IPPROTO_IP, IP_TOS, (char*) &tos,
> len );
>
> rc's value is 0 after the call, so it seemed to work fine, but I believe
> this is what's causing the following error.
>
> "write2 failed: Transport endpoint is not connected"
>
> With some search around, I found that
>
> #define IP_TOS 3 /* old (winsock 1.1) value 8 */
>
> So I tried this value (3 instead of 8), and now it does not give me the
> previous problem
> with "write2 failed: Transport endpoint is not connected", but it does not
> seem to do
> anything when I sniffed the IP packet with Ethereal.
>
> Could anybody help me with this? I really appreciate your help.
IP_TOS is crappy on Windows. First, the value of IP_TOS depends on
whether using Winsock1 or WinSock2, second, it's disabled by default in
systems since W2K.
See http://support.microsoft.com/default.aspx?scid=kb;en-us;248611
for the sad details.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/