wpa_supplicant against a wrt54g with new broadcom drivers

[Jouni Malinen]

On Fri, Oct 01, 2004 at 12:57:38AM +0200, Andreas Schuldei wrote:

> i updated the firware in my wrt54g in my working setup with the
> latest sveasoft pre-release alchemy pre-5.3 and it broke. 
> 
> the firmware contains new broadcom binary only drivers. 

Which version of the Broadcom driver is this? Is the driver (mainly,
wl.o and the user space tool wl) available somewhere for downloading?

>  WPA: RX message 1 of Group Key Handshake from 00:0f:66:45:e2:ad (ver=2) 

It looks like 4-way handshake was successful and the client was able to
decrypt Group Key msg 1/2.

>  WPA: Group Key - hexdump(len=16): c6 92 9c a0 0f 25 51 b1 da b3 bd 18 6f b7 09 82 
>  WPA: Installing GTK to the driver (keyidx=1 tx=0). 
>  WPA: RSC - hexdump(len=6): 00 00 00 00 00 00 
>  wpa_driver_madwifi_set_key: alg=CCMP key_idx=1 set_tx=0 seq_len=6 key_len=16 
>  WPA: Sending EAPOL-Key 2/2 
>  WPA: Key negotiation completed with 00:0f:66:45:e2:ad 

Client side seemed happy..

>  Wireless event: cmd=0x8b1a len=12 
>  Wireless event: cmd=0x8b15 len=20 
>  Wireless event: new AP: 00:00:00:00:00:00 
>  Setting scan request: 0 sec 100000 usec 
>  EAPOL: External notification - portEnabled=0 
>  EAPOL: SUPP_PAE entering state DISCONNECTED 

..but AP deauthenticated/disassociated..

This could be because of the AP not liking something in the Group Key
msg 2/2.. Which version of madwifi driver are you using? If I remember
correctly, madwifi did not encrypt group key messages at some point. Has
that been fixed in the version you are using? It's possible that the
newer version of Broadcom driver started verifying that the Group Key
messages are encrypted..

-- 
Jouni Malinen                                            PGP id EFC895FA