.. _example_interfaces_wlan_blockedchannels:
################
Blocked Channels
################
The following scenarios show how to define a ``blocked-channels`` list,
which tells the auto-channel selection algorithm the channels to skip
when selecting the best channel. In practical terms, the behavior is
the opposite of the channel plan where channels are explicitly
allowed.
*******************************************
Non-Overlapping Channels On The 2.4GHz Band
*******************************************
Description
===========
In this example, the 2.4 GHz radio controller will be configured to use
``auto-channel selection`` with channel plan ``1,6,11``. This configuration
is very common because this is the largest list of non-overlapping channels on
the 2.4 GHz band, ensuring the AP will not cause adjacent-channel interference.
Scenario
========
.. include:: blockedchannels/non-overlappingchannelsonthe2.4ghzband
.. raw:: html
*************************************
Non-Weather Channels On The 5GHz Band
*************************************
Description
===========
In this example, the 5 GHz radio controller will be configured to use
``auto-channel selection`` with channel plan ``${allowed_channels}``. This configuration
is used to avoid selecting weather channels which require 10 minutes of Channel
Availability Check (CAC) before they start working. Weather channels are ``${blocked_channels}``.
Scenario
========
.. include:: blockedchannels/non-weatherchannelsonthe5ghzband
.. raw:: html
***********************************
Non-Radar Channels On The 5GHz Band
***********************************
Description
===========
In this example, the 5 GHz radio controller will be configured to use
``auto-channel selection`` with channel plan ``${allowed_channels}``. This configuration is
used to avoid selecting radar channels (which require at least 1 minute of CAC before they
start working): ``${blocked_channels}``.
Scenario
========
.. include:: blockedchannels/non-radarchannelsonthe5ghzband
.. raw:: html