maybe you are able to quickly spot a problem with this...I don't understand the "NDIS: Could not find interface ''\Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F}''<br>
Failed to initialize driver interface<br>
Failed to add interface '\Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F}'"<br><br>at the bottom??<br><br>here's the whole thing:<br><br>C:\Dev Projects\wpa_supplicant-windows-bin-0.4.9>wpa_supplicant.exe -i'\Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F}' -c wpa_supplicant.co
<br>f.txt -d<br>Initializing interface ''\Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F}'' conf 'wpa_supplicant.conf.txt' driver 'default' ctrl_interface 'N<br>A'<br>Configuration file 'wpa_supplicant.conf.txt' -> 'C:\Dev Projects\wpa_supplicant-
windows-bin-0.4.9/wpa_supplicant.conf.txt'<br>Reading configuration file 'C:\Dev Projects\wpa_supplicant-windows-bin-0.4.9/wpa_supplicant.conf.txt'<br>ctrl_interface='/var/run/wpa_supplicant'<br>ap_scan=1<br>Priority group 0
<br> id=0 ssid='example wpa-psk network'<br>Initializing interface (2) ''\Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F}''<br>EAPOL: SUPP_PAE entering state DISCONNECTED<br>EAPOL: KEY_RX entering state NO_KEY_RECEIVE
<br>EAPOL: SUPP_BE entering state INITIALIZE<br>EAP: EAP entering state DISABLED<br>EAPOL: External notification - portEnabled=0<br>EAPOL: External notification - portValid=0<br>NDIS: Packet.dll version: 3.0 alpha3<br>NDIS: Looks like adapter names are in UNICODE
<br>NDIS: 2 adapter names found<br>NDIS: 2 adapter descriptions found<br>NDIS: 0 - \Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F} - Intel(R) PRO/Wireless 2200BG Network Connection (Microsoft's Packet Scheduler)<br>NDIS: 1 - \Device\NPF_{201016AF-B1FE-4CFD-A410-CD2D3F264D07} - Broadcom NetXtreme Gigabit Ethernet Driver (Microsoft's Packet Scheduler)
<br>NDIS: Could not find interface ''\Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F}''<br>Failed to initialize driver interface<br>Failed to add interface '\Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F}'<br>Cancelling scan request
<br><br>C:\Dev Projects\wpa_supplicant-windows-bin-0.4.9>pause<br>Press any key to continue . . .<br><br><br><br><div><span class="gmail_quote">On 7/13/06, <b class="gmail_sendername">George S. Lockwood</b> <<a href="mailto:gslockwood@gmail.com">
gslockwood@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>I think the error is about this line ctrl_interface=/var/run/wpa_supplicant
<br><br>I'm running windows xp and not unix and not sure what is correct...<br><br><br><div></div><div><span class="q"><span class="gmail_quote">On 7/13/06, <b class="gmail_sendername">
Bryan Kadzban</b> <<a href="mailto:bryan@kadzban.is-a-geek.net" title="mailto:bryan@kadzban.is-a-geek.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">bryan@kadzban.is-a-geek.net</a>> wrote:
</span></span></div><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"></blockquote></div><div><span class="e" id="q_10c6a508061e0d7c_3">
George S. Lockwood wrote:<br>> Say, do you happen to have the direct link to wpa_supplicant site?<br>><br>> On 7/13/06, George S. Lockwood <<a href="mailto:gslockwood@gmail.com" title="mailto:gslockwood@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
gslockwood@gmail.com</a>> wrote:
<br>><br>>><br>>> Hey thanks.<br>>><br>>> Just so I'm sure the wpa_supplicant's Windows port you mention is<br>>> using the NIC to provide connectivity...it's not a device driver<br>>> itself, right?
<br>>><br>>> thanks again,<br>>><br>>> george<br><br>No, wpa_supplicant is not a driver. (WinPcap is, but I think you<br>already knew that.) It's a userspace program that you can either run<br>directly, or install as a service and run that way. This:
<br><br><a href="http://hostap.epitest.fi/wpa_supplicant/" title="http://hostap.epitest.fi/wpa_supplicant/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://hostap.epitest.fi/wpa_supplicant/</a>
<br><br>is the current URL. Near the end of that page, there's a set of steps<br>that happen when you associate with a wireless LAN; the PacketRequest
<br>API is used for the following steps:<br><br>- wpa_supplicant requests the kernel driver to scan neighboring BSSes<br>- wpa_supplicant requests the kernel driver to associate with the chosen BSS<br>- wpa_supplicant configures encryption keys for unicast and broadcast
<br><br>There's another option in NDIS for the initial association, too --<br>wpa_supplicant can program in an SSID and security settings, and let the<br>card associate with any matching AP (this is used when connecting to an
<br>AP that doesn't include an SSID IE in its beacons).<br><br>Also, I'm pretty sure that the WinPcap packet-send and -capture API is<br>used during the following steps:<br><br>- if WPA-EAP: integrated IEEE 802.1X Supplicant completes EAP
<br>authentication with the authentication server (proxied by the<br>Authenticator in the AP)<br>- If WPA-EAP: master key is received from the IEEE 802.1X Supplicant<br>- wpa_supplicant completes WPA 4-Way Handshake and Group Key Handshake
<br>with the Authenticator (AP)<br><br>This is not PacketRequest (I don't think), but it is WinPcap.<br><br><br></span></div><div><span class="q">_______________________________________________<br>Winpcap-users mailing list
<br><a href="mailto:Winpcap-users@winpcap.org" title="mailto:Winpcap-users@winpcap.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Winpcap-users@winpcap.org</a><br><a href="https://www.winpcap.org/mailman/listinfo/winpcap-users" title="https://www.winpcap.org/mailman/listinfo/winpcap-users" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
https://www.winpcap.org/mailman/listinfo/winpcap-users</a><br><br><br><br></span></div><div></div><br>
</div></blockquote></div><br>