Re: [WinPcap-users] 3.1beta - WanPacket vs Adapter selecteability

[Gianluca Varenni]

Hi.   First of all, the support for WAN we added into winpcap3.1beta should be transparent to the user, i.e. you can use wan adapters with both PacketXXX and pcap_XXX APIs. As a consequence, all the stuff contained in WanPacket.cpp/.h SHOULD NOT be used (in fact, it is not exported in the developer's pack!); those files are separate from the packet.dll (and shipped in wanpacket.dll) only for developing purposes.   I suggest you to try the normal PacketXXX APIs, or BETTER, the pcap_XXX APIs (as you have probably read in the docs, the PacketXXX can change between different winpcap releases, and in fact we changed some functions/signatures into winpcap 3.1beta, as you've probably seen in the winpcap 3.1beta release notes).   Have a nice day GV   ----- Original Message ----- From: {Pedro Lucas-Suporte Netcount} To: [EMAIL PROTECTED] Sent: Tuesday, February 24, 2004 8:07 PM Subject: [WinPcap-users] 3.1beta - WanPacket vs Adapter selecteability Hello   Up to Winpcap 2.3, I've been using Ndiswan as the adapter to be opened for all users of my tool that require packet measurements via PPPoE (ADSL users) or Ethernet (Cable users). I am using Packet.lib directly, and not wpcap.lib, and Windows XP.   Unfortunately, some of my users keep regretting that they cannot not see Ndiswan as a "selecteable" adapter, even with after trials like those in http://winpcap.polito.it/misc/dialup.htm . In spite of that, all of them can see an adapter called "WAN (PPP/SLIP) interface", but that adapter failed to open.   As I have observed, for 3.1beta, Winpcap development team is + committed to support WAN access. I already compiled errored free my tool with WanPacket.cpp and WanPacket.h, and I am now proceeding to kind-of duplicate my code for LAN/WAN by using the new API.   My question is simple:   a) WAN users that have a selecteable adapter called "WAN (PPP/SLIP) interface" after establishing an ADSL session (all have), will they be able to open it with the API call WanPacketOpenAdapter(...) ? Or b) Is it that Ndiswan (\Device\Packet_NdisWanIpNdisWan ? ) must continue to show up as a selecteable adapter for WanPacketOpenAdapter( ) to work ???     Meanwhile, count me as an intermediate tester w/ a lot of users that will start testing the WanPacket services for 3.1beta by middle March.   Thanx a Lot for Winpcap ! Pedro Lucas http://netcount.no-ip.com