Re: LEAP (was: wpa supplicant/ipw3945, ESSID last char missing)

[Jouni Malinen <jkmaline@cc.hut.fi>]

On Wed, Oct 04, 2006 at 07:29:39PM -0400, Theodore Tso wrote:

> P.S.  Because of all of these changing interfaces, I *still* haven't
> been able to get wpa_supplicant working with LEAP so I can get
> wireless access to in IBM offices using my ipw3945 driver.  I've
> tried, and failed.  Sigh, I guess I'm not smart enough....

This is getting somewhat off topic to the main thread, but anyway, LEAP
is quite an odd beast as far as EAP methods are concerned and the way it
is implemented in Cisco APs makes it even worse.. LEAP can mean so many
different things that it is difficult to give any generic answer to how
to do this. Just about any other wireless security configuration would
be easier to explain.. ;-)

Feel free to write me more details on the configuration used in the
network and I can try to figure out how that would need to be
configured. I would need to know whether LEAP is being used with IEEE
802.1X (dynamic WEP keys; key_mgmt=IEEE8021X in wpa_supplicant)) or with
WPA (key_mgmt=WPA-EAP in wpa_supplicant). In addition, it would be
useful to know whether the APs are configured to require Cisco
prorietary "Network EAP" authentication algorithm (auth_alg=LEAP in
wpa_supplicant) or not. Many of the drivers do not support that at all..
I don't know whether ipw3945 does since I have not tested this myself
and do not remember having heard of a clear report on this being used.

And just hope that the APs do not require Cisco proprietary CKIP or CMIC
encryption algorithms which are most likely not supported by ipw3945 (or
most Linux drivers for that matter)..

-- 
Jouni Malinen                                            PGP id EFC895FA