Specifications

Altitude 35x0 Access Point Product Reference Guide 289
● There are two LAN interfaces on the AP35xx LAN port: LAN1 and LAN2. By default, LAN1 is the
primary LAN connection. LAN2 is only used for tunneled traffic.
● An AP can use its LAN1 interface on the LAN port 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.
● Extreme Networks recommends using the LAN1 interface for adoption in multi-cell deployments.
● If you have multiple independent WLANs mapped to different VLANs, the AP's LAN1 interface
requires trunking be enabled with the correct management and native VLAN IDs configured.
Additionally, the AP needs to be connected to a 802.1q trunk port on the wired controller.
● Be aware IPSec Mode supports NAT Traversal (NAT-T).
Extended WLANs Only
An extended WLAN configuration forces all MU traffic through the controller (tunneled traffic). No
wireless traffic is locally bridged at the AP.
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 controller, the following configuration updates
are made automatically:
● The AP’s LAN2 subnet becomes enabled
● All extended VLANs are mapped to LAN2.
NOTE
MUs on the same WLAN associated to the AP can communicate locally at the AP Level without going through the
controller. If this scenario is undesirable, the access point's MU-to-MU disallow option should be enabled.
Independent WLANs Only
An independent WLAN configuration forces all MU traffic be bridged locally by the AP. No wireless
traffic is tunneled back to the controller. Each extended WLAN is mapped to the access point's LAN1
interface. The only traffic between the controller and the AP are control messages (for example,
heartbeats, statistics and configuration updates).
Extended WLANs with Independent WLANs
An AP can have both extended WLANs and independent WLANs operating in conjunction. When used
together, MU traffic from extended WLANs go back to the controller 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.