Supplicant used different EAP type 13: (TLS)
Mon Mar 24 10:17:41 PDT 2008
On Mon, Mar 24, 2008 at 03:03:26PM +0100, Chr wrote:
> WPA-EAP (WPA+RSN) TLS - madwifi-ng-r3403 (AR5416/AR5008)
> and hostapd 0.6.3 (built-in eap-server)...
> The most clients can connect, ping & surf without any problems,
> But all Windows XP (Only XP!) ones generate a strange error
> with the default TLS setting! (The non-default
> settings works too! but take a look at the error first).
What is the difference between "default" and "non-default" settings?
> authentication failed - EAP type: 0 (Unknown)
> Supplicant used different EAP type: 13 (TLS)
> With any other client (like Vista/wpa_supp/Apple) it looks like this:
> IEEE 802.11: associated
> WPA: pairwise key handshake completed (RSN)
> IEEE 802.1X: authenticated - EAP type: 0 (Unknown)
> WPA: group key handshake completed (RSN))
It looks like the EAP types are not updated properly when using the
build-in EAP server (instead of external RADIUS authentication server).
> Now, according to the log... the authentication failed because
> the Windows XP client _really_ used TLS... while all other clients
> are using a "Unkown type" that is actually TLS because the AP only
> allows TLS authentication?!
Well, no. This is likely a bug in hostapd that may only affect the debug
output. Could you please send a detailed debug log (-dd on command line)
from hostapd showing the failed authentication with Windows XP?
Jouni Malinen PGP id EFC895FA
More information about the Hostap