MIME-Version: 1.0
In-Reply-To: <4B44BB7A.5040003@cygwin.com>
References: <53b627ea1001060651u9dc16ddqbc3a38c7fb3f453c AT mail DOT gmail DOT com> 	 <4B44BB7A DOT 5040003 AT cygwin DOT com>
Date: Wed, 6 Jan 2010 22:51:01 +0530
Message-ID: <53b627ea1001060921l1c54580akc03f09f4f50e8e07@mail.gmail.com>
Subject: Re: Cygwin and raw sockets - Windows XP with SP2 , Vista and later
From: Karthik Balaguru <karthikbalaguru79 AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Wed, Jan 6, 2010 at 10:04 PM, Larry Hall (Cygwin)
<reply-to-list-only-lh AT cygwin DOT com> wrote:
> On 01/06/2010 09:51 AM, Karthik Balaguru wrote:
>>
>> I got the below info from
>> http://www.cygwin.com/cygwin-ug-net/highlights.html#ov-hi-sockets =A0-
>> 'Socket-related calls in Cygwin basically call the functions by the
>> same name in Winsock, Microsoft's implementation of Berkeley sockets,
>> but with lots of tweaks.'
>> But, It does not clearly convey whether cygwin uses Microsoft's
>> winsock . Does cygwin use winsock ?
>> If cygwin uses winsock, then i think the raw socket usage restrictions
>> applied for further releases from 'Windows XP with SP2' is applicable
>> for cygwin also.:-(
>
> Cygwin does not provide its own implementation for sockets. =A0It uses
> Winsock V2 so basic restrictions imposed by Winsock will constrain
> Cygwin as well.
>

Larry, Thx for the clarification.

But, I came across the below link that conveys that the network
support in Cygwin is supposed to provide the POSIX API, not the
Winsock API -
http://www.cygwin.com/faq/faq.api.html#faq.api.net-functions
What does the above link refer to ?

Interestingly ,the below link conveys that raw sockets is supported
unofficially ! Strange !
http://sourceware.org/ml/cygwin/2005-10/msg00753.html
But, how & why is it supported unofficially ?

The below link seems to convey the problems of using the Raw sockets
with Winsock and it also about the restrictions w.r.t various windows
releases  -
http://tangentsoft.net/wskfaq/advanced.html#rawsocket
So, is the method of usage of winpcap is the only way to use raw
sockets in cygwin environment ?

=46rom http://www.winpcap.org/docs/docs_41b5/html/main.html , I find
that the purpose of WinPcap is to give this kind of access to Win32
applications that it provides facilities to:
1. transmit raw packets 2. capture raw packets and 3. filter the packets
Any other ideas/ways apart from winpcap to use raw sockets in cygwin
environment ?

Thx in advans,
Karthik Balaguru

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple