<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Nur Text Zchn";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.NurTextZchn
{mso-style-name:"Nur Text Zchn";
mso-style-priority:99;
mso-style-link:"Nur Text";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1662614477;
mso-list-type:hybrid;
mso-list-template-ids:736681856 -643790980 67567619 67567621 67567617 67567619 67567621 67567617 67567619 67567621;}
@list l0:level1
{mso-level-start-at:103;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=DE link=blue vlink=purple><div class=WordSection1><p class=MsoPlainText><span lang=EN-US>Hi!<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>I've a problem with 802.1x and EAP-TLS where I'm not quite sure who is responsible for this problem and how to work around it. I hope someone can help me – I couldn’t find anything with Google and I just can’t believe I’m the first guy with this problem. The setup is following.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>- Windows 7 SP1 Client with 802.1x and EAP-TLS configurated<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>- Extreme Networks 450e Switches </span><span lang=EN-US style='font-family:Wingdings'>à</span><span lang=EN-US> LAN based 802.1x<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>- Freeradius 2.1.12-3.el5 on RHEL5 only TLS as EAP type configured/allowed <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>The problem now is that in 1/3 of the clients boots (done over 40 times with a tap devices running as sniffer) the Windows Client sends an<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>response: Legacy Nak (Response only) [RFC3748] with the wish for PEAP. After this the freeradius Server sends a reject ([eap] NAK asked for unsupported type PEAP). With the next identity request the Client does an clean EAP-TLs handshake, but the switch already put the client into the reject network.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>Here is the communication flow in these cases (Wireshark): Line 5 / Packet 54 is the problem<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-family:"Courier New"'><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'>No. Time Source Destination Protocol Length Info<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 9 27.371093 switch --> client EAP 60 Request, Identity [RFC3748]<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 51 43.669530 switch --> client EAP 60 Request, Identity [RFC3748]<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 52 43.693510 client --> switch EAP 60 Response, Identity [RFC3748]<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 53 43.699498 switch --> client EAP 60 Request, EAP-TLS [RFC5216] [Aboba]<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 54 43.700496 client --> switch EAP 60 Response, Legacy Nak (Response only) [RFC3748]<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 84 44.639980 switch --> client EAP 60 Request, Identity [RFC3748]<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 85 44.646980 client --> switch EAP 60 Response, Identity [RFC3748]<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 86 44.652974 switch --> client EAP 60 Request, EAP-TLS [RFC5216] [Aboba]<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 87 44.758887 client --> switch TLSv1 123 Client Hello<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 88 44.765875 switch --> client TLSv1 1042 Server Hello, Certificate, Certificate Request, Server Hello Done<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 89 44.766875 client --> switch EAP 60 Response, EAP-TLS [RFC5216] [Aboba]<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 90 44.772880 switch --> client TLSv1 1042 Server Hello, Certificate, Certificate Request, Server Hello Done<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 91 44.772892 client --> switch EAP 60 Response, EAP-TLS [RFC5216] [Aboba]<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 92 44.778868 switch --> client TLSv1 1042 Server Hello, Certificate, Certificate Request, Server Hello Done<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 93 44.779865 client --> switch EAP 60 Response, EAP-TLS [RFC5216] [Aboba]<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 94 44.784859 switch --> client TLSv1 177 Server Hello, Certificate, Certificate Request, Server Hello Done<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 95 44.787862 client --> switch TLSv1 1510 Certificate, Client Key Exchange, Certificate Verify, Change Cipher Spec, Encrypted Handshake Message<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 96 44.793854 switch --> client EAP 60 Request, EAP-TLS [RFC5216] [Aboba]<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 97 44.793861 client --> switch TLSv1 530 Certificate, Client Key Exchange, Certificate Verify, Change Cipher Spec, Encrypted Handshake Message<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'> 98 44.807887 switch --> client TLSv1 87 Change Cipher Spec, Encrypted Handshake Message<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'>102 44.818881 client --> switch EAP 60 Response, EAP-TLS [RFC5216] [Aboba]<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'>103 44.855827 switch --> client EAP 60 Success<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><span lang=EN-US>It seems to be a timing issue …. anyway:<o:p></o:p></span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText style='margin-left:36.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span lang=EN-US><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span lang=EN-US>Windows 7 is configured to EAP-TLS with GPOs <o:p></o:p></span></p><p class=MsoPlainText style='margin-left:36.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span lang=EN-US><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span lang=EN-US>I’ve uninstalled anti-virus, behavior detection software<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>In the 2/3 of the cases it works the Client does not send a NAK, so I believe it is a client problem but it’s Windows 7 … there must be thousands of installs with Windows 7 and 802.1x EAP/TLS. Would it help if freeradius ignores the EAP-NAK packets? Any help appreciated!<o:p></o:p></span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><span style='mso-fareast-language:DE'>Mit freundlichen Grüßen<o:p></o:p></span></p><p class=MsoPlainText><span style='mso-fareast-language:DE'>Robert Penz<o:p></o:p></span></p><p class=MsoPlainText><span style='mso-fareast-language:DE'><o:p> </o:p></span></p><p class=MsoPlainText><span style='mso-fareast-language:DE'>--------------------------------------------------------------<o:p></o:p></span></p><p class=MsoPlainText><span style='mso-fareast-language:DE'>Dipl.Inf. Robert Penz<o:p></o:p></span></p><p class=MsoPlainText><span style='mso-fareast-language:DE'>DVT - Daten-Verarbeitung-Tirol GmbH<o:p></o:p></span></p><p class=MsoPlainText><span style='mso-fareast-language:DE'>Adamgasse 22, 6020 Innsbruck<o:p></o:p></span></p><p class=MsoPlainText><span style='mso-fareast-language:DE'>Tel: +43 (0)512 508 3334 / Fax: +43 (0)512 508 3355<o:p></o:p></span></p><p class=MsoPlainText><span style='mso-fareast-language:DE'>E-Mail: robert.penz@tirol.gv.at<o:p></o:p></span></p><p class=MsoPlainText><span style='mso-fareast-language:DE'><o:p> </o:p></span></p><p class=MsoPlainText><o:p> </o:p></p></div></body></html>