Hi there, I've tested winpcap 3.1betas thru 3 on my winXP (single CPU) environment and all seems to work well.
However, I was surprised to find two issues while doing some testing of winpcap 3.1 on my Win2K - SMP environment: 1) It seems that on Win2K SMP, pcap_findalldevs no longer returns the same set of interfaces it does under winpcap 3.0 (I'm expecting the same ones as before with the addition of the NdisWan one). This system has two NICs installed. One is a 3Com device, and the other is an intel device. Both are 100MB ethernet cards. The 3com NIC is the primary NIC on the system used for all communications to and from the system. The second (Intel) NIC is used by a dedicated application (via winpcap), and is not used by anything else on the system. It therefore does not have an IP address (this may or may not be relevant to the observed issue). So, the problem is that pcap_findalldevs no longer mentions the Intel NIC (without the IP address). I'm making this observation BOTH with Ethereal, and the application which uses the Intel NIC. 2) Additionally, The application which uses the dedicated Intel NIC, only really wants to use Ethernet type devices, so it takes the set of interfaces returned by pcap_findalldevs, and uses pcap_open_live on each, and then calls pcap_datalink to validate if the interface type is DLT_EN10MB. Oddly, when using winpcap 3.1 beta3, of the two interfaces returned by pcap_findalldevs (Vertified by Ethereal), the NdisWAN interface passes the DLT_EN10MB test, while the 3Com interface doesn't. The same application binaries (Ethereal and my app) have no issues on WinXP or on Win2K with win-pcap 3.0. Let me know if I can provide more information to track down these issues. Thanks. - Mark Pizzolato ================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] ==================================================================
