madwifi(cvs), wpa_supp v0.2.5 and linksys router problem

[Jouni Malinen]

On Mon, Nov 22, 2004 at 01:30:48AM +0100, Andreas Schuldei wrote:

> Again i experience problems with wpa from my notebook with the
> newest madwifi driver from cvs (atheos hardware), my wrt54g
> linksys router (new broadcom binary drivers) with sveasoft
> alchemy-6.0-rc1.w42 firmware

I tried to reproduce this with same configuration using CVS version of
madwifi and Satori-4.0 v2.07.1.7sv firmware on WRT54G. However,
everything seemed to work fine with WPA-PSK/CCMP..

Which version of the Broadcom driver is used in the firmware you are
using? You can get this information with 'wl ver'. The one I used has
following version information:

(none):[~]# wl ver
wl:     3.50 RC21.10
        wl0: Jan 21 2004 20:53:00 version 3.50.21.10

Is alchemy-6.0-rc1.w42 firmware available somewhere for testing? I would
need at least wl.o and nas binaries to be able to reproduce the same
test setup.

> root at timotheus:~# wpa_supplicant -i ath0 -D madwifi -d

> WPA: RX message 1 of Group Key Handshake from 00:0f:66:45:e2:ad (ver=2)
> WPA: Group Key - hexdump(len=16): 6b 22 bd f8 7c ec ff 29 bd 7b 7c 71 53 1f 78 14
> 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
> Cancelling authentication timeout

Everything looks fine here, i.e., 4-Way and Group Key handshakes were
completed. However..

> 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
> EAPOL: SUPP_BE entering state INITIALIZE
> EAP: EAP entering state DISABLED
> EAPOL: External notification - portValid=0
> EAPOL: External notification - EAP success=0
> Disconnect event - remove keys

Something triggered the driver to generate disconnect event. I would
assume this was Disassociate or Deauthenticate frame from the AP.
Wireless sniffer trace of the authentication attempt could be used to
verify this..

-- 
Jouni Malinen                                            PGP id EFC895FA