You are not logged in.

#1 2013-04-28 16:55:19

buhman
Member
Registered: 2013-04-28
Posts: 2

802.11a band 2 frequencies do not match reported regulatory domain.

The original symptom/goal is where I'm attempting to get hostapd to put the wireless interface in AP mode. When hostapd starts:

zack@helios ~ % sudo hostapd -dd /etc/hostapd/hostapd.conf
random: Trying to read entropy from /dev/random
Configuration file: /etc/hostapd/hostapd.conf
ctrl_interface_group=0
nl80211: interface wlan0 in phy phy0
rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
nl80211: Using driver-based off-channel TX
nl80211: Use separate P2P group interface (driver advertised support)
nl80211: TDLS supported
nl80211: TDLS external setup
nl80211: Add own interface ifindex 4
nl80211: Set mode ifindex 4 iftype 3 (AP)
nl80211: Setup AP - device_ap_sme=0 use_monitor=0
nl80211: Subscribe to mgmt frames with AP handle 0x25e5150
nl80211: Register frame type=0xb0 nl_handle=0x25e5150
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame type=0x0 nl_handle=0x25e5150
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame type=0x20 nl_handle=0x25e5150
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame type=0xa0 nl_handle=0x25e5150
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame type=0xc0 nl_handle=0x25e5150
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame type=0xd0 nl_handle=0x25e5150
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame type=0x40 nl_handle=0x25e5150
nl80211: Register frame match - hexdump(len=0): [NULL]
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
nl80211: Regulatory information - country=US
nl80211: 2402-2472 @ 40 MHz
nl80211: 5170-5250 @ 40 MHz
nl80211: 5250-5330 @ 40 MHz
nl80211: 5490-5600 @ 40 MHz
nl80211: 5650-5710 @ 40 MHz
nl80211: 5735-5835 @ 40 MHz
nl80211: 57240-63720 @ 2160 MHz
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=21 dBm
Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=21 dBm
Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=21 dBm
Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=21 dBm
Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=21 dBm
Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=21 dBm
Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=21 dBm
Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=21 dBm
Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=21 dBm
Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=21 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=21 dBm
Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=21 dBm
Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=21 dBm
Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=21 dBm
Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=21 dBm
Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=21 dBm
Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=21 dBm
Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=21 dBm
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=21 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=21 dBm
channel [21] (157) is disabled for use in AP mode, flags: 0x77 NO-IBSS PASSIVE-SCAN
wlan0: IEEE 802.11 Configured channel (157) 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. (-4)
wlan0: Unable to setup interface.
wlan0: Flushing old station entries
wlan0: Deauthenticate all stations
nl80211: CMD_FRAME freq=0 wait=0 no_cck=0 no_ack=0 offchanok=0
nl80211: Frame command failed: ret=-22 (Invalid argument) (freq=0 wait=0)
wpa_driver_nl80211_set_key: ifindex=4 alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=4 alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=4 alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=4 alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
netlink: Operstate: linkmode=0, operstate=6
nl80211: Set mode ifindex 4 iftype 2 (STATION)
nl80211: Unsubscribe mgmt frames handle 0x25e5150 (AP teardown)

I have the US regdom loaded:

zack@helios ~ % iw reg get                                           :(
country US:
	(2402 - 2472 @ 40), (3, 27)
	(5170 - 5250 @ 40), (3, 17)
	(5250 - 5330 @ 40), (3, 20), DFS
	(5490 - 5600 @ 40), (3, 20), DFS
	(5650 - 5710 @ 40), (3, 20), DFS
	(5735 - 5835 @ 40), (3, 30)
	(57240 - 63720 @ 2160), (N/A, 40)

Which obviously has no restrictions for passive-mode. But, the actual frequency restrictions reported by cfg80211 are quite different:

zack@helios ~ % iw list
Wiphy phy0
	Band 1:
		Capabilities: 0x11ce
			HT20/HT40
			SM Power Save disabled
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 3839 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] (21.0 dBm)
			* 2422 MHz [3] (21.0 dBm)
			* 2427 MHz [4] (21.0 dBm)
			* 2432 MHz [5] (21.0 dBm)
			* 2437 MHz [6] (21.0 dBm)
			* 2442 MHz [7] (21.0 dBm)
			* 2447 MHz [8] (21.0 dBm)
			* 2452 MHz [9] (21.0 dBm)
			* 2457 MHz [10] (21.0 dBm)
			* 2462 MHz [11] (21.0 dBm)
			* 2467 MHz [12] (disabled)
			* 2472 MHz [13] (disabled)
			* 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: 0x11ce
			HT20/HT40
			SM Power Save disabled
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 3839 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] (16.0 dBm) (passive scanning, no IBSS)
			* 5200 MHz [40] (16.0 dBm) (passive scanning, no IBSS)
			* 5220 MHz [44] (16.0 dBm) (passive scanning, no IBSS)
			* 5240 MHz [48] (16.0 dBm) (passive scanning, no IBSS)
			* 5260 MHz [52] (20.0 dBm) (passive scanning, no IBSS, radar detection)
			* 5280 MHz [56] (16.0 dBm) (passive scanning, no IBSS, radar detection)
			* 5300 MHz [60] (16.0 dBm) (passive scanning, no IBSS, radar detection)
			* 5320 MHz [64] (16.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] (17.0 dBm) (passive scanning, no IBSS)
			* 5765 MHz [153] (17.0 dBm) (passive scanning, no IBSS)
			* 5785 MHz [157] (17.0 dBm) (passive scanning, no IBSS)
			* 5805 MHz [161] (17.0 dBm) (passive scanning, no IBSS)
			* 5825 MHz [165] (17.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
	max scan IEs length: 2257 bytes
	Coverage class: 0 (up to 0m)
	Supported Ciphers:
		* WEP40 (00-0f-ac:1)
		* WEP104 (00-0f-ac:5)
		* TKIP (00-0f-ac:2)
		* CCMP (00-0f-ac:4)
		* CMAC (00-0f-ac:6)
	Available Antennas: TX 0x3 RX 0x3
	Configured Antennas: TX 0x3 RX 0x3
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * WDS
		 * monitor
		 * mesh point
		 * P2P-client
		 * P2P-GO
	software interface modes (can always be added):
		 * AP/VLAN
		 * monitor
	valid interface combinations:
		 * #{ managed, WDS, P2P-client } <= 2048, #{ AP, mesh point, P2P-GO } <= 8,
		   total <= 2048, #channels <= 1, STA/AP BI must match
	Supported commands:
		 * new_interface
		 * set_interface
		 * new_key
		 * start_ap
		 * new_station
		 * new_mpath
		 * set_mesh_config
		 * set_bss
		 * authenticate
		 * associate
		 * deauthenticate
		 * disassociate
		 * join_ibss
		 * join_mesh
		 * remain_on_channel
		 * set_tx_bitrate_mask
		 * frame
		 * frame_wait_cancel
		 * set_wiphy_netns
		 * set_channel
		 * set_wds_peer
		 * tdls_mgmt
		 * tdls_oper
		 * probe_client
		 * set_noack_map
		 * register_beacons
		 * start_p2p_device
		 * Unknown command (92)
		 * connect
		 * disconnect
	Supported TX frame types:
		 * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
	Supported RX frame types:
		 * IBSS: 0x40 0xb0 0xc0 0xd0
		 * managed: 0x40 0xd0
		 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * mesh point: 0xb0 0xc0 0xd0
		 * P2P-client: 0x40 0xd0
		 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * P2P-device: 0x40 0xd0
	Device supports RSN-IBSS.
	WoWLAN support:
		 * wake up on disconnect
		 * wake up on magic packet
		 * wake up on pattern match, up to 6 patterns of 1-256 bytes
	HT Capability overrides:
		 * MCS: ff ff ff ff ff ff ff ff ff ff
		 * maximum A-MSDU length
		 * supported channel width
		 * short GI for 40 MHz
		 * max A-MPDU length exponent
		 * min MPDU start spacing
	Device supports TX status socket option.
	Device supports HT-IBSS.
	Device supports low priority scan.
	Device supports scan flush.
	Device supports AP scan.

I had been discussing this on the hostapd mailing list, and one of the developers mentioned:

It's not hostapd, but the regulatory code or driver that has marked the
channel as not allowed for AP mode:
5785 MHz [157] (17.0 dBm) (passive scanning, no IBSS)

The passive scanning part there indicates that no radiation can be
initiated on the channel (i.e., need to see a master device operating on
the channel before transmitting any frames).

So, the conclusion of that was 1) it's not hostapd's fault (agreed) 2) at present, there are exactly zero usable band-2 frequencies (all either disabled, or passive-scanning) (agreed) 3) this is regulatory code and/or driver's fault (disagree somewhat)

I've semi-conclusively ruled out that it isn't regulatory code that is causing these restrictions.

So, perhaps it's the driver and/or hardware that's causing this? I don't think so:

zack@helios ~ % lspci -s 10:
10:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)

The card itself is a mPCIe 2x2 Ubiquiti SR71, which is attached to a mPCIe -> PCIe adapter.

So, the question is, how can I get 5GHz channels out of passive-scan mode and/or not-disabled? (or, something greater than exactly zero channels available for AP mode?)

Last edited by buhman (2013-04-28 16:57:53)

Offline

#2 2013-04-29 16:00:34

Strike0
Member
From: Germany
Registered: 2011-09-05
Posts: 1,277

Re: 802.11a band 2 frequencies do not match reported regulatory domain.

Welcome to the forums.
One thing you can try is re-check, if you get better results with different wireless-n settings: http://wireless.kernel.org/en/users/Doc … figuration
The driver might need a+n mode for 5Mhz AP operation according to other posts.
Another thing to follow up: The openwrt 12.09 (out last week) implemented patches for  _experimental_ ath5k/9k support for 5Mhz. I have no experience with it on ath9k myself, but if it is new to openwrt and they call the new feature experimental - the vanilla driver very probably is the key to your problem.

Offline

Board footer

Powered by FluxBB