Le 29 août 2014 à 10:49, Stefan Paetow a écrit :
Nope.
I use mschapv2 as my inner authentication method in the ttls section in the eap module, and it functions fine. What are you using? 'md5'? 'gtc'?
Stefan
-----Original Message----- From: freeradius-users-bounces+stefan.paetow=ja.net@lists.freeradius.org [mailto:freeradius-users-bounces+stefan.paetow=ja.net@lists.freeradius.org] On Behalf Of Axel Luttgens [...]
With FreeRADIUS 3.0.4 and:
update outer.reply { User-Name = "%{request:User-Name}" }
only, I got the behavior I described in my earlier post... Perhaps did you have to add another setting?
My log excerpts provided examples of the problem I was facing with both TTLS-MSCHAPv2 and PEAP-MSCHAPv2; I also tried TTLS-PAP, with the same negative result. To be sure, do you mean you really manage to retrieve the inner identity with the help of an "update outer.reply" only? Axel