[PATCH v5 13/17] mesh: do not allow pri/sec channel switch

Peter Oh peter.oh at bowerswilkins.com
Tue Jun 12 10:50:54 PDT 2018

On 06/12/2018 02:31 AM, Jouni Malinen wrote:
> I don't really justification for this in more common use cases since the
> default behavior should always work fine without needing such exceptions
> to allow hardcoded skipping of pri/sec channel switch. It is possible
> that something is missing from the current implementation on
> automatically doing this correctly and that can obviously be fixed, but
> this should work just fine as long as you start the virtual interfaces
> in the sequence that selects the 20 MHz channel to be used as the
> primary channel first.
I understood your opinion. This exception may be not the right approach 
and could hide an existing issue (or bug if exist). But my patch series 
is to make mesh point able to use DFS channels, not to fix existing 
issue, so I'll remove this patch from the series in next revision.
We could discuss this exception later separately about why we need this 
exception and what to improve to avoid such exception.


More information about the Hostap mailing list