On Wednesday 25 January 2017 11:50 PM, Jean-Pierre Tosoni wrote: >> -----Message d'origine----- >> De : linux-wireless-owner@xxxxxxxxxxxxxxx [mailto:linux-wireless- >> owner@xxxxxxxxxxxxxxx] De la part de Vasanthakumar Thiagarajan >> Envoyé : mercredi 25 janvier 2017 12:31 >> À : johannes@xxxxxxxxxxxxxxxx >> Cc : linux-wireless@xxxxxxxxxxxxxxx; Vasanthakumar Thiagarajan >> Objet : [RFC 2/3] cfg80211: Disallow moving out of operating DFS channel >> in non-ETSI >> >> For non-ETSI regulatory domain, CAC result on DFS channel may not be valid >> once moving out of that channel (as done during remain-on-channel, >> scannning and off-channel tx). >> Running CAC on an operating DFS channel after every off-channel operation >> will only add complexity and disturb the current link. Better do not allow >> any off-channel switch from a DFS operating channel in non-ETSI domain. >> > > Moving out should be forbidden only to "master" devices i.e. AP, mesh, > ad-hoc. > "Slave" devices i.e. client stations, are not responsible for detecting > radars, hence, they can do an off-channel scan and go back to a "DFS > operating channel" without waiting for CAC. > > It looks like your patch would forbid multichannel scan ? > > No, this patch forbids off-channel switch only for DFS master device. cfg80211_beaconing_iface_active() checks if it is a beaconing interface. I'll mention this in the commit log. Vasanth
