https://bugzilla.novell.com/show_bug.cgi?id=584028
https://bugzilla.novell.com/show_bug.cgi?id=584028#c10
Andreas Hartmann changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
InfoProvider|andihartmann@freenet.de |
--- Comment #10 from Andreas Hartmann 2011-02-27 08:25:03 UTC ---
One more thing:
I'm using WPA2-TLS to connect to the WLAN. The initiation of the TLS connection
does take long time, because the supplicant doesn't send a EAPOL Start packet
to the AP.
In detail:
This is the way, the initiation of the connection works fine and smooth (this
is done within the same second directly after association):
EAPOL Start [802.1X] Authentication (sent by supplicant)
EAP Request, Identity [RFC3748] (sent by AP)
EAP Response, Identity [RFC3748] (sent by supplicant)
EAP Request, EAP-TLS [RFC5216] [Aboba] sent by AP
TLSv1 Client Hello (sent by supplicant)
TLSv1 Server Hello (sent by AP)
..
(I can see this with ralinks rt3572sta driver, version 2.4.0.2)
rt61pci works like this:
EAP Request, Identity [RFC3748] (sent by AP)
EAP Response, Identity [RFC3748] (sent by supplicant)
30 s later
EAP Request, Identity [RFC3748] (sent by AP)
EAP Response, Identity [RFC3748] (sent by supplicant)
EAP Request, EAP-TLS [RFC5216] [Aboba] sent by AP
TLSv1 Client Hello (sent by supplicant)
TLSv1 Server Hello (sent by AP)
..
(there could be even more tries until the AP sends the EAP-TLS-Request.)
Could you please fix this, too?
wpa_supplicant is always wpa_supplicant-0.7.3-12.1.i586.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.