Motorola RFS Series Reference Manual page 479

• An AAP can use its LAN1 interface or WAN interface for adoption. The default gateway interface is set
to LAN1. If the WAN Interface is used, explicitly configure WAN as the default gateway interface.
• Motorola recommends using the LAN1 interface for adoption in multi-cell deployments.
• If you have multiple independent WLANs mapped to different VLANs, the AAP's LAN1 interface requires
trunking be enabled with the correct management and native VLAN IDs configured. Additionally, the AAP
needs to be connected to a 802.1q trunk port on the wired switch.
• Be aware IPSec Mode supports NAT Traversal (NAT-T).
B.2.2 Extended WLANs Only
An extended WLAN configuration forces all MU traffic through the switch. No wireless traffic is locally
bridged by the AAP.
Each extended WLAN is mapped to the Access Point's virtual LAN2 subnet. By default, the Access Point's
LAN2 is not enabled and the default configuration is set to static with IP addresses defined as all zeros. If
the extended VLAN option is configured on the switch, the following configuration updates are made
automatically:
• The AAP's LAN2 subnet becomes enabled
• All extended VLANs are mapped to LAN2.
NOTE: MUs on the same WLAN associated to the AAP can communicate locally at the AP
Level without going through the switch. If this scenario is undesirable, the Access Point's
MU-to-MU disallow option should be enabled.
B.2.3 Independent WLANs Only
An independent WLAN configuration forces all MU traffic be bridged locally by the AAP. No wireless traffic
is tunneled back to the switch. Each extended WLAN is mapped to the Access Point's LAN1 interface. The
only traffic between the switch and the AAP are control messages (for example, heartbeats, statistics and
configuration updates).
B.2.4 Extended WLANs with Independent WLANs
An AAP can have both extended WLANs and independent WLANs operating in conjunction. When used
together, MU traffic from extended WLANs go back to the switch and traffic from independent WLANs is
bridged locally by the AP.
All local WLANs are mapped to LAN1, and all extended WLANs are mapped to LAN2.
B.2.5 Extended VLAN with Mesh Networking
Mesh networking is an extension of the existing wired network. There is no special configuration required,
with the exception of setting the mesh and using it within one of the two extended VLAN configurations.
NOTE: The mesh backhaul WLAN must be an independent WLAN mapped to LAN2. The
switch enforces the WLAN be defined as an independent WLAN by automatically setting
the WLAN to independent when backhaul is selected. The AP ensures the backhaul
WLAN be put on LAN1.
B-9