You are right, it is possible to do it as you comment
(NL80211_CMD_STOP_AP and then NL80211_CMD_START_AP). It is therefore
not necessary a specific command to abort the CAC.
Thank you very much for the clarification and the time spent.
PS: If you use OpenWRT you have to control the STOP and the
On Tue, 2018-09-25 at 10:19 +0200, Enrique Giraldo wrote:
> Add NL80211_CMD_ABORT_CAC to the nl80211 interface.
As Arend pointed out, this really needs a much better commit message.
Please also adjust the subject to have a proper prefix etc. See
What you commented was the first thing that I tried, but doing it, the
radio stays in an inconsistent state and the hostapd is not able to
raise an instance again.
Attached is the log of what is happening:
Tue Sep 25 09:58:10 2018 daemon.notice hostapd: wlan0: DFS-CAC-START
freq=5500 chan=100
On 9/25/2018 11:28 AM, Enrique Giraldo wrote:
The main reason is to be able to stop the CAC when you want to make a
channel switch and the CAC is ongoing. It's true that the radio would
not pass to the next phase, the behavior is the same as when during
the CAC a radar event is detected. In the
The main reason is to be able to stop the CAC when you want to make a
channel switch and the CAC is ongoing. It's true that the radio would
not pass to the next phase, the behavior is the same as when during
the CAC a radar event is detected. In the case of aborting, a later
action is expected,
On 9/25/2018 10:19 AM, Enrique Giraldo wrote:
Add NL80211_CMD_ABORT_CAC to the nl80211 interface.
This one really needs a good motivation. The CAC duration is a hard
requirement so aborting it means that the radio can not proceed to the
next phase. You really need to describe your reasoning
