summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>2021-08-13 10:47:27 +0200
committerMiruna Paun <mrpa@enea.se>2021-08-13 10:43:22 +0100
commit039084cbbb1d580614978037e32708867acf50de (patch)
tree3ce260e9323940188613510ec142b75ac479bc1d
parent1f86725f48a1bcc9ce6d6120dc69def08acebef9 (diff)
downloadnfv-access-documentation-039084cbbb1d580614978037e32708867acf50de.tar.gz
Wireless AP: 802.11ac/n: Different channel number
Note that 802.11n or 802.11ac/n might use a different channel than the one explicitly requested when overlapping BSSes are found in the neighbourhood. Change-Id: I7ab45b00b7d0461fb2dfce0c3c794b99df70a823 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
-rw-r--r--doc/book-enea-edge-getting-started/doc/net_config_options.xml14
1 files changed, 11 insertions, 3 deletions
diff --git a/doc/book-enea-edge-getting-started/doc/net_config_options.xml b/doc/book-enea-edge-getting-started/doc/net_config_options.xml
index 9c9dfe2..a9faf0a 100644
--- a/doc/book-enea-edge-getting-started/doc/net_config_options.xml
+++ b/doc/book-enea-edge-getting-started/doc/net_config_options.xml
@@ -916,15 +916,13 @@
916 </mediaobject> 916 </mediaobject>
917 </figure> 917 </figure>
918 918
919 <note> 919 <para>Only a single Wireless AP is allowed on a physical interface. The
920 <para>Only a single Wireless AP is allowed on a physical interface. The
921 validation of the <literal>wap-capable</literal> interface is done when 920 validation of the <literal>wap-capable</literal> interface is done when
922 adding the Wireless AP, so, in case of an error, the parameters of the 921 adding the Wireless AP, so, in case of an error, the parameters of the
923 <literal>wap-capable</literal> interface must be rechecked. This can be 922 <literal>wap-capable</literal> interface must be rechecked. This can be
924 done by accessing the <emphasis role="bold">Configuration</emphasis> 923 done by accessing the <emphasis role="bold">Configuration</emphasis>
925 menu and selecting <emphasis role="bold">External 924 menu and selecting <emphasis role="bold">External
926 Interfaces</emphasis>.</para> 925 Interfaces</emphasis>.</para>
927 </note>
928 926
929 <note> 927 <note>
930 <para>For the 2.4GHz band, the <literal>802.11 g/n</literal> wireless 928 <para>For the 2.4GHz band, the <literal>802.11 g/n</literal> wireless
@@ -934,6 +932,16 @@
934 and secondary Wireless AP channels will be swapped, resulting in an 932 and secondary Wireless AP channels will be swapped, resulting in an
935 effective channel width of 20MHz instead of 40Mhz being used. 933 effective channel width of 20MHz instead of 40Mhz being used.
936 To avoid this, select another wireless channel.</para> 934 To avoid this, select another wireless channel.</para>
935
936 <para>For the 5GHz band, the <literal>802.11 n</literal> and the
937 <literal>802.11 ac/n</literal> wireless modes can be configured
938 explicitly to use a specific channel number, even when Automatic
939 Channel Selection (<literal>ACS</literal>) is available. For regulatory
940 requirements compliance, channels are scanned in order to avoid
941 overlapping with existing networks. If overlaps are detected,
942 <literal>ACS</literal> will try to find another free channel,
943 resulting in a different channel number being used instead of the one
944 explicitly configured. To avoid this, select another wireless channel.</para>
937 </note> 945 </note>
938 </section> 946 </section>
939</chapter> 947</chapter>