<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2912" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>oid 0x0d010101 is OID_802_11_BSSID, and from the trace you
sent, it seems that wpa_supplicant is querying the current BSSID to the wifi
card (the function is called xxx_get_xxx)</FONT><FONT size=2>. From the MSDN
documentation, a query for this OID will fail (in infrastructure mode) if the
NIC is not associated to an AP.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Hope it helps</FONT></DIV>
<DIV><FONT size=2>GV</FONT></DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=gslockwood@gmail.com href="mailto:gslockwood@gmail.com">George S.
Lockwood</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=winpcap-users@winpcap.org
href="mailto:winpcap-users@winpcap.org">winpcap-users@winpcap.org</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, July 14, 2006 7:03 AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [Winpcap-users] Adapting
WinPcap’s functionality for connecting to Wi-Fi access points (APs).</DIV>
<DIV><BR></DIV>Well, yes removing the 's works, but now another
problem:<BR><BR>NDIS: Driver supports OID_802_11_CAPABILITY - NoOfPMKIDs 4
NoOfAuthEncrPairs 12<BR>NDIS: driver capabilities: key_mgmt 0xf enc 0xf auth
0x3<BR>Own MAC address: 00:16:6f:4e:02:c7 <BR>wpa_driver_ndis_set_wpa:
enabled=1<BR><SPAN style="FONT-WEIGHT: bold">ndis_get_oid: oid=0xd010101 len
(6) failed</SPAN><BR style="FONT-WEIGHT: bold"><SPAN
style="FONT-WEIGHT: bold">ndis_get_oid: oid=0xd010101 len (6) failed
</SPAN><BR style="FONT-WEIGHT: bold"><SPAN
style="FONT-WEIGHT: bold">ndis_get_oid: oid=0xd010101 len (6) failed</SPAN><BR
style="FONT-WEIGHT: bold"><SPAN style="FONT-WEIGHT: bold">ndis_get_oid:
oid=0xd010101 len (6) failed </SPAN><BR>Setting scan request: 0 sec 100000
usec<BR>Added interface
\Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F}<BR>NDIS: Failed to get
SSID<BR>Could not read SSID from driver.<BR>ndis_get_oid: oid=0xd010101 len
(6) failed <BR>ndis_get_oid: oid=0xd010101 len (6) failed<BR>ndis_get_oid:
oid=0xd010101 len (6) failed<BR>CTRL-EVENT-TERMINATING - signal 2
received<BR>Removing interface
\Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F}<BR>State: DISCONNECTED
-> DISCONNECTED <BR>No keys have been configured - skip key
clearing<BR>EAPOL: External notification - portEnabled=0<BR>EAPOL: External
notification - portValid=0<BR>wpa_driver_ndis_set_wpa: enabled=0<BR>No keys
have been configured - skip key clearing <BR>Cancelling scan request<BR><BR>I
guess I can look up the OID for <SPAN
style="FONT-WEIGHT: bold">0xd010101</SPAN> any ideas? did you see this?
<BR><BR>also the SSID I gave it is valid. does the key have to be 256
bit encoded? <BR><BR>george<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="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>Thanks man, that's really great you understand it all!<BR><BR>I tried
removing the braces and the prefix to the guid part, tomorrow morning I'll
remove the apostrophes. I think I included the 's because they were in
an example! <BR><BR>I believe I tried -i"Intel" (for my card) but not sure
about 's or "s or what. So I'll try -iIntel first.<BR><BR>If I can
just get past this, then maybe I'll see whether I have a viable config file.
<BR><BR>so is the order of steps<BR>1. learn of the NIC's interface.<BR>2.
use that with the wpa_supplicant.exe -i -c config.file<BR>3. start
ndis_event.exe
(or is this optional)<BR>4. then
wpa_cli
(or is this too optional) <BR>4. start wpa_gui <BR><BR>use the ui.
Does that sound right?<BR><BR>so far when I've started ndis_event.exe, it
seems to give me an error that is relatable to the
ctrl_interface=/var/run/wpa
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">_supplicant
except instead of wpa_supplicant it meantions ......\bfd or close to
that.</BLOCKQUOTE>
<DIV><BR>Without the documentation in front of me, I don't know what this
exe does, but is sounds like it somehow captures NIC messages such as how a
connection proceeds.... <BR></DIV><BR><BR>And Bryan, what about Windows Zero
Config (WZC)? <BR><BR>I guess I see for myself but perhaps you have some
insight. any other tricks you've discovered in your journey into this
supplicant s/w???<BR><BR>
<DIV></DIV>
<DIV><SPAN class=q><SPAN class=gmail_quote>On 7/13/06, <B
class=gmail_sendername>Bryan Kadzban</B> <<A
title=mailto:bryan@kadzban.is-a-geek.net
onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:bryan@kadzban.is-a-geek.net" target=_blank>
bryan@kadzban.is-a-geek.net</A>> wrote:</SPAN></SPAN></DIV>
<DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"></BLOCKQUOTE></DIV>
<DIV><SPAN class=e id=q_10c6b2d20c60e166_3>George S. Lockwood wrote:<BR>>
maybe you are able to quickly spot a problem with this...I don't<BR>>
understand the "NDIS: Could not find interface<BR>>
''\Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F}'' <BR><BR>It means you
have an extra set of ' characters around the
interface<BR>name. ;-) You don't have to escape the
string with single quotes like<BR>that, unless you built wpa_supplicant
yourself under Cygwin. (You can <BR>also use the first word of
the description given for your card, based on<BR>its entry in Device
Manager; that's what I do. So for instance, a<BR>"Linksys WRT54GS
Blah Blah" card could be specified with -iLinksys.) <BR><BR>> On 7/13/06,
George S. Lockwood <<A title=mailto:gslockwood@gmail.com
onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:gslockwood@gmail.com"
target=_blank>gslockwood@gmail.com</A>> wrote: <BR>><BR>>> I
think the error is about this line<BR>>>
ctrl_interface=/var/run/wpa_supplicant <BR>>><BR>>> I'm running
windows xp and not unix and not sure what is correct...<BR><BR>That is still
required. There is no /var/run/wpa_supplicant on windows,<BR>but
if that line isn't there, then wpa_cli (and wpa_gui) won't work. <BR>Without
that setting, the UDP socket that wpa_cli and wpa_gui use will<BR>not be set
up. The value never used to matter, although I seem
to<BR>remember some talk about using a named pipe instead of a UDP socket
in<BR>the release notes for one of the 0.5.x versions, so it might matter
if<BR>you use the most recent version.<BR><BR>(We may want to move this
discussion to <A title=mailto:hostap@epitest.fi
onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:hostap@epitest.fi" target=_blank>hostap@epitest.fi</A>, since
that's <BR>the wpa_supplicant mailing list, or to private
mail. We're starting to<BR>get way off topic for
winpcap-users.)<BR><BR><BR></SPAN></DIV>
<DIV><SPAN
class=q>_______________________________________________<BR>Winpcap-users
mailing list <BR><A title=mailto:Winpcap-users@winpcap.org
onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:Winpcap-users@winpcap.org"
target=_blank>Winpcap-users@winpcap.org</A><BR><A
title=https://www.winpcap.org/mailman/listinfo/winpcap-users
onclick="return top.js.OpenExtLink(window,event,this)"
href="https://www.winpcap.org/mailman/listinfo/winpcap-users"
target=_blank>https://www.winpcap.org/mailman/listinfo/winpcap-users</A><BR><BR><BR><BR></SPAN></DIV>
<DIV></DIV><BR></DIV></BLOCKQUOTE></DIV><BR>
<P>
<HR>
<P></P>_______________________________________________<BR>Winpcap-users
mailing
list<BR>Winpcap-users@winpcap.org<BR>https://www.winpcap.org/mailman/listinfo/winpcap-users<BR></BLOCKQUOTE></BODY></HTML>