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

[Michal Kazior]

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."