Re: [Winpcap-users] Adapting WinPcap’s functionality for connecting to Wi-Fi access points (APs).

George S. Lockwood gslockwood at
Thu Jul 13 23:59:26 GMT 2006

maybe you are able to quickly spot a problem with this...I don't understand
the "NDIS: Could not find interface
Failed to initialize driver interface
Failed to add interface

at the bottom??

here's the whole thing:

C:\Dev Projects\wpa_supplicant-windows-bin-0.4.9>wpa_supplicant.exe
-i'\Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F}' -c
f.txt -d
Initializing interface
''\Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F}'' conf
'wpa_supplicant.conf.txt' driver 'default' ctrl_interface 'N
Configuration file 'wpa_supplicant.conf.txt' -> 'C:\Dev
Reading configuration file 'C:\Dev Projects\wpa_supplicant-windows-bin-0.4.9
Priority group 0
   id=0 ssid='example wpa-psk network'
Initializing interface (2)
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
NDIS: Packet.dll version: 3.0 alpha3
NDIS: Looks like adapter names are in UNICODE
NDIS: 2 adapter names found
NDIS: 2 adapter descriptions found
NDIS: 0 - \Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F} - Intel(R)
PRO/Wireless 2200BG Network Connection (Microsoft's Packet Scheduler)
NDIS: 1 - \Device\NPF_{201016AF-B1FE-4CFD-A410-CD2D3F264D07} - Broadcom
NetXtreme Gigabit Ethernet Driver (Microsoft's Packet Scheduler)
NDIS: Could not find interface
Failed to initialize driver interface
Failed to add interface '\Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F}'
Cancelling scan request

C:\Dev Projects\wpa_supplicant-windows-bin-0.4.9>pause
Press any key to continue . . .

On 7/13/06, George S. Lockwood <gslockwood at> wrote:
> I think the error is about this line
> ctrl_interface=/var/run/wpa_supplicant
> I'm running windows xp and not unix and not sure what is correct...
> On 7/13/06, Bryan Kadzban <bryan at> wrote:
> > George S. Lockwood wrote:
> > Say, do you happen to have the direct link to wpa_supplicant site?
> >
> > On 7/13/06, George S. Lockwood <gslockwood at> wrote:
> >
> >>
> >> Hey thanks.
> >>
> >> Just so I'm sure the wpa_supplicant's Windows port you mention is
> >> using the NIC to provide's not a device driver
> >> itself, right?
> >>
> >> thanks again,
> >>
> >> george
> No, wpa_supplicant is not a driver.  (WinPcap is, but I think you
> already knew that.)  It's a userspace program that you can either run
> directly, or install as a service and run that way.  This:
> is the current URL.  Near the end of that page, there's a set of steps
> that happen when you associate with a wireless LAN; the PacketRequest
> API is used for the following steps:
> - wpa_supplicant requests the kernel driver to scan neighboring BSSes
> - wpa_supplicant requests the kernel driver to associate with the chosen
> - wpa_supplicant configures encryption keys for unicast and broadcast
> There's another option in NDIS for the initial association, too --
> wpa_supplicant can program in an SSID and security settings, and let the
> card associate with any matching AP (this is used when connecting to an
> AP that doesn't include an SSID IE in its beacons).
> Also, I'm pretty sure that the WinPcap packet-send and -capture API is
> used during the following steps:
> - if WPA-EAP: integrated IEEE 802.1X Supplicant completes EAP
> authentication with the authentication server (proxied by the
> Authenticator in the AP)
> - If WPA-EAP: master key is received from the IEEE 802.1X Supplicant
> - wpa_supplicant completes WPA 4-Way Handshake and Group Key Handshake
> with the Authenticator (AP)
> This is not PacketRequest (I don't think), but it is WinPcap.
> _______________________________________________
> Winpcap-users mailing list
> Winpcap-users at
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the Winpcap-users mailing list