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

[George S. Lockwood]

Sorry to bug you so much.  you can ignore my 2 earlier emails of today...

Got it to connect to my simple WPA-PSK, TKIP AP, next will be an
EAP-TTLS/CHAP.  This may be harder to figure out config file-wise.

Have you ever seen a EAP-TTLS/CHAP specific config file?

Like I said just earlier, I'd really like to use the wpa_gui but I don't
know how to get it started.  Now when I run it, the secondary cmd console
window showes

Trying to connect to '/var/run/wpa_supplicant/udp
PING failed to connect to wpa_supplicant

over and over

and the UI does not show anything in the adaptor and network dropboxes.

any ideas?

george


On 7/14/06, George S. Lockwood <gslockwood at gmail.com> wrote:
>
> Well, yes removing the 's works, but now another problem:
>
> NDIS: Driver supports OID_802_11_CAPABILITY - NoOfPMKIDs 4
> NoOfAuthEncrPairs 12
> NDIS: driver capabilities: key_mgmt 0xf enc 0xf auth 0x3
> Own MAC address: 00:16:6f:4e:02:c7
> wpa_driver_ndis_set_wpa: enabled=1
> ndis_get_oid: oid=0xd010101 len (6) failed
> ndis_get_oid: oid=0xd010101 len (6) failed
> ndis_get_oid: oid=0xd010101 len (6) failed
> ndis_get_oid: oid=0xd010101 len (6) failed
> Setting scan request: 0 sec 100000 usec
> Added interface \Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F}
> NDIS: Failed to get SSID
> Could not read SSID from driver.
> ndis_get_oid: oid=0xd010101 len (6) failed
> ndis_get_oid: oid=0xd010101 len (6) failed
> ndis_get_oid: oid=0xd010101 len (6) failed
> CTRL-EVENT-TERMINATING - signal 2 received
> Removing interface \Device\NPF_{556DEBC4-B686-4A77-A2D8-7F34F3A5708F}
> State: DISCONNECTED -> DISCONNECTED
> No keys have been configured - skip key clearing
>
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> wpa_driver_ndis_set_wpa: enabled=0
> No keys have been configured - skip key clearing
> Cancelling scan request
>
> I guess I can look up the OID for 0xd010101 any ideas? did you see this?
>
> also the SSID I gave it is valid.  does the key have to be 256 bit
> encoded?
>
> george
>
>
> On 7/13/06, George S. Lockwood <gslockwood at gmail.com> wrote:
> >
> > Thanks man, that's really great you understand it all!
> >
> > 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!
> >
> > I believe I tried -i"Intel" (for my card) but not sure about 's or "s or
> > what.  So I'll try -iIntel first.
> >
> > If I can just get past this, then maybe I'll see whether I have a viable
> > config file.
> >
> > so is the order of steps
> > 1. learn of the NIC's interface.
> > 2. use that with the wpa_supplicant.exe -i -c config.file
> > 3. start ndis_event.exe                             (or is this
> > optional)
> > 4. then wpa_cli                                         (or is this too
> > optional)
> > 4. start wpa_gui
> >
> > use the ui.  Does that sound right?
> >
> > 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
> > >
> > > _supplicant except instead of wpa_supplicant it meantions ......\bfd
> > > or close to that.
> >
> >
> > 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....
> >
> >
> > And Bryan, what about Windows Zero Config (WZC)?
> >
> > 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???
> >
> > On 7/13/06, Bryan Kadzban < bryan at kadzban.is-a-geek.net> wrote:
> >
> > > George S. Lockwood wrote:
> > > 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}''
> >
> > It means you have an extra set of ' characters around the interface
> > name.  ;-)  You don't have to escape the string with single quotes like
> > that, unless you built wpa_supplicant yourself under Cygwin.  (You can
> > also use the first word of the description given for your card, based on
> > its entry in Device Manager; that's what I do.  So for instance, a
> > "Linksys WRT54GS Blah Blah" card could be specified with -iLinksys.)
> >
> > > On 7/13/06, George S. Lockwood <gslockwood at gmail.com> 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...
> >
> > That is still required.  There is no /var/run/wpa_supplicant on windows,
> > but if that line isn't there, then wpa_cli (and wpa_gui) won't work.
> > Without that setting, the UDP socket that wpa_cli and wpa_gui use will
> > not be set up.  The value never used to matter, although I seem to
> > remember some talk about using a named pipe instead of a UDP socket in
> > the release notes for one of the 0.5.x versions, so it might matter if
> > you use the most recent version.
> >
> > (We may want to move this discussion to hostap at epitest.fi, since that's
> > the wpa_supplicant mailing list, or to private mail.  We're starting to
> > get way off topic for winpcap-users.)
> >
> >
> > _______________________________________________
> > Winpcap-users mailing list
> > Winpcap-users at winpcap.org
> > https://www.winpcap.org/mailman/listinfo/winpcap-users
> >
> >
> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winpcap.org/pipermail/winpcap-users/attachments/20060714/4d7da5d6/attachment-0001.htm