Ethereal-users: Re: [Ethereal-users] intel anypoint

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Olaf Lachowicz" <olaflachowicz@xxxxxxxxxxx>
Date: Tue, 25 Mar 2003 21:53:33 -0000
WinXP Home Edition
----- Original Message ----- 
From: "Guy Harris" <guy@xxxxxxxxxx>
To: "Olaf Lachowicz" <olaflachowicz@xxxxxxxxxxx>
Cc: <ethereal-users@xxxxxxxxxxxx>
Sent: Tuesday, March 25, 2003 9:37 PM
Subject: Re: [Ethereal-users] intel anypoint


> On Tue, Mar 25, 2003 at 09:19:40PM -0000, Olaf Lachowicz wrote:
> > It is Windows XP indeed, and I installed WinPcap. What is NDIS WAN
> > framework?
> 
> NDIS is the "Network Driver Interface Specification", which is
> Microsoft's specification for how to write drivers for network devices
> on Windows.
> 
> There are routines in both Windows OT (95, 98, Me) and Windows NT (NT
> 3.x, NT 4.0, NT 5.0/Windows 2000, NT 5.1/Windows XP, and so on) that can
> be called by those drivers.
> 
> There are also mechanisms to plug network-layer protocols such as IP
> into the networking code.
> 
> The mechanisms in question are somewhat designed around LANs; in
> Windows, there's an "NDIS intermediate driver", called NDISWAN, that
> provides services that WAN drivers can use.
> 
> > Can you please help me on what to do?
> 
> There's probably not much you *can* do.
> 
> If the Anypoint driver looks like a driver offering PPP, that means it's
> probably using NDISWAN, and that just won't work with WinPcap on Windows
> NT, including the NT 5.1 you're running (which Microsoft calls "Windows
> XP"):
> 
> http://winpcap.polito.it/misc/faq.htm#Q-6
> 
> "Q-6: Can I use WinPcap on a PPP connection?
> 
> A: We have tested WinPcap on PPP connections under Windows 95, Windows
> 98 and Windows ME.  In Windows 95, due to a bug in NDIS, WinPcap
> sometimes resets the PPP connection.  In Windows 98/ME this bug appears
> to be corrected, and WinPcap seems to receive correctly, however it is
> not able to send packets.  Under Windows NT/2000/XP there are problems
> with the binding process, that prevent a protocol driver from working
> properly on the WAN adapter.  The problem is caused by the PPP driver of
> WinNTx, ndiswan, that doesn't provide a standard interface to capture."
> 
> If the Anypoint driver looks like an ATM driver, it might, in theory,
> work, but WinPcap might not have been tested with that:
> 
> http://winpcap.polito.it/misc/faq.htm#Q-17
> 
> "Q-17: Which network adapters are supported?
> 
> A: The NPF device driver was developed to work primarily with Ethernet
> adapters.  Support for other MACs was added during the development, but
> Ethernet remains the preferred one.  The main reason is that all our
> development stations have Ethernet adapters so all our tests were made
> on this type of network.  However, the current situation is:
> 
> ...
> 
>    o Windows NT4/2000: the packet driver works correctly on Ethernet
>      networks.  We were not able to make it working on PPP WAN links,
>      because of binding problems on the NDISWAN adapter.  As in Win9x,
>      FDDI, ARCNET, ATM and Token Ring should be supported, but are not
>      granted to work perfectly.
> 
> ..."
> 
> You'd have to ask the WinPcap developers for more help:
> 
> http://winpcap.polito.it/contact.htm