DFS start_dfs_cac() failed, -1 / nl80211: Failed to start radar

Tue Oct 6 06:38:08 PDT 2015

You don't seem to have the radar detection support compiled in.
There's no "radar detect widths" in interface combinations.

You need to compile kernel/ath9k with CONFIG_ATH9K_DFS_CERTIFIED.

Micha?

On 6 October 2015 at 15:14, J Sahana <J.Sahana at aricent.com> wrote:
> Hi Michal,
>
> This is the output of iw list, I don?t see this radar detection here....
>
> Wiphy phy1
> max # scan SSIDs: 4
> max scan IEs length: 2257 bytes
> max # sched scan SSIDs: 0
> max # match sets: 0
> Retry short limit: 7
> Retry long limit: 4
> Coverage class: 0 (up to 0m)
> Device supports RSN-IBSS.
> Device supports AP-side u-APSD.
> Device supports T-DLS.
> 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 0x7 RX 0x7
> Configured Antennas: TX 0x7 RX 0x7
> Supported interface modes:
>  * IBSS
>  * managed
>  * AP
>  * AP/VLAN
>  * WDS
>  * monitor
>  * P2P-client
>  * P2P-GO
> Band 1:
> Capabilities: 0x11ef
> RX LDPC
> HT20/HT40
> SM Power Save disabled
> RX HT20 SGI
> 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-23
> Bitrates (non-HT):
> * 0.0 Mbps
> * 0.0 Mbps (short preamble supported)
> * 0.0 Mbps (short preamble supported)
> * 0.0 Mbps (short preamble supported)
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> Frequencies:
> * 2412 MHz [1] (0.0 dBm)
> * 2417 MHz [2] (0.0 dBm)
> * 2422 MHz [3] (0.0 dBm)
> * 2427 MHz [4] (0.0 dBm)
> * 2432 MHz [5] (0.0 dBm)
> * 2437 MHz [6] (0.0 dBm)
> * 2442 MHz [7] (0.0 dBm)
> * 2447 MHz [8] (0.0 dBm)
> * 2452 MHz [9] (0.0 dBm)
> * 2457 MHz [10] (0.0 dBm)
> * 2462 MHz [11] (0.0 dBm)
> * 2467 MHz [12] (disabled)
> * 2472 MHz [13] (disabled)
> * 2484 MHz [14] (disabled)
> Band 2:
> Capabilities: 0x11ef
> RX LDPC
> HT20/HT40
> SM Power Save disabled
> RX HT20 SGI
> 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-23
> Bitrates (non-HT):
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> Frequencies:
> * 5180 MHz [36] (0.0 dBm) (no IR)
> * 5200 MHz [40] (0.0 dBm) (no IR)
> * 5220 MHz [44] (0.0 dBm) (no IR)
> * 5240 MHz [48] (0.0 dBm) (no IR)
> * 5260 MHz [52] (0.0 dBm) (no IR, radar detection)
>   DFS state: usable (for 5864 sec)
>   DFS CAC time: 0 ms
> * 5280 MHz [56] (0.0 dBm) (no IR, radar detection)
>   DFS state: usable (for 5864 sec)
>   DFS CAC time: 0 ms
> * 5300 MHz [60] (0.0 dBm) (no IR, radar detection)
>   DFS state: usable (for 5864 sec)
>   DFS CAC time: 0 ms
> * 5320 MHz [64] (0.0 dBm) (no IR, radar detection)
>   DFS state: usable (for 5864 sec)
>   DFS CAC time: 0 ms
> * 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] (0.0 dBm) (no IR)
> * 5765 MHz [153] (0.0 dBm) (no IR)
> * 5785 MHz [157] (0.0 dBm) (no IR)
> * 5805 MHz [161] (0.0 dBm) (no IR)
> * 5825 MHz [165] (0.0 dBm) (no IR)
> Supported commands:
>  * new_interface
>  * set_interface
>  * new_key
>  * start_ap
>  * new_station
>  * set_bss
>  * authenticate
>  * associate
>  * deauthenticate
>  * disassociate
>  * join_ibss
>  * 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
>  * set_mcast_rate
>  * channel_switch
>  * set_qos_map
>  * 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
> software interface modes (can always be added):
>  * AP/VLAN
>  * monitor
> valid interface combinations:
>  * #{ managed } <= 2048, #{ AP } <= 8, #{ P2P-client, P2P-GO } <= 1,
>    total <= 2048, #channels <= 1, STA/AP BI must match
>  * #{ WDS } <= 2048,
>    total <= 2048, #channels <= 1, STA/AP BI must match
> 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 SAE with AUTHENTICATE command
> Device supports low priority scan.
> Device supports scan flush.
> Device supports AP scan.
> Device supports per-vif TX power setting
> P2P GO supports CT window setting
> Driver supports a userspace MPM
> Device supports active monitor (which will ACK incoming frames)
> Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
> Wiphy phy0
> max # scan SSIDs: 4
> max scan IEs length: 2257 bytes
> max # sched scan SSIDs: 0
> max # match sets: 0
> Fragmentation threshold: 1000
> RTS threshold: 2346
> Retry short limit: 7
> Retry long limit: 4
> Coverage class: 0 (up to 0m)
> Device supports RSN-IBSS.
> Device supports AP-side u-APSD.
> Device supports T-DLS.
> 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 0x7 RX 0x7
> Configured Antennas: TX 0x7 RX 0x7
> Supported interface modes:
>  * IBSS
>  * managed
>  * AP
>  * AP/VLAN
>  * WDS
>  * monitor
>  * P2P-client
>  * P2P-GO
> Band 1:
> Capabilities: 0x11ef
> RX LDPC
> HT20/HT40
> SM Power Save disabled
> RX HT20 SGI
> 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-23
> Bitrates (non-HT):
> * 0.0 Mbps
> * 0.0 Mbps (short preamble supported)
> * 0.0 Mbps (short preamble supported)
> * 0.0 Mbps (short preamble supported)
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> Frequencies:
> * 2412 MHz [1] (0.0 dBm)
> * 2417 MHz [2] (0.0 dBm)
> * 2422 MHz [3] (0.0 dBm)
> * 2427 MHz [4] (0.0 dBm)
> * 2432 MHz [5] (0.0 dBm)
> * 2437 MHz [6] (0.0 dBm)
> * 2442 MHz [7] (0.0 dBm)
> * 2447 MHz [8] (0.0 dBm)
> * 2452 MHz [9] (0.0 dBm)
> * 2457 MHz [10] (0.0 dBm)
> * 2462 MHz [11] (0.0 dBm)
> * 2467 MHz [12] (disabled)
> * 2472 MHz [13] (disabled)
> * 2484 MHz [14] (disabled)
> Band 2:
> Capabilities: 0x11ef
> RX LDPC
> HT20/HT40
> SM Power Save disabled
> RX HT20 SGI
> 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-23
> Bitrates (non-HT):
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> * 0.0 Mbps
> Frequencies:
> * 5180 MHz [36] (0.0 dBm) (no IR)
> * 5200 MHz [40] (0.0 dBm) (no IR)
> * 5220 MHz [44] (0.0 dBm) (no IR)
> * 5240 MHz [48] (0.0 dBm) (no IR)
> * 5260 MHz [52] (0.0 dBm) (no IR, radar detection)
>   DFS state: usable (for 5864 sec)
>   DFS CAC time: 0 ms
> * 5280 MHz [56] (0.0 dBm) (no IR, radar detection)
>   DFS state: usable (for 5864 sec)
>   DFS CAC time: 0 ms
> * 5300 MHz [60] (0.0 dBm) (no IR, radar detection)
>   DFS state: usable (for 5864 sec)
>   DFS CAC time: 0 ms
> * 5320 MHz [64] (0.0 dBm) (no IR, radar detection)
>   DFS state: usable (for 5864 sec)
>   DFS CAC time: 0 ms
> * 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] (0.0 dBm) (no IR)
> * 5765 MHz [153] (0.0 dBm) (no IR)
> * 5785 MHz [157] (0.0 dBm) (no IR)
> * 5805 MHz [161] (0.0 dBm) (no IR)
> * 5825 MHz [165] (0.0 dBm) (no IR)
> Supported commands:
>  * new_interface
>  * set_interface
>  * new_key
>  * start_ap
>  * new_station
>  * set_bss
>  * authenticate
>  * associate
>  * deauthenticate
>  * disassociate
>  * join_ibss
>  * 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
>  * set_mcast_rate
>  * channel_switch
>  * set_qos_map
>  * 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
> software interface modes (can always be added):
>  * AP/VLAN
>  * monitor
> valid interface combinations:
>  * #{ managed } <= 2048, #{ AP } <= 8, #{ P2P-client, P2P-GO } <= 1,
>    total <= 2048, #channels <= 1, STA/AP BI must match
>  * #{ WDS } <= 2048,
>    total <= 2048, #channels <= 1, STA/AP BI must match
> 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 SAE with AUTHENTICATE command
> Device supports low priority scan.
> Device supports scan flush.
> Device supports AP scan.
> Device supports per-vif TX power setting
> P2P GO supports CT window setting
> Driver supports a userspace MPM
> Device supports active monitor (which will ACK incoming frames)
> Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
>
> Regards,
> Sahana
>
> -----Original Message-----
> From: Michal Kazior [mailto:michal.kazior at tieto.com]
> Sent: Tuesday, October 06, 2015 5:52 PM
> To: J Sahana <J.Sahana at aricent.com>
> Cc: hostap at lists.shmoo.com
> Subject: Re: DFS start_dfs_cac() failed, -1 / nl80211: Failed to start radar
>
> Post your `iw list` so we can verify if your device advertises radar detection support in the first place, please.
>
>
> Micha?
>
> On 6 October 2015 at 14:10, J Sahana <J.Sahana at aricent.com> wrote:
>> Michal,
>>
>> Thanks for your quick reply. I'm running this hostapd on Freescale board, with ath10k driver.
>> Iw reg get shows DFS set to FCC with country as US. Please let me know what other details do you need regarding the board, as I'm accesing it remotely I don?t have much details about its configurations.
>>
>> Regards,
>> Sahana
>>
>>
>> -----Original Message-----
>> From: Michal Kazior [mailto:michal.kazior at tieto.com]
>> Sent: Tuesday, October 06, 2015 4:27 PM
>> To: J Sahana <J.Sahana at aricent.com>
>> Subject: Re: DFS start_dfs_cac() failed, -1 / nl80211: Failed to start
>> radar
>>
>> On 6 October 2015 at 12:36, J Sahana <J.Sahana at aricent.com> wrote:
>>> Hi Michal,
>>>
>>> I?m trying to run hostapd 2.3 version in 5GHz with DFS enabled. But
>>> it?s no running and getting similar error as seen in the thread on
>>> the net (http://lists.shmoo.com/pipermail/hostap/2014-August/030776.html).
>>> So thought of taking some help from you.  Can you please let me know
>>> the problem here. Unlike the issue on the thread we are using 20MHz
>>> bandwidth, but still hostapd is not coming to run state.
>>>
>>>
>>>
>>> This is the below snippet that is seen:
>> [...]
>>
>> Avoid e-mailing me privately, please. Instead always go to the mailing list. It's much more productive because not only I, but many others, might be able to help you.
>>
>> As for the failure you're seeing: hard to tell from this log snippet.
>> This could very well be regulatory problem (you could check if you have DFS domain other than UNSET via `iw reg get`, e.g. FCC or ETSI) or interface combination (are you running any other virtual interfaces on this radio chip, e.g. client mode?).
>>
>>
>> Micha?
>> "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."