Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <99ae192566a7c5ae91c6ee92b8c4ddb41a29e34e.camel@sipsolutions.net>
Subject: Re: RFC: Remote Off-Channel CAC for DFS
From:   Johannes Berg <johannes@sipsolutions.net>
To:     Markus Theil <markus.theil@tu-ilmenau.de>,
        linux-wireless@vger.kernel.org
Date:   Mon, 29 Jun 2020 21:35:40 +0200
In-Reply-To: <c49513d5-9da7-5545-02e1-ff368f9f6961@tu-ilmenau.de> (sfid-20200629_203549_647727_9A89A56D)
References: <c49513d5-9da7-5545-02e1-ff368f9f6961@tu-ilmenau.de>
         (sfid-20200629_203549_647727_9A89A56D)
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.3 (3.36.3-1.fc32) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

Hi,

On Mon, 2020-06-29 at 19:40 +0200, Markus Theil wrote:
> When using DFS channels, it would be nice, if I could dedicate a small
> amount of interfaces only to CAC checking channels and set them
> available or unavailable on multiple other remote APs/Mesh Points in
> order to use them, when switching to lower utilized channels without
> going through a full CAC.
> 
> Whats the opinion on the mailing list about adding a new command to
> nl80211 in order to set the DFS state of a currently not used channel
> after a Off-Channel CAC on another device nearby, but not on the same
> host? The parameters would roughly be the same as for a channel switch
> and an additional DFS channel state. Internally, I would trigger the DFS
> state sync code between multiple interfaces.

But wait, don't we already sync this within the kernel?

johannes