EAP-Message incorrectly decoded as LEAP?

[Stefan Winter]

Hi,

yep, that did the trick.

Could these changes make it to 2.1.13 / 2.2.0?

Stefan

On 13.02.2012 11:20, Alan DeKok wrote:
> 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.
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html


-- 
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et 
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473