[Prism54-devel] Re: Client mode with extended MLME level

[Jouni Malinen]

On Sat, Jan 10, 2004 at 10:26:32PM -0800, hello world wrote:

>       You might well try to send Authentication
> response in the case statement for
> DOT11_OID_AUTHENTICATEEX (in the function
> prism54_process_trap_helper) as is being done in
> DOT11_OID_AUTHENTICATE. This should help move the
> state of the STA to Authenticated and move on the
> Association phase.

This is done only in AP mode. The STA was already authenticated
(DOT11_STATE_AUTH) at this point and DOT11_OID_AUTHENTICATEEX is not
needed anymore (and in fact, it will just crash/confuse the firmware).

> Also, code need to be added to the
> DOT11_OID_ASSOCIATEEX case to respond to the
> association indication just as it has been done in
> DOT11_OID_ASSOCIATE case.

Again, AP mode is quite different here.. Sure, extended mode will need
code for this even in client mode, but the problem was in not getting
DOT11_OID_ASSOCIATEEX in the first place.

>       The other thing you can try is to retrieve the
> DOT11_OID_STATE from the firmware which might give you
> the current state of the STA in case it does not work.

Which was DOT11_STATE_AUTH..


Actually, I managed to get the card associated in the extended
mode yesterday. I just needed to ignore what the documentation says and
request association with DOT11_OID_ASSOCIATEEX when the firmware reports
that it has completed authentication. I would assume the next step of
adding WPA IE to AssocReq would be relatively easy. Although, this time
I might ignore documentation from the beginning and just try couple of
most logical ways of doing this ;-).

-- 
Jouni Malinen                                            PGP id EFC895FA