Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 27 Oct 2005 09:45:12 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Invalid argument error when using recvfrom
Message-ID: <20051027074512.GB28394@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <435FC398 DOT 8000508 AT verizon DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <435FC398.8000508@verizon.net>
User-Agent: Mutt/1.4.2i

On Oct 26 13:57, Fernando Barsoba wrote:
> Hi all,
> 
> Using raw sockets with cygwin is being really painful... After being 
> able to create an IP datagram using the latest snapshot now I'm getting 
> the error "Invalid argument" when calling recvfrom() without doing BIND 
> first.
> 
> There is no need to call bind() before recvfrom when using raw sockets. 
> Why am i getting this error now? Some restriction with winsock?

Probably.  When using raw sockets with Cygwin, you're really in the
hands of Winsock, which has a couple of restrictions in that matter.
I'd suggest to have a look into MSDN which elaborates a bit on the usage
of raw sockets.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT 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/