Hi Robert.
You're right.
You have to build WinPcap woth this option turned on (which is one of the
variants of the project you can use to build the library).
This is to keep the stricter compatibility with libpcap, which is causing us
a lot of headache (libpcap does not have pcap_findalldevs_ex() and
pcap_open(); don't ask me why because I'll become upset).
We believe this should not be a big issue for the vast majority of people,
which are "users" of WinPcap (they do not compile it). I agree with you that
if you want to compile it, you should use this setting in the project.
Cheers,
fulvio
-----Original Message-----
From: Robert Thornthwaite [mailto:[EMAIL PROTECTED]
Sent: venerdi 16 aprile 2004 22.58
To: [EMAIL PROTECTED]
Subject: [WinPcap-users] New WinPcap 3.1 beta functions.
The new functions such as pcap_findalldevs_ex() and pcap_open() to not seem
to be available unless one builds the REMOTE configurations of wpcap. The
documentation does not indicate that the new functions are only available in
the REMOTE configurations. Did I make a mistake?
Robert Thornthwaite
Input/Output, Inc.
phone: 281 879 2112
email: [EMAIL PROTECTED]
web: http://www.i-o.com/
==================================================================
This is the WinPcap users list. It is archived at
http://www.mail-archive.com/[EMAIL PROTECTED]/
To unsubscribe use
mailto: [EMAIL PROTECTED]
==================================================================
