www.delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS |
X-Spam-Check-By: | sourceware.org |
Message-ID: | <4B44EEB7.7000700@cygwin.com> |
Date: | Wed, 06 Jan 2010 15:12:39 -0500 |
From: | "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com> |
Reply-To: | cygwin AT cygwin DOT com |
User-Agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090320 Remi/2.0.0.21-1.fc8.remi Lightning/0.9 Thunderbird/2.0.0.21 Mnenhy/0.7.5.0 |
MIME-Version: | 1.0 |
To: | cygwin AT cygwin DOT com |
Subject: | Re: Cygwin and raw sockets - Windows XP with SP2 , Vista and later |
References: | <53b627ea1001060651u9dc16ddqbc3a38c7fb3f453c AT mail DOT gmail DOT com> <4B44BB7A DOT 5040003 AT cygwin DOT com> <53b627ea1001060921l1c54580akc03f09f4f50e8e07 AT mail DOT gmail DOT com> <4B44CF10 DOT 4040707 AT cygwin DOT com> <53b627ea1001061149l102ce517y5b7c3797c70e6284 AT mail DOT gmail DOT com> |
In-Reply-To: | <53b627ea1001061149l102ce517y5b7c3797c70e6284@mail.gmail.com> |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
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 |
On 01/06/2010 02:49 PM, Karthik Balaguru wrote: > I got the below link that conveys the problems with winpcap usage with cygwin > http://www.mail-archive.com/winpcap-users AT winpcap DOT polito DOT it/msg02534.html > It seems to convey that winpcap can also easily be used with gcc using > the MinGW compile environment (www.mingw.org). True. > It also conveys that winpcap cannot be used from within a cygwin > environment as it depends on the MSVCRT.dll which, innately conflicts > with the cygwin1.dll There is the real potential for conflicts if you just blindly link against Winpcap and use it in some Cygwin app. > So, it can be put as below in brief - > 1.For raw socket usage in a purely windows based application, winpcap > is the right choice. > WinPcap is an open source library for packet capture and network > analysis for the Win32 platforms. I think you missed something key in your reading if you *really* need raw *socket* support above and beyond what you get from Winsock. Re-read your last sentence above again carefully. > 2.For raw socket usage in a linux based application on cygwin > environment, libpcap would be the right choice Right. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |