Bug#386951: driver loses association repeatedly (WPA)

Kel Modderman kelrin at tpg.com.au
Mon Sep 11 10:07:26 UTC 2006


On Monday 11 September 2006 19:24, martin f krafft wrote:
> Package: madwifi-source
> Version: 0.svnr1697.0.9.2-1
> Severity: important
>
> Ever since I upgraded to the madwifi-ng driver, it's become mostly
> unusable. I am using the latest 2.6.17 kernel from unstable. From
> time to time I get it to work, but most of the time it cannot
> establish an association with the access point, even after reloading
> the driver. I am using WPA, and with -D madwifi, wpasupplicant says:
>
> <2>Trying to associate with 00:12:cf:01:4a:d6 (SSID='krafft' freq=2447 MHz)
> <2>Association request to the driver failed
> <2>Associated with 00:12:cf:01:4a:d6
> <2>WPA: Key negotiation completed with 00:12:cf:01:4a:d6 [PTK=TKIP
> GTK=TKIP] <2>CTRL-EVENT-CONNECTED - Connection to 00:12:cf:01:4a:d6
> completed (reauth) [id=0 id_str=] <2>WPA: Group rekeying completed with
> 00:12:cf:01:4a:d6 [GTK=TKIP] <2>WPA: Group rekeying completed with
> 00:12:cf:01:4a:d6 [GTK=TKIP] <2>CTRL-EVENT-DISCONNECTED - Disconnect event
> - remove keys
>
> If I switch to -D wext, it's even worse:
>
> <2>Trying to associate with 00:12:cf:01:4a:d6 (SSID='krafft' freq=2447 MHz)
> <2>Authentication with 00:00:00:00:00:00 timed out.
>
> As said, from time to time it *does* work with the same
> configuration (-D madwifi, I never actually got it to work with
> wext). Also, other machines are associating fine with the AP, so it
> really seems to be an atheros problem.

Unfortunately, this is a bug more than annoying a few people right now.

Can you please try the patch on madwifi.org ticket #776 [1] that reverts a 
scanning related "enhancement" that appears to help some, but hinder others.

Thanks, Kel.

http://madwifi.org/ticket/776




More information about the Pkg-madwifi-maintainers mailing list