|
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
|
[WinPcap-users] 3.1beta - WanPacket vs Adapter selecteability
{Pedro Lucas-Suporte Netcount} Tue, 24 Feb 2004 23:03:22 -0800
- Re: [WinPcap-users] 3.1beta - WanPacket vs ... {Pedro Lucas-Suporte Netcount}
- Re: [WinPcap-users] 3.1beta - WanPacke... Gianluca Varenni
