wpa_supplicant Windows port, again (WPA2)
Mon Sep 26 19:45:47 PDT 2005
On Mon, Sep 26, 2005 at 06:36:14PM -0400, Bryan Kadzban wrote:
> Well, 0.4.5 did fix the problem I was having. It successfully completes
> the 4-way handshake now, every time I've tried it.
That's nice to hear. I did not see much improvements with my AP, but
then again, I did not test with a Cisco AP that may use a different
retry timeout with the EAPOL-Key frames.
> That's without turning debug off, too. However, on system startup, I
> had to turn it off, because on the machine I tested it on, there seemed
> to be a race between wpa_supplicant and DHCP, or something. Turning
> debug off helped a lot (but didn't quite totally fix the problem;
> netlogon still starts a little too early). But I'll be looking into
> that a lot more tomorrow; I think it has something to do with the DHCP
Interesting.. If nothing else, you could try triggering DHCP to renew
the lease after the connection has been completed.
> Anyway, the one thing I would like to know for sure is, after the
> CTRL-EVENT-CONNECTED string gets sent to all connected frontends, should
> the machine be able to pass network traffic? (I.e., am I watching for
> the right string from wpa_supplicant?) If not, is there something else
> that I should be watching for that signals when the card is capable of
> using the network?
Yes, that is indeed the event message that is sent when both pairwise
and group keys have been configured and the connection is ready for data
traffic. This would also be the point when DHCP client should start
trying to get/renew lease.
Jouni Malinen PGP id EFC895FA
More information about the Hostap