Bug#366937: [pkg-wpa-devel] Bug#366937: wpasupplicant fails to run due to EAP methods with same EAP-type

Kel Modderman kelrin at tpg.com.au
Fri May 12 09:29:33 UTC 2006


Arjan Oosting wrote:
> Package: wpasupplicant
> Version: 0.5.3-1
> Severity: normal
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> I have just upgraded wpasupplicant to the version in experimental to
> give it a try, but it fails to run and gives the following error
> message: 
>
> Failed to register EAP methods
> Two or more EAP methods used the same EAP type.
> Failed to initialize wpa_supplicant
>
> I guess this is due to the following change made upstream:
>
> * added support for EAP-SAKE (no EAP method number allocated yet, so
>   this is using the same experimental type 255 as EAP-PSK)
>
> Because both EAP-SAKE and EAP-PSK are enabled during build, we get a
> conflict, because both use the same EAP-type.
>
> I have build wpasupplicant without the support for EAP-SAKE (by
> updating the config dpatch) and then it runs fine.
>
>   


Yep, stupid mistake on my part.

http://lists.alioth.debian.org/pipermail/pkg-wpa-devel/2006-May/000405.html

Will be better in next upload.

Thanks, Kel.




More information about the Pkg-wpa-devel mailing list