Hi,
I have noticed that when authenticating using TTLS/MSCHAPv2 that the
outer-identity is used in the RADIUS reply packet even if the
use_tunneled_reply is set to yes for TTLS in eap.conf
Does anyone know the reason for this?
Thanks
Scott Armitage
PGP.sig
Description: This is a digitally
Scott Armitage s.p.armit...@lboro.ac.uk wrote:
I have noticed that when authenticating using TTLS/MSCHAPv2 that the
outer-identity is used in the RADIUS reply packet even if the
use_tunneled_reply is set to yes for TTLS in eap.conf
Does anyone know the reason for this?
TLS session
On 20/07/11 11:26, Scott Armitage wrote:
Hi,
I have noticed that when authenticating using TTLS/MSCHAPv2 that the
outer-identity is used in the RADIUS reply packet even if the
use_tunneled_reply is set to yes for TTLS in eap.conf
That's not what we see:
[ttls] Using saved attributes from the
On 20 Jul 2011, at 13:39, Phil Mayers wrote:
On 20/07/11 11:26, Scott Armitage wrote:
Hi,
I have noticed that when authenticating using TTLS/MSCHAPv2 that the
outer-identity is used in the RADIUS reply packet even if the
use_tunneled_reply is set to yes for TTLS in eap.conf
That's not
On 20 Jul 2011, at 12:49, Alexander Clouter wrote:
Scott Armitage s.p.armit...@lboro.ac.uk wrote:
I have noticed that when authenticating using TTLS/MSCHAPv2 that the
outer-identity is used in the RADIUS reply packet even if the
use_tunneled_reply is set to yes for TTLS in eap.conf
On 20/07/11 14:27, Scott Armitage wrote:
[ttls] Using saved attributes from the original Access-Accept
Reply-Message = Authenticated by Test ORPS
Ok, looking at the debug the reason this is happening is that you are
doing TTLS/MSCHAP, as opposed to TTLS/EAP-MSCHAP.
[ttls] Got
On 20 Jul 2011, at 15:40, Phil Mayers wrote:
On 20/07/11 14:27, Scott Armitage wrote:
[ttls] Using saved attributes from the original Access-Accept
Reply-Message = Authenticated by Test ORPS
Ok, looking at the debug the reason this is happening is that you are
doing TTLS/MSCHAP,
7 matches
Mail list logo