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="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
_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><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>> 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 href="mailto:gslockwood@gmail.com">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 href="mailto:hostap@epitest.fi">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>_______________________________________________<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>