Hi Alan, Thanks! Did you change the RLM_MODULE_HANDLED to PW_CHALLENGE in rlm_eap_ttls.c?
Are you familiar with the TLS protocol? Because as that did the trick for EAP-MD5, EAP-MSCHAPV2 still screws up as FreeRadius sends me two EAP-messages in the TLS application data followed by a corrupt message. I am sure this is not because of SecureW2 as the the MAC of the application data after decoding does check out. THIs means Freeradius is sending me something funny... I will debug freeradius a bit more and tell you what I find out. Regards, Tom. > -----Original Message----- > From: Alan DeKok [mailto:[EMAIL PROTECTED] > Sent: Friday, March 05, 2004 7:31 PM > To: [EMAIL PROTECTED] > Subject: Re: EAP-TTLS-EAP-* > > > "Tom Rixom" <[EMAIL PROTECTED]> wrote: > > - The EAP-TTLS module looks at the Access-Challenge and > generates a = > > RLM_MODULE_HANDLED return code > > - The EAP-TTLS module looks at the return code, and because = > > RLM_MODULE_HANDLED is not handled=20 > > it generates an error and the authentication fails... > > > > Does this mean Inner EAP is not supported in EAP-TTLS? > > It means I screwed up. > > The Aegis client works, and is what I used to develop EAP-TTLS. > > The code should be fixed now. > > Alan DeKok. > > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
