Joe Vieira wrote:

...

Wed Feb 6 10:43:44 2008 : Error: TLS Alert write:fatal:bad record mac Wed Feb 6 10:43:44 2008 : Error: rlm_eap: SSL error error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac Wed Feb 6 10:43:44 2008 : Error: rlm_eap_tls: SSL_read failed in a system call (-1), TLS session fails.

could someone help me figure out what that means exactly?

Something went wrong with the SSL session. It's big magic...

im running 2.0.1 and i saw those errors at the end of a string of these errors... Wed Feb 6 10:43:04 2008 : Error: rlm_eap: Failed to remember handler! Wed Feb 6 10:43:07 2008 : Error: rlm_eap: Failed to remember handler! and Wed Feb 6 10:43:07 2008 : Error: rlm_eap_tls: Unexpected ACK received the reason i am looking over these logs right now is because the server segfaulted with error 4, 4 seconds after this happened. Joe

Joe Vieira wrote:

im running 2.0.1 and i saw those errors at the end of a string of these errors...

Wed Feb 6 10:43:04 2008 : Error: rlm_eap: Failed to remember handler! Wed Feb 6 10:43:07 2008 : Error: rlm_eap: Failed to remember handler!

Ugh. That means that something is going very wrong inside of the code. It was unable to store the state of the current EAP session, so the session can't be authenticated. I'm not sure why this would be happening. The EAP session storage is keyed off of the "State" variable, which should be unique for every Access-Challenge. If it's accidentally creating the same state for multiple EAP sessions, then that would explain the error... Is this on a 64-bit machine? I've committed some changes to src/modules/rlm_eap/ which *may* help. if not, it should now print more information about what's going wrong... Alan DeKok.