User's Manual

Table Of Contents
Fortress ES-Series CLI Guide: Networking and Radio Configuration
65
3.4.9.9 BSS VLANs Settings
NOTE: Packets
belonging to a
BSS's native VLAN, as
established by
VlanId
,
are always allowed to
traverse a trunk link; so
untagged packets are
always allowed.
VlanId
assigns a VLAN ID between
1
and
4094
to the BSS. By
default all interfaces are assigned VLAN ID 1. If the VLAN ID
you enter is not already present in the
Active VLAN Table
(Section 3.11.1), it will be automatically added. A new VLAN ID
configured in this way will not yet be associated with an IPv4
address. Refer to Section 3.11.1 for instructions on associating
a new VLAN with an IP address.
SwitchingMode determines whether the BSS will act as a
trunk
or
access
(the default) interface in Fortress’s VLANs
implementation.
SwitchingMode is automatically fixed on
Trunk
when WDS is enabled.
AllowAll (or
-vlanAllowAll
) and Table (or
-vlanActiveList
)
configure VLAN trunk filtering for the interface, when the
interface
SwitchingMode is
trunk
. When AllowAll is
Y
(yes,
the default), no filtering takes place on the interface. If you set
AllowAll to
n
(no), the interface accepts only packets with
VLAN tags matching a VLAN ID that has been specified for the
BSS using the
Table option. (When SwitchingMode is
access
,
these options have no effect.)
3.4.9.10 BSS Fortress Security Zone
Zone places the BSS in the Mesh Point’s
clear
or
encrypted
zone.
Traffic in the encrypted zone is subject to Fortress’s Mobile
Security Protocol (MSP), as configured on the Mesh Point itself
(refer to Section 4.1).
By default BSSs are created in the encrypted zone. When
WDS is enabled, the BSS’s
Zone value is fixed on
encrypted
and cannot be changed.
Configuring a BSS to reside in the clear zone exempts all traffic
on that BSS from MSP.
Standard Wi-Fi security protocols can be applied to the traffic
on a BSS (Section 3.4.9.15, below), regardless of whether the
BSS is in the
clear
or
encrypted
zone.
3.4.9.11 FastPath Mesh BSS Cost Offset
The
UCostOffset setting applies only when FastPath Mesh
(Section 3.2) is licensed and enabled on the Mesh Point.
UCostOffset specifies a non-negative integer, between
0
(zero, the default) and
4,294,967,295
, by which you can weight
the interface more or less heavily in the FP Mesh cost
equation. The higher the offset, the less attractive the interface,
with the maximum (
4,294,967,295) causing the interface to
never be used to route network traffic.