Hi everyone, we have a strange problem going on here. We have a Windows 8 Client that tries to join our WLAN using EAP TLS Auth. The Server writes to its logfiles that everything seems to be ok and he is willing to give this system a: ACCESS-ACCEPT Thu Apr 3 06:05:55 2014 : Auth: Login OK: [host/KP4101] (from client kc1034 port 807 cli 5C-51-4F-D9-5E-6D) In a traffic dump I can see the following packages to the end of the conversation: PacketNo Length Info 17 825 Access-Request 18 1132 Access-Challenge <<<< In this Packet is EAP-TLS Length of 1626 mentioned but its size is only 1024, shouldn't the server send the missing 602 bytes in response to the next request instead of the Access-Accept? 19 219 Access-Request 20 232 Access-Accept Because on the other side we have the client on there are the following log entries: 0086 [5060] 03-11 08:41:37:364: >> Received Request (Code: 1) packet: Id: 11, Length: 1024, Type: 13, TLS blob length: 1626. Flags: LM <<<< The client receives the 1024 bytes from packet no. 18, I assume and he is aware of the fact that the TLS blob is 1626 bytes. 0087 [5060] 03-11 08:41:37:364: EapTlsCMakeMessage, state(3) flags (0x1400) 0090 [5060] 03-11 08:41:37:364: << Sending Response (Code: 2) packet: Id: 11, Length: 6, Type: 13, TLS blob length: 0. Flags: <<<< The client is responding 0093 [5060] 03-11 08:41:37:379: >> Received Success (Code: 3) packet: Id: 11, Length: 4, Type: 0, TLS blob length: 0. Flags: <<<< The client receives a Success ( Access-Accept ), but aren't we expecting 602 Bytes here? 0094 [5060] 03-11 08:41:37:379: EapTlsCMakeMessage, state(3) flags (0x1410) 0095 [5060] 03-11 08:41:37:379: Code 3 unexpected in state SentFinished <<<< The client wonders about something ( 602 missing bytes?) and cancels the whole authentication process to restart it again 5 seconds later. 0096 [5060] 03-11 08:41:37:379: EapTlsEnd 0097 [5060] 03-11 08:41:37:379: EapTlsEnd(host/kp5975.hauni.koerber.de) This process loops for about 5 minutes than the client seems to be feed up and stops its joining efforts. In my lab I have a Cisco Access Point with a brand new IOS Version 15.2(4)JB4. Freeradius comes in its version 2.1.1 and the client runs Windows8 we also have a Windows8.1 client but the problem is the same. Can anyone bring a clarification to this? The exact same setup is working with Windows7 clients without any problems. Regards from Hamburg/Germany Kai
kai.zemke@hauni.com wrote:
we have a strange problem going on here. We have a Windows 8 Client that tries to join our WLAN using EAP TLS Auth.
And you didn't post the FreeRADIUS debug mode. Why. Just... why?
In a traffic dump I can see the following packages to the end of the conversation:
The only relevant traffic dump is "radiusd -X".
Can anyone bring a clarification to this?
Without a debug log, no.
The exact same setup is working with Windows7 clients without any problems.
Then the problem is likely that Windows 8 is broken. Alan DeKok.
Okay so here we go with a "radiusd -X" Attached to this mail. Regards Kai -----Ursprüngliche Nachricht----- Von: freeradius-users-bounces+kai.zemke=hauni.com@lists.freeradius.org [mailto:freeradius-users-bounces+kai.zemke=hauni.com@lists.freeradius.org] Im Auftrag von Alan DeKok Gesendet: Donnerstag, 3. April 2014 15:08 An: FreeRadius users mailing list Betreff: Re: freeradius EAP TLS / Windows 8 Client kai.zemke@hauni.com wrote:
we have a strange problem going on here. We have a Windows 8 Client that tries to join our WLAN using EAP TLS Auth.
And you didn't post the FreeRADIUS debug mode. Why. Just... why?
In a traffic dump I can see the following packages to the end of the conversation:
The only relevant traffic dump is "radiusd -X".
Can anyone bring a clarification to this?
Without a debug log, no.
The exact same setup is working with Windows7 clients without any problems.
Then the problem is likely that Windows 8 is broken. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Am Donnerstag, 3. April 2014, 16:30:08 schrieb kai.zemke@hauni.com:
Okay so here we go with a "radiusd -X" Attached to this mail.
Regards Kai
-----Ursprüngliche Nachricht----- Von: freeradius-users-bounces+kai.zemke=hauni.com@lists.freeradius.org [mailto:freeradius-users-bounces+kai.zemke=hauni.com@lists.freeradius.org] Im Auftrag von Alan DeKok Gesendet: Donnerstag, 3. April 2014 15:08 An: FreeRadius users mailing list Betreff: Re: freeradius EAP TLS / Windows 8 Client
kai.zemke@hauni.com wrote:
we have a strange problem going on here. We have a Windows 8 Client that tries to join our WLAN using EAP TLS Auth.
Hi, I don't think the problem is on the FR side, since the debug output show that it sends a Access-Accept in the end. Mit freundlichen Grüßen, Michael Schwartzkopff -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Le 03/04/2014 15:08, Alan DeKok a écrit :
The exact same setup is
working with Windows7 clients without any problems. Then the problem is likely that Windows 8 is broken.
Or the bug is in Cisco ? https://supportforums.cisco.com/document/113836/windows-8-clients-cant-assoc... I don't know if this bug report apply to your case ? Alain -- Administrateur Système/Réseau Laboratoire de Photonique et Nanostructures (LPN/CNRS - UPR20) Centre de Recherche Alcatel Data IV - Marcoussis route de Nozay - 91460 Marcoussis Tel : 01-69-63-61-34
While i was investigating i also found this bugs about windows 8 and cisco APs. But they all apply to setups with a centralized access point management. I have only autonomous standalone access points. So from my point of view... this bug does not apply to my setup. Regards Kai ________________________________________ Von: freeradius-users-bounces+kai.zemke=hauni.com@lists.freeradius.org [freeradius-users-bounces+kai.zemke=hauni.com@lists.freeradius.org] im Auftrag von Alain Péan [alain.pean@lpn.cnrs.fr] Gesendet: Donnerstag, 3. April 2014 16:43 An: freeradius-users@lists.freeradius.org Betreff: Re: freeradius EAP TLS / Windows 8 Client Le 03/04/2014 15:08, Alan DeKok a écrit :
The exact same setup is
working with Windows7 clients without any problems. Then the problem is likely that Windows 8 is broken.
Or the bug is in Cisco ? https://supportforums.cisco.com/document/113836/windows-8-clients-cant-assoc... I don't know if this bug report apply to your case ? Alain -- Administrateur Système/Réseau Laboratoire de Photonique et Nanostructures (LPN/CNRS - UPR20) Centre de Recherche Alcatel Data IV - Marcoussis route de Nozay - 91460 Marcoussis Tel : 01-69-63-61-34 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Le 03/04/2014 19:39, kai.zemke@hauni.com a écrit :
While i was investigating i also found this bugs about windows 8 and cisco APs. But they all apply to setups with a centralized access point management. I have only autonomous standalone access points. So from my point of view... this bug does not apply to my setup.
I already read the report of such a behaviour with windows 8 and a Netgear wireless access point (wnap300). If you have another wireless AP available, for example aruba, you should try with it. Another test is to try PKIP instead of WPA2 on your AP ssid.
participants (4)
-
Alain Péan -
Alan DeKok -
kai.zemke@hauni.com -
Michael Schwartzkopff