X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4B1E6316.1090005@etr-usa.com> Date: Tue, 08 Dec 2009 07:30:46 -0700 From: Warren Young User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Cygwin-L Subject: Re: SOCK_RAW raw socket and cygwin References: <8C8865ED624BB94F8FE50259E2B5C5B304593DB2E4 AT palmail03 DOT lsi DOT com> In-Reply-To: <8C8865ED624BB94F8FE50259E2B5C5B304593DB2E4@palmail03.lsi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Leyendecker, Robert wrote: > Is it possible to use a SOCK_RAW in cygwin for read and > write of IP packets? While it's possible Cygwin is breaking something here, I'd first verify that you're not exceeding the underlying stack's capabilities. See the Winsock Programmer's FAQ, item 4.1: http://tangentsoft.net/wskfaq/advanced.html#rawsocket It happens that I'm back to working on the FAQ again, so if you learn anything about raw sockets that you think should go in the FAQ, let me know. Off-list, of course. -- 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