Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Mon, 25 Mar 2002 12:06:43 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Networking problem Message-ID: <20020325170643.GJ18503@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3C9EBD68 DOT 4A5B688 AT npd DOT hcltech DOT com> <4 DOT 3 DOT 1 DOT 2 DOT 20020325094404 DOT 0231cb70 AT pop DOT ma DOT ultranet DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4.3.1.2.20020325094404.0231cb70@pop.ma.ultranet.com> User-Agent: Mutt/1.3.23.1i On Mon, Mar 25, 2002 at 09:46:50AM -0500, Larry Hall (RFK Partners, Inc) wrote: >At 01:02 AM 3/25/2002, Rajaraman B wrote: >>There is no support for IP_HDRINCL socket option. Many header files > >Check out Winsock capabilities in this area. Cygwin's socket support >is dependent on Winsock functionality. Of course patches to augment Cygwin are always cheerfully accepted, too. If Winsock can do it, then Cygwin should be able to do it. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/