not logged in | [Login]
Always use radiusd -X
when debugging!
The certificates created using the scripts in the "raddb/certs" directory are known to be compatible with ALL operating systems.
If you see the server send an Access-Challenge, and the client never sends another Access-Request, then
STOP!
The supplicant (client PC) has decided that it doesn't like the server, and has failed to continue the EAP conversation. This usually happens because the client is a WIndows machine, and you did not follow the recommended way to create and install server certificates.
The server certificate has to have special OIDs in it, or else the Microsoft clients will silently fail. See the file "scripts/xpextensions" file for details, or the following page:
http://support.microsoft.com/kb/814394/en-us
For additional Windows XP SP2 issues, see:
http://support.microsoft.com/kb/885453/en-us
The long description of the likely causes is below
For detailed instructions on how to configure EAP, see:
http://deployingradius.com/documents/configuration/eap.html
If you are running version 2.1.10 or later, you may see the following message:
WARNING: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WARNING: !! EAP session for state 0x3e833be03884222b... did not finish! WARNING: !! Please read http://wiki.freeradius.org/Certificate_Compatibility WARNING: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
In that case, follow the instructions given above.
Last edited by Alan DeKok (alandekok), 2020-12-30 14:22:21
Sponsored by Network RADIUS