Issue with 5GHz AP in "Radar Detection" channels

kostiur · June 9, 2020, 11:57pm

Hi! I'm trying to set up an AP for 5GHz for a channel in the "Radar Detection" section (in this post I used 140), however I am not able to get it working, and always get the message in the Wireless tab of luci:

radio1 -- Generic 802.11nac: Device is not active

disabled -- SSID: test | Mode: Master: Wireless is not associated

This is the important output of iw list:

		Frequencies:
			* 5180 MHz [36] (23.0 dBm)
			* 5200 MHz [40] (23.0 dBm)
			* 5220 MHz [44] (23.0 dBm)
			* 5240 MHz [48] (23.0 dBm)
			* 5260 MHz [52] (20.0 dBm) (radar detection)
			* 5280 MHz [56] (20.0 dBm) (radar detection)
			* 5300 MHz [60] (20.0 dBm) (radar detection)
			* 5320 MHz [64] (20.0 dBm) (radar detection)
			* 5500 MHz [100] (26.0 dBm) (radar detection)
			* 5520 MHz [104] (26.0 dBm) (radar detection)
			* 5540 MHz [108] (26.0 dBm) (radar detection)
			* 5560 MHz [112] (26.0 dBm) (radar detection)
			* 5580 MHz [116] (26.0 dBm) (radar detection)
			* 5600 MHz [120] (26.0 dBm) (radar detection)
			* 5620 MHz [124] (26.0 dBm) (radar detection)
			* 5640 MHz [128] (26.0 dBm) (radar detection)
			* 5660 MHz [132] (26.0 dBm) (radar detection)
			* 5680 MHz [136] (26.0 dBm) (radar detection)
			* 5700 MHz [140] (26.0 dBm) (radar detection)
			* 5720 MHz [144] (disabled)
			* 5745 MHz [149] (13.0 dBm)
			* 5765 MHz [153] (13.0 dBm)
			* 5785 MHz [157] (13.0 dBm)
			* 5805 MHz [161] (13.0 dBm)
			* 5825 MHz [165] (13.0 dBm)
			* 5845 MHz [169] (13.0 dBm)
			* 5865 MHz [173] (13.0 dBm)

And this is my log file

Tue Jun  9 23:38:02 2020 daemon.notice netifd: radio1 (3076): command failed: Not supported (-95)
Tue Jun  9 23:38:02 2020 user.notice mac80211: Failed command: iw phy phy1 set distance 0
Tue Jun  9 23:38:02 2020 daemon.err hostapd: Configuration file: /var/run/hostapd-phy1.conf                            
Tue Jun  9 23:38:03 2020 kern.warn kernel: [  998.307220] ath10k_ahb a800000.wifi: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
Tue Jun  9 23:38:03 2020 kern.warn kernel: [  998.307269] ath10k_ahb a800000.wifi: msdu-desc: 2500  skid: 32 
Tue Jun  9 23:38:03 2020 kern.info kernel: [  998.342835] ath10k_ahb a800000.wifi: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
Tue Jun  9 23:38:03 2020 kern.info kernel: [  998.343827] ath10k_ahb a800000.wifi: wmi print 'free: 56528 iram: 23400 sram: 32520'
Tue Jun  9 23:38:04 2020 kern.warn kernel: [  998.603796] ath10k_ahb a800000.wifi: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Tue Jun  9 23:38:04 2020 kern.info kernel: [  998.604111] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Tue Jun  9 23:38:04 2020 kern.info kernel: [  998.619921] br-lan: port 2(wlan1) entered blocking state
Tue Jun  9 23:38:04 2020 kern.info kernel: [  998.619969] br-lan: port 2(wlan1) entered disabled state
Tue Jun  9 23:38:04 2020 kern.info kernel: [  998.625595] device wlan1 entered promiscuous mode
Tue Jun  9 23:38:04 2020 daemon.notice hostapd: wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
Tue Jun  9 23:38:04 2020 daemon.notice hostapd: Channel 144 (secondary) not allowed for AP mode, flags: 0x109 RADAR
Tue Jun  9 23:38:04 2020 daemon.warn hostapd: wlan1: IEEE 802.11 Configured channel (140) not found from the channel list of current mode (2) IEEE 802.11a
Tue Jun  9 23:38:04 2020 daemon.warn hostapd: wlan1: IEEE 802.11 Hardware does not support configured channel
Tue Jun  9 23:38:04 2020 daemon.err hostapd: Could not select hw_mode and channel. (-3)
Tue Jun  9 23:38:04 2020 daemon.notice hostapd: wlan1: interface state COUNTRY_UPDATE->DISABLED
Tue Jun  9 23:38:04 2020 daemon.notice hostapd: wlan1: AP-DISABLED                
Tue Jun  9 23:38:04 2020 daemon.err hostapd: wlan1: Unable to setup interface.  
Tue Jun  9 23:38:04 2020 daemon.notice hostapd: wlan1: interface state DISABLED->DISABLED
Tue Jun  9 23:38:04 2020 daemon.notice hostapd: wlan1: AP-DISABLED                
Tue Jun  9 23:38:04 2020 daemon.notice hostapd: wlan1: CTRL-EVENT-TERMINATING     
Tue Jun  9 23:38:04 2020 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan1 wasn't started
Tue Jun  9 23:38:04 2020 daemon.notice hostapd: nl80211: deinit ifname=wlan1 disabled_11b_rates=0
Tue Jun  9 23:38:04 2020 kern.info kernel: [  998.634745] device wlan1 left promiscuous mode
Tue Jun  9 23:38:04 2020 kern.info kernel: [  998.635199] br-lan: port 2(wlan1) entered disabled state
Tue Jun  9 23:38:04 2020 kern.warn kernel: [  998.768951] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 0
Tue Jun  9 23:38:04 2020 daemon.notice netifd: radio1 (3076): cat: can't open '/var/run/wifi-phy1.pid': No such file or directory  
Tue Jun  9 23:38:04 2020 daemon.notice netifd: radio1 (3076): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process  path (/proc/exe)
Tue Jun  9 23:38:04 2020 daemon.notice netifd: radio1 (3076): Command failed: Invalid argument
Tue Jun  9 23:38:04 2020 daemon.notice netifd: radio1 (3076): Device setup failed: HOSTAPD_START_FAILED

I've tried with multiple others, and this also happens for them, not only for the example channel 140.

lantis1008 · June 10, 2020, 4:17am

It tells you there what's wrong. 144 is not allowed, but you're using settings which try to use it.

Make your test case simpler.
Try a 20MHz channel on 52. This should not require any additional channels.
Then try a 40 and 80 on 52 as well. They should all be valid according to what you've posted above.

If that works, try the same tests at higher channels. But of course note that if you choose a width which bonds multiple channels, and one of those channels isn't allowed, it isn't going to work.

Posting the results of the simpler test cases (what works what doesn't) will help people to help you.

kostiur · June 10, 2020, 11:31am

You're right, I should start with simpler examples and go from there. but I'd already tried all of that.
Anyway, I found the solution. Apparently luci doesn't deal well with starting an interface in a DFS channel. If I set it up and /etc/init.d/network restart, everything works out... I feel dumb for wasting so much time with such a simple solution.

lleachii · June 10, 2020, 1:31pm

Incorrect.

mk24 · June 11, 2020, 10:55am

On the CLI I have had incidences of the wifi command not properly starting a new wireless configuration, but a full network restart did.

system · June 21, 2020, 10:55am

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.