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><span class="gmail_quote">On 7/13/06, <b class="gmail_sendername">
Bryan Kadzban</b> <<a href="mailto:bryan@kadzban.is-a-geek.net">bryan@kadzban.is-a-geek.net</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;">
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">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/">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>_______________________________________________<br>Winpcap-users mailing list<br><a href="mailto:Winpcap-users@winpcap.org">
Winpcap-users@winpcap.org</a><br><a href="https://www.winpcap.org/mailman/listinfo/winpcap-users">https://www.winpcap.org/mailman/listinfo/winpcap-users</a><br><br><br><br></blockquote></div><br>