EAP-Message incorrectly decoded as LEAP?

Alan DeKok aland at deployingradius.com
Mon Feb 13 11:20:08 CET 2012


Stefan Winter wrote:
> Maybe something wrong in the dictionary.freeradius.internal:

  Yes.

> This gives LEAP 21 = 0x15 (which is actually TTLS!), and TTLS 25 =0x19
> (which is actually PEAP!), and PEAP 29 = 0x1D (which is actually
> EAP-MSCHAPv2!)

  Solution:

$ egrep VALUE dictionary.freeradius.internal  | grep EAP-Type | awk
'{print "ATTRIBUTE EAP-Type-" $3 " " 1280+$4 " octets"}' >
foo;./format.pl foo

  And copy the resulting file into dictionary.freeradius.internal, to
replace the existing (wrong) EAP-Type-* definitions.

  Alan DeKok.



More information about the Freeradius-Devel mailing list