lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4F2EDE23.5070505@openwrt.org>
Date:	Sun, 05 Feb 2012 20:53:07 +0100
From:	Felix Fietkau <nbd@...nwrt.org>
To:	Jurica Vukadin <u.ra604@...glemail.com>
CC:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"John W. Linville" <linville@...driver.com>,
	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: Re: regression, 3.2.2 stable: ath9k won't associate anymore

On 2012-02-05 8:45 PM, Jurica Vukadin wrote:
> Hi,
> 
> commit "b4a82a0 ath9k_hw: fix interpretation of the rx KeyMiss flag"
> caused my card to stop associating with the router.
> Reverting it fixes the issue. Encryption is WEP, if that matters; I
> haven't tried others.
> 
> The device is "10:00.0 Network controller: Atheros Communications Inc.
> AR9287 Wireless Network Adapter (PCI-Express) (rev 01)"
> 
> excerpt from dmesg before the revert:
> Feb  5 20:00:56 smaug kernel: [    7.468770] ath9k 0000:10:00.0: PCI
> INT A -> GSI 17 (level, low) -> IRQ 17
> Feb  5 20:00:56 smaug kernel: [    7.468787] ath9k 0000:10:00.0:
> setting latency timer to 64
> Feb  5 20:00:56 smaug kernel: [    7.558116] ath: EEPROM regdomain: 0x6a
> Feb  5 20:00:56 smaug kernel: [    7.558118] ath: EEPROM indicates we
> should expect a direct regpair map
> Feb  5 20:00:56 smaug kernel: [    7.558121] ath: Country alpha2 being used: 00
> Feb  5 20:00:56 smaug kernel: [    7.558122] ath: Regpair used: 0x6a
> Feb  5 20:00:56 smaug kernel: [    8.044750] ieee80211 phy0: Selected
> rate control algorithm 'ath9k_rate_control'
> Feb  5 20:00:56 smaug kernel: [    8.045371] Registered led device: ath9k-phy0
> Feb  5 20:01:01 smaug kernel: [   16.161078] wlan0: authenticate with
> 00:01:e3:4a:9e:be (try 1)
> Feb  5 20:01:01 smaug kernel: [   16.163159] wlan0: authenticated
> Feb  5 20:01:01 smaug kernel: [   16.197844] wlan0: associate with
> 00:01:e3:4a:9e:be (try 1)
> Feb  5 20:01:01 smaug kernel: [   16.200307] wlan0: RX AssocResp from
> 00:01:e3:4a:9e:be (capab=0x431 status=0 aid=4)
> Feb  5 20:01:01 smaug kernel: [   16.200312] wlan0: associated
> Feb  5 20:01:31 smaug kernel: [   46.185930] wlan0: deauthenticating
> from 00:01:e3:4a:9e:be by local choice (reason=3)
The issue is WEP specific, a fix has been found and confirmed. I'll
submit it for inclusion soon.

- Felix
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ