Fabrice Beauvir <[EMAIL PROTECTED]> wrote:So sorry, It's my duty fault , it my client throught the AP .
You've managed to convince the server to send packets to itself.No 192.168.6.73 is my AP ..
That's quite a feat.
So,
<shrug> Then the AP is bouncing the Access-Challenge packet back to the server.
The AP SHOULD NOT be sending Access-Challenges to the server. Fix that, and it should work.
is the misconfiguration is due to the fact that my clients are MS type (Windows 2000 and XP) and not the radius server nor my certificates are wrong ?
I mean , it works fine using a Windows 2000 IAS radius server.....
Do you understand ???? ;-)
The radius receive in an acces challenge a EAP "start" that it can't understood .
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
