linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lutomirski <luto@mit.edu>
To: linux-wireless@vger.kernel.org
Subject: Re: regulatory hiccup
Date: Fri, 23 Jul 2010 16:03:02 -0400	[thread overview]
Message-ID: <AANLkTi=Wy1r2C1xL289QQX10aVZaYfF7A1K8sd93ZXOd@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinfMiS=+dqi=azF2exJbkrSLYT9nN0aor7gff-Q@mail.gmail.com>

On Fri, Jul 23, 2010 at 3:35 PM, Andrew Lutomirski <luto@mit.edu> wrote:
> On Fri, Jul 23, 2010 at 3:30 PM, Andrew Lutomirski <luto@mit.edu> wrote:
>>
>> Then, after fiddling with an AP for a bit, I got:
>>
>> [11747.264221] cfg80211: Calling CRDA for country: US
>> [11747.282664] cfg80211: Current regulatory domain updated by AP to: US
>> [11747.282672]     (start_freq - end_freq @ bandwidth),
>> (max_antenna_gain, max_eirp)
>> [11747.282680]     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1600 mBm)
>> [11747.282688]     (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 1600 mBm)
>>
>
> It's worse than that.  I reconnected to the AP (it appeared to work
> for a few seconds) and I saw:
>
> Wiphy phy0
> [...]
>        Band 2:
>                Capabilities: 0x872
>                        HT20/HT40
>                        Static SM Power Save
>                        RX Greenfield
>                        RX HT20 SGI
>                        RX HT40 SGI
>                        No RX STBC
>                        Max AMSDU length: 3839 bytes
>                        No DSSS/CCK HT40
>                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>                Minimum RX AMPDU time spacing: 4 usec (0x05)
>                HT TX/RX MCS rate indexes supported: 0-23, 32
>                Frequencies:
>                        * 5180 MHz [36] (15.0 dBm) (passive scanning, no IBSS)
>                        * 5200 MHz [40] (15.0 dBm) (passive scanning, no IBSS)
>                        * 5220 MHz [44] (15.0 dBm) (passive scanning, no IBSS)
>                        * 5240 MHz [48] (15.0 dBm) (passive scanning, no IBSS)
>                        * 5260 MHz [52] (15.0 dBm) (passive scanning, no IBSS, radar detection)
>                        * 5280 MHz [56] (15.0 dBm) (passive scanning, no IBSS, radar detection)
>                        * 5300 MHz [60] (15.0 dBm) (passive scanning, no IBSS, radar detection)
>                        * 5320 MHz [64] (15.0 dBm) (passive scanning, no IBSS, radar detection)
>                        * 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)
>
> Which is absurd, because:
>
> Connected to 00:02:6f:6e:d7:6c (on wlan0)
>        SSID: FFTT5
>        freq: 5785        [!!!!!!!!!!!]
>        RX: 72058 bytes (310 packets)
>        TX: 2568 bytes (20 packets)
>        signal: -33 dBm
>        tx bitrate: 6.0 MBit/s
>
> The connection died after a little while, presumably because the AP
> was outside of its own allowed band.
>

Here's the offending country IE:

Country Information: Country Code: US, Indoor Environment
Tag Number: 7 (Country Information)
Tag length: 6
Tag interpretation: Country Code: US, Indoor Environment
  Start Channel: 36, Channels: 13, Max TX Power: 16 dBm

AFAICT net/wireless/reg.c ignores the last bit, and the other APs that
work correctly here don't send country IEs.

--Andy

  reply	other threads:[~2010-07-23 20:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-23 19:30 regulatory hiccup Andrew Lutomirski
2010-07-23 19:35 ` Andrew Lutomirski
2010-07-23 20:03   ` Andrew Lutomirski [this message]
2010-07-27 23:33     ` Luis R. Rodriguez
2010-07-27 23:46       ` Andrew Lutomirski
2010-07-27 23:51         ` Luis R. Rodriguez
2010-07-27 23:32   ` Luis R. Rodriguez
2010-07-27 23:30 ` Luis R. Rodriguez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=Wy1r2C1xL289QQX10aVZaYfF7A1K8sd93ZXOd@mail.gmail.com' \
    --to=luto@mit.edu \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).