Return-path: Received: from rn-out-0910.google.com ([64.233.170.187]:55200 "EHLO rn-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752116AbZBISWQ (ORCPT ); Mon, 9 Feb 2009 13:22:16 -0500 Received: by rn-out-0910.google.com with SMTP id k40so1442400rnd.17 for ; Mon, 09 Feb 2009 10:22:14 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <43e72e890902091020p65235e3ds833560974c785318@mail.gmail.com> References: <1234202993.21570.18.camel@localhost> <43e72e890902091020p65235e3ds833560974c785318@mail.gmail.com> Date: Mon, 9 Feb 2009 10:22:14 -0800 Message-ID: <43e72e890902091022n1d4b6edcg63e3f233991f67ee@mail.gmail.com> (sfid-20090209_192220_063925_56038689) Subject: Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges From: "Luis R. Rodriguez" To: tony@linx.net Cc: linux-wireless@vger.kernel.org, reinette chatre Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, Feb 9, 2009 at 10:20 AM, Luis R. Rodriguez wrote: > On Mon, Feb 9, 2009 at 10:09 AM, Tony Vroon wrote: >> I'm using: >> [ebuild R ] net-wireless/wireless-regdb-20090130 0 kB >> [ebuild R ] net-wireless/crda-1.0.1-r1 0 kB >> [ebuild R ] net-wireless/iwl5000-ucode-5.4.0.11 0 kB >> >> The regulatory information for Great Britain looks as follows: >> country GB: >> (2402.000 - 2482.000 @ 40.000), (N/A, 20.00) >> (5170.000 - 5250.000 @ 40.000), (N/A, 20.00) >> (5250.000 - 5330.000 @ 40.000), (N/A, 20.00), DFS >> (5490.000 - 5710.000 @ 40.000), (N/A, 27.00), DFS >> >> iw reports the card configuration like such: >> Wiphy phy0 >> Band 1: >> HT capabilities: 0x087e >> * 20/40 MHz operation >> * SM PS disabled >> * HT-greenfield >> * 20 MHz short GI >> * 40 MHz short GI >> * max A-MSDU len 7935 >> HT A-MPDU factor: 0x0003 (65535 bytes) >> HT A-MPDU density: 0x0005 (4 usec) >> HT MCS set: ff ff ff 00 01 00 00 00 00 00 c2 01 01 00 00 00 >> Frequencies: >> * 2412 MHz [1] (15.0 dBm) >> * 2417 MHz [2] (15.0 dBm) >> * 2422 MHz [3] (15.0 dBm) >> * 2427 MHz [4] (15.0 dBm) >> * 2432 MHz [5] (15.0 dBm) >> * 2437 MHz [6] (15.0 dBm) >> * 2442 MHz [7] (15.0 dBm) >> * 2447 MHz [8] (15.0 dBm) >> * 2452 MHz [9] (15.0 dBm) >> * 2457 MHz [10] (15.0 dBm) >> * 2462 MHz [11] (15.0 dBm) >> * 2467 MHz [12] (15.0 dBm) (passive scanning, no IBSS) >> * 2472 MHz [13] (15.0 dBm) (passive scanning, no IBSS) >> Bitrates: >> * 1.0 Mbps >> * 2.0 Mbps (short preamble supported) >> * 5.5 Mbps (short preamble supported) >> * 11.0 Mbps (short preamble supported) >> * 6.0 Mbps >> * 9.0 Mbps >> * 12.0 Mbps >> * 18.0 Mbps >> * 24.0 Mbps >> * 36.0 Mbps >> * 48.0 Mbps >> * 54.0 Mbps >> * 60.0 Mbps >> Band 2: >> HT capabilities: 0x087e >> * 20/40 MHz operation >> * SM PS disabled >> * HT-greenfield >> * 20 MHz short GI >> * 40 MHz short GI >> * max A-MSDU len 7935 >> HT A-MPDU factor: 0x0003 (65535 bytes) >> HT A-MPDU density: 0x0005 (4 usec) >> HT MCS set: ff ff ff 00 01 00 00 00 00 00 c2 01 01 00 00 00 >> Frequencies: >> * 5180 MHz [36] (disabled) >> * 5200 MHz [40] (disabled) >> * 5220 MHz [44] (disabled) >> * 5240 MHz [48] (disabled) >> * 5260 MHz [52] (disabled) >> * 5280 MHz [56] (disabled) >> * 5300 MHz [60] (disabled) >> * 5320 MHz [64] (disabled) >> * 5500 MHz [100] (disabled) >> * 5520 MHz [104] (disabled) >> * 5540 MHz [108] (disabled) >> * 5560 MHz [112] (disabled) >> * 5580 MHz [116] (disabled) >> * 5600 MHz [120] (disabled) >> * 5620 MHz [124] (disabled) >> * 5640 MHz [128] (disabled) >> * 5660 MHz [132] (disabled) >> * 5680 MHz [136] (disabled) >> * 5700 MHz [140] (disabled) >> * 5745 MHz [149] (disabled) >> * 5765 MHz [153] (disabled) >> * 5785 MHz [157] (disabled) >> * 5805 MHz [161] (disabled) >> * 5825 MHz [165] (disabled) >> Bitrates: >> * 6.0 Mbps >> * 9.0 Mbps >> * 12.0 Mbps >> * 18.0 Mbps >> * 24.0 Mbps >> * 36.0 Mbps >> * 48.0 Mbps >> * 54.0 Mbps >> * 60.0 Mbps >> Supported interface modes: >> * IBSS >> * Station >> * Monitor >> >> My Cisco AIR-AP1131AG-E-K9_v04 access point with C1130 Software >> (C1130-K9W7-M), Version 12.4(10b)JA, RELEASE has Dot11Radio0 & >> Dot11Radio1 configured like so: >> world-mode dot11d country GB indoor >> >> The kernel seems to do something else: >> cfg80211: Calling CRDA for country: GB >> cfg80211: Current regulatory domain updated by AP to: GB >> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) >> (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) >> >> Any idea how that could happen please? > > Your AP did not provide 5 GHz frequencies in its country information > element. Because of this the intersection between what CRDA has for GB > and what your AP provides does not include any channels in 5 GHz. This > has been fixed in wireless-testing though, if your AP country IE does > not have information for a separate band we lave that band to trust > CRDA information instead. > > This should have been propagated down to 29 already, maybe it'll be in rc5? BTW this is the patch commit info: commit 0c7dc45d21de6ae212b5ccb7cdff5beff795ccf0 Author: Luis R. Rodriguez Date: Wed Jan 7 17:43:36 2009 -0800 cfg80211: Fix regression with 11d on bands This fixes a regression on disallowing bands introduced with the new 802.11d support. The issue is that IEEE-802.11 allows APs to send a subset of what a country regulatory domain defines. This was clarified in this document: http://tinyurl.com/11d-clarification As such it is possible, and this is what is done in practice, that a single band 2.4 GHz AP will only send 2.4 GHz band regulatory information through the 802.11 country information element and then the current intersection with what CRDA provided yields a regulatory domain with no 5 GHz information -- even though that country may actually allow 5 GHz operation. We correct this by only applying the intersection rules on a channel if the the intersection yields a regulatory rule on the same band the channel is on. Signed-off-by: Luis R. Rodriguez Acked-by: Johannes Berg Signed-off-by: John W. Linville