Specifications

BPG_11n_v1.0 | Page 24
Bridge ESS Profiles
Traffic can be tunneled back to the controller or be bridged locally. There is a setting in the
ESS profile that sets the ESS to tunneled (default) or bridged. An AP300 can have both types
of ESS profiles on a single radio.
A tunneled ESS is generally the preferred method; however there are network designs where
it makes more sense to keep data traffic local. This is where bridged ESS profiles make sense.
For example, if there is a branch office that does not have a controller on site but does have
their own set of IT servers local, it would not be desirable for traffic to traverse WAN links
(twice) to get to those local services. With bridged ESS profiles the local traffic stays local.
The table below lists which features are/are not supported with bridged ESS Profiles.
Feature
Supported
Virtual Port
Yes
Band Steering!!
Yes
Asset Tag Tracking
(Aeroscout)
Yes
802.1x Radius-based Mac
Filtering !!!!
Yes
Locationing
Yes
L2/L3 discovery
Yes
DHCP option 43-based AP
discovery
Yes
Load Balancing
Yes
Rogue detection/
mitigation
Yes
IPV6, Apple Talk, Air
Fortress forwarding!
Yes
802.1q VLAN Tagging
Yes
Meru QoS-rule based QoS
No
Station MELF Event
(Station-log)!
No
IGMP Snooping
No
Captive Portal!
No
Inter Controller Roaming
No
UDP broadcast control
No
RADIUS Assigned
Dynamic VLANs
No
Captive Portal!
No
Call Admission Control
No
MERU BEST PRACTICES GUIDE | 11n Design, Implementation and Optimization