On Mon, 2015-11-30 at 11:56 +0200, Jouni Malinen wrote: > On Mon, Nov 23, 2015 at 07:27:17PM +0100, Michal Sojka wrote: > > Regulatory rules are applied to channels as if the channel is at > > least > > 20 MHz wide. This is a problem when dealing with 5 and 10 MHz > > channels > > because side channels of a regulatory rule get disabled even when > > they > > fall into rule's frequency range. > > > > This problem was already fixed in commit > > 4edd56981c8fbb349b1529a2feaf772636eb1c83, but only for custom > > regulatory > > domains provided by drivers. Here we fix it also for all other > > (e.g. > > user-supplied) regulatory domains. > > > > Before that, similar commit was > > reverted (e33e2241e272eddc38339692500bd1c7d8753a77) due to it > > allowing > > running AP on channel 12 in the US regulatory domain. > > I'm afraid this new patch needs to be reverted as well since it > allows active scanning on channel 12 in the US regulatory domain. > I.e., every full scan with this commit included results in a Probe > Request frame being sent on channel 12.. > I've dropped it from my tree. johannes
