<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css">body { font-family:'Helvetica'; font-size:12px}</style>
</head>
<body><div>Alan,</div><div><br></div><div>Thank you for your answer.</div><div>I know you must be right, but I still didn't manage to have it working again.</div><div><br></div><div>I'm still getting troubles with TLS exchanges and don't know enough of it to be able to debug it.</div><div><br></div><div>I read tons of threads where Alan DeKok kept repeating to read his website, as well as using default configuration which is know to work.</div><div>I also read that those EAP sessions not finishing where only due to certs problems or fragmentation.</div><div>Certs are fine, fragmentation should be ok.</div><div><br></div><div>I completely started the AP's configuration again, from factory defaults, not using the backup, only setting the strict minimum (WPA2-Enterprise, shared key, radius IP), the remaining parameters being left to default values.</div><div><br></div><div>I still have no clue on what is going wrong.</div><div><br></div><div>Best regards,</div><div><br></div><div>Benjamin</div><div><br></div><div><br></div><div><br></div><div>Le Thu, 21 Jun 2012 20:32:02 +0200, Alan Buxey <A.L.M.Buxey@lboro.ac.uk> a écrit:<br></div><br><blockquote style="margin: 0 0 0.80ex; border-left: #0000FF 2px solid; padding-left: 1ex"> If you haven't touched FR then don't look there as that's not what has changed. Your problem has already been identified - the bit that got changed.<br>
<br>
<br>
No changes should be made on FR or on the clients<br>
<br>
<br>
alan<br>
<br>
</blockquote><br></body></html>