[strongSwan] EAP TTLS MSCHAPv2 authentication error : expected AVP_EAP_MESSAGE but received 462
tobias at strongswan.org
Tue Apr 19 15:33:45 CEST 2016
> Does it mean that strongswan's EAP TTLS plugin is only compatible with
> radius attributes ?
RFC 5281 (EAP-TTLSv0 ) only describes the encapsulation of EAP
messages in 'EAP-Message' RADIUS AVPs. Actually, the list of allowed
AVPs is very specific (see section 13). The 'EAP-Payload' Diameter AVP
defined in RFC 4072 (released three years earlier ) is not mentioned
at all. And the registry for allowed AVPs was never extended later
either . So it seems what the Cisco ePDG is doing is not RFC compliant.
More information about the Users