* [ath9k-devel] AR9280, 5GHz, and hostapd 0.7.2: 5GHz channels not available
@ 2010-05-25 5:21 Robert Gash
2010-05-25 18:42 ` Luis R. Rodriguez
0 siblings, 1 reply; 4+ messages in thread
From: Robert Gash @ 2010-05-25 5:21 UTC (permalink / raw)
To: ath9k-devel
I recently installed a Sparklan WPEA-111N (AR9280) into a new base station
that I'm building. I am specifically attempting to use the 5GHz bands (US),
as there is a significant amount of traffic on the 2.4GHz band around my
home (I live in a very dense area). The card itself seems to be working
correctly. However, when attempting to create a base station on the 5GHz
band, hostapd does not list *any* frequencies in mode=2 (802.11a) and notes
"wlan0: IEEE 802.11 Hardware does not support configured channel".
This does not seem to match the documentation, which indicates that channels
available in iw list should be usable as base station channels. I've tried
this on both hostapd 0.6.10 from the original Ubuntu 10.04 install, as well
as a rebuilt version of 0.7.2 (taken from Debian experimental). Neither
version works correctly. Log snippets I've found on this list and elsewhere
seem to indicate that I should at least see an "Allowed channel" entry for
the 5GHz channels.
Is this a known limitation with the ath9k drivers at this point, or is this
likely an issue in the hostapd code?
Relevant logs and configurations are below. Help and suggestions in the
right direction are appreciated.
-R
*hostapd.conf:*
interface=wlan0
bridge=br0
driver=nl80211
ssid=XXXXXXXX
hw_mode=a
channel=36
ieee80211n=1
ht_capab=[HT40-][SHORT-GI-40][DSSS_CCK-40]
*hostapd output (5GHz fail):*
root at gashalot-gw:/etc/hostapd# hostapd -dd /etc/hostapd/test.conf
Configuration file: /etc/hostapd/test.conf
nl80211: Add own interface ifindex 4
nl80211: New interface mon.wlan0 created: ifindex=30
nl80211: Add own interface ifindex 30
nl80211: Add own interface ifindex 31
nl80211: Adding interface wlan0 into bridge br0
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
nl80211: Added 802.11b mode based on 802.11g information
Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=20 dBm
wlan0: IEEE 802.11 Configured channel (36) not found from the channel list
of current mode (2) IEEE 802.11a
wlan0: IEEE 802.11 Hardware does not support configured channel
Could not select hw_mode and channel. (-1)
wlan0: Unable to setup interface.
Flushing old station entries
Deauthenticate all stations
nl80211: Remove interface ifindex=30
netlink: Operstate: linkmode=0, operstate=6
*iw list:*
Wiphy phy0
Band 1:
Capabilities: 0x104e
HT20/HT40
SM Power Save disabled
RX HT40 SGI
No RX STBC
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm) (passive scanning)
* 2472 MHz [13] (20.0 dBm) (passive scanning)
* 2484 MHz [14] (disabled)
Bitrates (non-HT):
* 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
Band 2:
Capabilities: 0x104e
HT20/HT40
SM Power Save disabled
RX HT40 SGI
No RX STBC
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
Frequencies:
* 5180 MHz [36] (30.0 dBm) (passive scanning, no
IBSS)
* 5200 MHz [40] (30.0 dBm) (passive scanning, no
IBSS)
* 5220 MHz [44] (30.0 dBm) (passive scanning, no
IBSS)
* 5240 MHz [48] (30.0 dBm) (passive scanning, no
IBSS)
* 5260 MHz [52] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5280 MHz [56] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5300 MHz [60] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5320 MHz [64] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5500 MHz [100] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5520 MHz [104] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5540 MHz [108] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5560 MHz [112] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5580 MHz [116] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5600 MHz [120] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5620 MHz [124] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5640 MHz [128] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5660 MHz [132] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5680 MHz [136] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5700 MHz [140] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5745 MHz [149] (30.0 dBm) (passive scanning, no
IBSS)
* 5765 MHz [153] (30.0 dBm) (passive scanning, no
IBSS)
* 5785 MHz [157] (30.0 dBm) (passive scanning, no
IBSS)
* 5805 MHz [161] (30.0 dBm) (passive scanning, no
IBSS)
* 5825 MHz [165] (30.0 dBm) (passive scanning, no
IBSS)
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
max # scan SSIDs: 4
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
Supported commands:
* new_interface
* set_interface
* new_key
* new_beacon
* new_station
* new_mpath
* set_mesh_params
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* Unknown command (55)
* Unknown command (57)
* Unknown command (59)
* set_wiphy_netns
* connect
* disconnect
*uname -a:*
Linux gashalot-gw 2.6.34-020634-generic #020634 SMP Mon May 17 19:27:49 UTC
2010 x86_64 GNU/Linux
*ath9k-related Kernel Logs:*
[ 7.008816] ath: EEPROM regdomain: 0x6a
[ 7.008822] ath: EEPROM indicates we should expect a direct regpair map
[ 7.008830] ath: Country alpha2 being used: 00
[ 7.008835] ath: Regpair used: 0x6a
[ 7.582713] phy0: Selected rate control algorithm 'ath9k_rate_control'
[ 7.584393] Registered led device: ath9k-phy0::radio
[ 7.584455] Registered led device: ath9k-phy0::assoc
[ 7.584517] Registered led device: ath9k-phy0::tx
[ 7.584584] Registered led device: ath9k-phy0::rx
[ 7.584609] phy0: Atheros AR9280 Rev:2 mem=0xffffc90004f20000, irq=17
[ 2140.755234] cfg80211: Calling CRDA for country: US
[ 2140.760228] cfg80211: Regulatory domain changed to country: US
[ 2140.760236] (start_freq - end_freq @ bandwidth), (max_antenna_gain,
max_eirp)
[ 2140.760246] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700
mBm)
[ 2140.760254] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700
mBm)
[ 2140.760262] (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000
mBm)
[ 2140.760270] (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000
mBm)
[ 2140.760278] (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000
mBm)
[ 2140.760286] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000
mBm)
*lcpci output: *
02:00.0 Network controller: Atheros Communications Inc. AR928X Wireless
Network Adapter (PCI-Express) (rev 01)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20100524/b8687d91/attachment-0001.htm
^ permalink raw reply [flat|nested] 4+ messages in thread* [ath9k-devel] AR9280, 5GHz, and hostapd 0.7.2: 5GHz channels not available
2010-05-25 5:21 [ath9k-devel] AR9280, 5GHz, and hostapd 0.7.2: 5GHz channels not available Robert Gash
@ 2010-05-25 18:42 ` Luis R. Rodriguez
2010-05-25 19:26 ` Luca Niccoli
0 siblings, 1 reply; 4+ messages in thread
From: Luis R. Rodriguez @ 2010-05-25 18:42 UTC (permalink / raw)
To: ath9k-devel
On Mon, May 24, 2010 at 10:21:19PM -0700, Robert Gash wrote:
> I recently installed a Sparklan WPEA-111N (AR9280) into a new base station that I'm building. I am specifically attempting to use the 5GHz bands (US), as there is a significant amount of traffic on the 2.4GHz band around my home (I live in a very dense area). The card itself seems to be working correctly. However, when attempting to create a base station
This is called an AP, base stations are for Cellular or WiMax.
> on the 5GHz band, hostapd does not list any frequencies in mode=2 (802.11a) and notes "wlan0: IEEE 802.11 Hardware does not support configured channel".
To use AP mode of operation hostapd must have the 5 GHz channel you chose
enabled. It must also not have any passive scan flags nor DFS flags since
DFS master mode is not supported.
> This does not seem to match the documentation, which indicates that channels available in iw list should be usable as base station channels.
What documentation are you reading? The channel is availble but has a
few channel flags.
> I've tried this on both hostapd 0.6.10 from the original Ubuntu 10.04 install, as well as a rebuilt version of 0.7.2 (taken from Debian experimental). Neither version works correctly.
It seems to be working as per design.
> Log snippets I've found on this list and elsewhere seem to indicate that I should at least see an "Allowed channel" entry for the 5GHz channels.
>
> Is this a known limitation with the ath9k drivers at this point, or is this likely an issue in the hostapd code?
It seems this must be an issue with what you percieve as
documentation telling you that you should be able to use some
channels in AP mode.
> Relevant logs and configurations are below. Help and suggestions in the right direction are appreciated.
>
> -R
>
> hostapd.conf:
> interface=wlan0
> bridge=br0
> driver=nl80211
> ssid=XXXXXXXX
> hw_mode=a
> channel=36
Channel is 36.
> ieee80211n=1
> ht_capab=[HT40-][SHORT-GI-40][DSSS_CCK-40]
>
> hostapd output (5GHz fail):
> root at gashalot-gw:/etc/hostapd# hostapd -dd /etc/hostapd/test.conf
> Configuration file: /etc/hostapd/test.conf
> nl80211: Add own interface ifindex 4
> nl80211: New interface mon.wlan0 created: ifindex=30
> nl80211: Add own interface ifindex 30
> nl80211: Add own interface ifindex 31
> nl80211: Adding interface wlan0 into bridge br0
> BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
> nl80211: Added 802.11b mode based on 802.11g information
> Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=20 dBm
> Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=20 dBm
> Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=20 dBm
> Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=20 dBm
> Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=20 dBm
> Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=20 dBm
> Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=20 dBm
> Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=20 dBm
> Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=20 dBm
> Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=20 dBm
> Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=20 dBm
> Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=20 dBm
> Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=20 dBm
> Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=20 dBm
> Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=20 dBm
> Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=20 dBm
> Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=20 dBm
> Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=20 dBm
> Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=20 dBm
> Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=20 dBm
> Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=20 dBm
> Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=20 dBm
> wlan0: IEEE 802.11 Configured channel (36) not found from the channel list of current mode (2) IEEE 802.11a
> wlan0: IEEE 802.11 Hardware does not support configured channel
> Could not select hw_mode and channel. (-1)
> wlan0: Unable to setup interface.
> Flushing old station entries
> Deauthenticate all stations
> nl80211: Remove interface ifindex=30
> netlink: Operstate: linkmode=0, operstate=6
>
> iw list:
> Wiphy phy0
> Band 1:
> Capabilities: 0x104e
> HT20/HT40
> SM Power Save disabled
> RX HT40 SGI
> No RX STBC
> Max AMSDU length: 7935 bytes
> DSSS/CCK HT40
> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
> Minimum RX AMPDU time spacing: 8 usec (0x06)
> HT TX/RX MCS rate indexes supported: 0-15
> Frequencies:
> * 2412 MHz [1] (20.0 dBm)
> * 2417 MHz [2] (20.0 dBm)
> * 2422 MHz [3] (20.0 dBm)
> * 2427 MHz [4] (20.0 dBm)
> * 2432 MHz [5] (20.0 dBm)
> * 2437 MHz [6] (20.0 dBm)
> * 2442 MHz [7] (20.0 dBm)
> * 2447 MHz [8] (20.0 dBm)
> * 2452 MHz [9] (20.0 dBm)
> * 2457 MHz [10] (20.0 dBm)
> * 2462 MHz [11] (20.0 dBm)
> * 2467 MHz [12] (20.0 dBm) (passive scanning)
> * 2472 MHz [13] (20.0 dBm) (passive scanning)
> * 2484 MHz [14] (disabled)
> Bitrates (non-HT):
> * 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
> Band 2:
> Capabilities: 0x104e
> HT20/HT40
> SM Power Save disabled
> RX HT40 SGI
> No RX STBC
> Max AMSDU length: 7935 bytes
> DSSS/CCK HT40
> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
> Minimum RX AMPDU time spacing: 8 usec (0x06)
> HT TX/RX MCS rate indexes supported: 0-15
> Frequencies:
> * 5180 MHz [36] (30.0 dBm) (passive scanning, no IBSS)
This is your chanel 36.
The passive scan flag does not allow AP mode of operation.
The no IBSS flag also does not allow AP mode of operation.
The passive scanning flag is used to help with cards who are
built to world roam. Part of the world roaming compromise is
to not restrict you from some channels completely but instead
to let you sit idly and passivly scanning, that is not issuing
probe requests. If the STA then picks up a beacon from an AP
then it knows that country does allow the STA to operate.
It then can lift its passive scan flag and let you send probe
requests too. If you did not have a no-ibss flag it would
then let you use a beaconing mode of operation after it lifted
the passive scanning flag.
The no IBSS flag should be renamed to no-beaconing as there
are other beaconing modes such as AP and Mesh which cannot
be used when this flag is used. When this flag is used it
means you simply cannot use beaconing modes on this channel.
> * 5200 MHz [40] (30.0 dBm) (passive scanning, no IBSS)
> * 5220 MHz [44] (30.0 dBm) (passive scanning, no IBSS)
> * 5240 MHz [48] (30.0 dBm) (passive scanning, no IBSS)
> * 5260 MHz [52] (30.0 dBm) (passive scanning, no IBSS, radar detection)
> * 5280 MHz [56] (30.0 dBm) (passive scanning, no IBSS, radar detection)
> * 5300 MHz [60] (30.0 dBm) (passive scanning, no IBSS, radar detection)
> * 5320 MHz [64] (30.0 dBm) (passive scanning, no IBSS, radar detection)
> * 5500 MHz [100] (30.0 dBm) (passive scanning, no IBSS, radar detection)
> * 5520 MHz [104] (30.0 dBm) (passive scanning, no IBSS, radar detection)
> * 5540 MHz [108] (30.0 dBm) (passive scanning, no IBSS, radar detection)
> * 5560 MHz [112] (30.0 dBm) (passive scanning, no IBSS, radar detection)
> * 5580 MHz [116] (30.0 dBm) (passive scanning, no IBSS, radar detection)
> * 5600 MHz [120] (30.0 dBm) (passive scanning, no IBSS, radar detection)
> * 5620 MHz [124] (30.0 dBm) (passive scanning, no IBSS, radar detection)
> * 5640 MHz [128] (30.0 dBm) (passive scanning, no IBSS, radar detection)
> * 5660 MHz [132] (30.0 dBm) (passive scanning, no IBSS, radar detection)
> * 5680 MHz [136] (30.0 dBm) (passive scanning, no IBSS, radar detection)
> * 5700 MHz [140] (30.0 dBm) (passive scanning, no IBSS, radar detection)
> * 5745 MHz [149] (30.0 dBm) (passive scanning, no IBSS)
> * 5765 MHz [153] (30.0 dBm) (passive scanning, no IBSS)
> * 5785 MHz [157] (30.0 dBm) (passive scanning, no IBSS)
> * 5805 MHz [161] (30.0 dBm) (passive scanning, no IBSS)
> * 5825 MHz [165] (30.0 dBm) (passive scanning, no IBSS)
All of your 5 GHz channels do not allow for AP mode of operation, or
for that matter any beaconing mode of operation, whether that is
IBSS, Mesh or AP.
> Bitrates (non-HT):
> * 6.0 Mbps
> * 9.0 Mbps
> * 12.0 Mbps
> * 18.0 Mbps
> * 24.0 Mbps
> * 36.0 Mbps
> * 48.0 Mbps
> * 54.0 Mbps
> max # scan SSIDs: 4
> Supported interface modes:
> * IBSS
> * managed
> * AP
> * AP/VLAN
> * monitor
> * mesh point
> Supported commands:
> * new_interface
> * set_interface
> * new_key
> * new_beacon
> * new_station
> * new_mpath
> * set_mesh_params
> * set_bss
> * authenticate
> * associate
> * deauthenticate
> * disassociate
> * join_ibss
> * Unknown command (55)
> * Unknown command (57)
> * Unknown command (59)
> * set_wiphy_netns
> * connect
> * disconnect
>
>
> uname -a:
> Linux gashalot-gw 2.6.34-020634-generic #020634 SMP Mon May 17 19:27:49 UTC 2010 x86_64 GNU/Linux
>
> ath9k-related Kernel Logs:
> [ 7.008816] ath: EEPROM regdomain: 0x6a
> [ 7.008822] ath: EEPROM indicates we should expect a direct regpair map
> [ 7.008830] ath: Country alpha2 being used: 00
> [ 7.008835] ath: Regpair used: 0x6a
And this is why, your card was programmed to world roam. See:
See:
http://wireless.kernel.org/en/users/Drivers/ath/
> [ 7.582713] phy0: Selected rate control algorithm 'ath9k_rate_control'
> [ 7.584393] Registered led device: ath9k-phy0::radio
> [ 7.584455] Registered led device: ath9k-phy0::assoc
> [ 7.584517] Registered led device: ath9k-phy0::tx
> [ 7.584584] Registered led device: ath9k-phy0::rx
> [ 7.584609] phy0: Atheros AR9280 Rev:2 mem=0xffffc90004f20000, irq=17
> [ 2140.755234] cfg80211: Calling CRDA for country: US
> [ 2140.760228] cfg80211: Regulatory domain changed to country: US
> [ 2140.760236] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> [ 2140.760246] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
> [ 2140.760254] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
> [ 2140.760262] (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> [ 2140.760270] (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> [ 2140.760278] (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> [ 2140.760286] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
>
> lcpci output:
> 02:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)
So your card world roams and it only enables AP mode on
2.4 GHz channels 1-11. You cannot change this, for further
information see:
http://wireless.kernel.org/en/vendors/VendorSupport
http://wireless.kernel.org/en/developers/Regulatory/statement
http://wireless.kernel.org/en/developers/Regulatory/
http://wireless.kernel.org/en/developers/Regulatory/CRDA
Luis
^ permalink raw reply [flat|nested] 4+ messages in thread
* [ath9k-devel] AR9280, 5GHz, and hostapd 0.7.2: 5GHz channels not available
2010-05-25 18:42 ` Luis R. Rodriguez
@ 2010-05-25 19:26 ` Luca Niccoli
2010-05-25 21:20 ` Luis R. Rodriguez
0 siblings, 1 reply; 4+ messages in thread
From: Luca Niccoli @ 2010-05-25 19:26 UTC (permalink / raw)
To: ath9k-devel
On 25 May 2010 20:42, Luis R. Rodriguez <lrodriguez@atheros.com> wrote:
> The passive scanning flag is used to help with cards who are
> built to world roam. Part of the world roaming compromise is
> to not restrict you from some channels completely but instead
> to let you sit idly and passivly scanning, that is not issuing
> probe requests. If the STA then picks up a beacon from an AP
> then it knows that country does allow the STA to operate.
> It then can lift its passive scan flag and let you send probe
> requests too. If you did not have a no-ibss flag it would
> then let you use a beaconing mode of operation after it lifted
> the passive scanning flag.
>> ath9k-related Kernel Logs:
>> [ ? ?7.008816] ath: EEPROM regdomain: 0x6a
>> [ ? ?7.008822] ath: EEPROM indicates we should expect a direct regpair map
>> [ ? ?7.008830] ath: Country alpha2 being used: 00
>> [ ? ?7.008835] ath: Regpair used: 0x6a
>
> And this is why, your card was programmed to world roam. See:
>
It was my understanding that the regulatory domain embedded in the
card firmware was used only to disable some channels completely, on
the basis of the fact that the radio/antenna hardware could have been
untested on those.
I don't understand (from a compliance point of view) why it can force
some channels to passive scanning: since this is purely a matter of
which nation the card is operating in, shouldn't it be managed only by
CRDA?
Cheers,
Luca
^ permalink raw reply [flat|nested] 4+ messages in thread
* [ath9k-devel] AR9280, 5GHz, and hostapd 0.7.2: 5GHz channels not available
2010-05-25 19:26 ` Luca Niccoli
@ 2010-05-25 21:20 ` Luis R. Rodriguez
0 siblings, 0 replies; 4+ messages in thread
From: Luis R. Rodriguez @ 2010-05-25 21:20 UTC (permalink / raw)
To: ath9k-devel
On Tue, May 25, 2010 at 12:26:08PM -0700, Luca Niccoli wrote:
> On 25 May 2010 20:42, Luis R. Rodriguez <lrodriguez@atheros.com> wrote:
>
> > The passive scanning flag is used to help with cards who are
> > built to world roam. Part of the world roaming compromise is
> > to not restrict you from some channels completely but instead
> > to let you sit idly and passivly scanning, that is not issuing
> > probe requests. If the STA then picks up a beacon from an AP
> > then it knows that country does allow the STA to operate.
> > It then can lift its passive scan flag and let you send probe
> > requests too. If you did not have a no-ibss flag it would
> > then let you use a beaconing mode of operation after it lifted
> > the passive scanning flag.
>
> >> ath9k-related Kernel Logs:
> >> [ ? ?7.008816] ath: EEPROM regdomain: 0x6a
> >> [ ? ?7.008822] ath: EEPROM indicates we should expect a direct regpair map
> >> [ ? ?7.008830] ath: Country alpha2 being used: 00
> >> [ ? ?7.008835] ath: Regpair used: 0x6a
> >
> > And this is why, your card was programmed to world roam. See:
> >
>
> It was my understanding that the regulatory domain embedded in the
> card firmware
The card has no firmware, it has an EEPROM and the regulatory
domain is programmed onto the EEPROM.
> was used only to disable some channels completely, on
> the basis of the fact that the radio/antenna hardware could have been
> untested on those.
The regulatory domain is chosen by the OEM and programmed by the ODM.
If the device is targetted for one specific region it will have one
regulatory domain, the country for which it is destined. Often times
though some OEMs prefer to sell a device to a few regions and so a
custom world regulatory domain is invented. Technically you can use
a global world regulatory domain but that is very restrictive so there
are some custom Atheros ones. These are not part of CRDA since they
are static and then are just kept part of the driver.
The custom world regulatory domains are documented here:
http://wireless.kernel.org/en/users/Drivers/ath
> I don't understand (from a compliance point of view) why it can force
> some channels to passive scanning: since this is purely a matter of
> which nation the card is operating in, shouldn't it be managed only by
> CRDA?
CRDA is a helper for compliance, the driver however can decide it knows
better due to some customizations or enhancements. cfg80211 itself supports
world roaming, which is the default, when a card does not know what
country it is in or what country the card was programmed for. Upon
initialization then the card first does complete restrictive world
roaming (the intersection of all regulatory domain). Then, the card
might know better in case it has an EEPROM and inform cfg80211 of this,
CRDA would be used if the card was using a country regulatory domain.
If the card was using a custom regulatory domain from a vendor it can
pass this to cfg80211 as well, which is what ath9k does for the 12
world regulatory domains it supports. The user can be more compliant
too, and inform cfg80211 that although the card believes it can world
roam, or is a card for 'JP' that it is in fact in the 'US', for example.
The user input then is just used to help compliance further.
Now, passive scanning is a world roaming feature. So for example the
interesection of all regulatory domains gives us 5 GHz disabled
completely. A compromise is to use passive scanning so that if a
card detects beacons from an AP it can then actively scan. It
will also then know it too can become start as an AP / IBSS / Mesh.
The exception for this is for DFS channels because DFS master support
is required for modes of operation that beacon (AP, IBSS, Mesh).
So your other option is to just keep all the 5 GHz channels disabled
completely. Consider passive scanning is an innovative way to help with
cards targetted for customers or businesses which want devices which
can work in different regulatory domains at the same time. With the
complexity of regulatory rules globally without passive scanning you'd
just have many channels always disabled.
Luis
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-05-25 21:20 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-25 5:21 [ath9k-devel] AR9280, 5GHz, and hostapd 0.7.2: 5GHz channels not available Robert Gash
2010-05-25 18:42 ` Luis R. Rodriguez
2010-05-25 19:26 ` Luca Niccoli
2010-05-25 21:20 ` Luis R. Rodriguez
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.