Ethereal-users: Re: [Ethereal-users] Lucent Win Modem (dialup) on NT

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

From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Wed, 14 Jan 2004 20:02:44 -0800

On Jan 14, 2004, at 7:34 PM, miten mehta wrote:

I have compaq armada e500 laptop and it has Lucent Win
Modem.  I had tested it to do ppp

That's unfortunate, because...

 In Ethereal I could not see my Lucent Win Modem
interface listed.

...WinPcap 3.0 doesn't support PPP interfaces at all:

	http://winpcap.polito.it/misc/changelog.htm

"Version 3.0 beta, 10 feb 03

		...

	o 	NdisWan support:
◦ due to the large number of messages reporting problems (blue screens) with VPNs, PPTP and such connections, we have disabled the support for NdisWan adapters. As a consequence, it is not possible to capture from PPP (neither NdisWanIp, nor NdisWanBh, nor NdisWanBfIn/Out...). At the moment we have no plans to fix the problem with VPNs, PPTP, PPP unless we get a generous sponsorship."

and WinPcap 2.x doesn't support it as well as one might like - in particular, it doesn't support it on NT (NT 4.0, 5.0 a/k/a W2K, 5.1 a/k/a Windows XP, etc.):

	http://www.ethereal.com/faq.html#q5.4

"3. WinPcap doesn't support PPP WAN interfaces on Windows NT/2000/XP/Server, so Ethereal cannot capture packets on those devices when running on Windows NT/2000/XP/Server. Regular dial-up lines, ISDN lines, and various other lines such as T1/E1 lines are all PPP interfaces. This may cause the interface not to show up on the list of interfaces in the "Capture Options" dialog."

	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."