FW: wpa_supplicant/TTLS/EAP-MD-5 on XP complains "NDIS: Could notfind interface ... "

[Wen Chen]

Hi Jouni,

Thanks for the feedback.  You were right that I was using an older winpcap.
But, the interface initialization problem appears to be persistingafter I
upgraded to WinPcap_3_1_beta4.exe.

The following supplicant output shows that wpa_supplicant is figuring out a
few more information before it stopped.  

Thanks for the help,

Wen

----------------------------------
C:\local\hostap\wpa_supplicant_win>wpa_supplicant -i
'\Device\NPF_{07654419-8518-4479-9130-1A9D7EE3FF15}' -c wpa_supplicant.conf
-dd
Initializing interface
''\Device\NPF_{07654419-8518-4479-9130-1A9D7EE3FF15}'' co
nf 'wpa_supplicant.conf' driver 'default'
Configuration file 'wpa_supplicant.conf' ->
'C:\local\hostap\wpa_supplicant_win/
wpa_supplicant.conf'
Reading configuration file
'C:\local\hostap\wpa_supplicant_win/wpa_supplicant.conf'
eapol_version=1
ap_scan=1
fast_reauth=1
Line: 323 - start of a new network block
ssid - hexdump_ascii(len=6):
     70 65 61 70 64 63                                 peapdc
key_mgmt: 0x1
eap methods - hexdump(len=2): 15 00
identity - hexdump_ascii(len=8):
     77 65 6e 40 74 65 6d 70                           wen at temp
anonymous_identity - hexdump_ascii(len=15):
     61 6e 6f 6e 79 6d 6f 75 73 40 6f 75 74 65 72      anonymous at outer
password - hexdump_ascii(len=8): [REMOVED]
priority=2 (0x2)
Priority group 2
   id=0 ssid='peapdc'
Initializing interface (2)
''\Device\NPF_{07654419-8518-4479-9130-1A9D7EE3FF15}'
'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
NDIS: 3 adapter names found
NDIS: 3 adapter descriptions found
NDIS: 0 - \Device\NPF_GenericNdisWanAdapter - Generic NdisWan adapter
NDIS: 1 - \Device\NPF_{07654419-8518-4479-9130-1A9D7EE3FF15} - Intel(R)
PRO/Wire
less LAN 2100 3B Mini PCI Adapter (Microsoft's Packet Scheduler)
NDIS: 2 - \Device\NPF_{7479B0AC-7EE0-4CA5-84DA-381C406C0CDE} - Intel(R)
PRO/1000
 MT Mobile Connection (Microsoft's Packet Scheduler)
NDIS: Could not find interface
''\Device\NPF_{07654419-8518-4479-9130-1A9D7EE3FF15}''
Failed to initialize driver interface
rmdir[ctrl_interface]: No such file or directory


-----Original Message-----
From: hostap-bounces+hi_wen=hotmail.com at shmoo.com
[mailto:hostap-bounces+hi_wen=hotmail.com at shmoo.com] On Behalf Of Jouni
Malinen
Sent: Tuesday, April 05, 2005 7:20 PM
To: hostap at shmoo.com
Subject: Re: wpa_supplicant/TTLS/EAP-MD-5 on XP complains "NDIS: Could
notfind interface ... "

On Tue, Apr 05, 2005 at 07:06:28PM -0700, Wen Chen wrote:

> I have not been able to go very far with wpa_supplicant on XP.
> Ndis_events.exe was running when I started wpa_supplicant.  And, my
> supplicant stopped at "NDIS: Could not find interface .".  I have included
> with this email the conf file, win_if_list output, wpa_supplicant output
and
> some system settings.  I'd appreciate some advice.

Which version of WinPcap are you using? Please re-test with 3.1 beta 4
unless you have already tested that.

-- 
Jouni Malinen                                            PGP id EFC895FA
_______________________________________________
HostAP mailing list
HostAP at shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap