Working around broken EAP client

Alan DeKok aland at
Tue Jun 11 14:59:55 CEST 2013

Gordon Ross wrote:
> [mschap] ERROR: User-Name (68983 at is not the same as MS-CHAP Name (68983) from EAP-MSCHAPv2

  It appears that behavior is allowed.  I've had discussions with the
people doing the standards.  And the MS-CHAP identity has *no* relation
to the EAP-Identity.

  It's insane, but that's how it works.

  I think for v2.2.1, it's best to make that check configurable, instead
of an error.

  Alan DeKok.

More information about the Freeradius-Users mailing list