Technical data

Bridging Versus Tunneling

Virtual Port : off

Overflow for : vcell_ESS

WMM Support : off

APSD Support : off

DTIM Period (number of beacons) : 1

Dataplane Mode : tunneled

AP VLAN Tag : 0

AP VLAN Priority : off

Countermeasure : on

Multicast MAC Transparency : off

Band Steering Mode : disable

Band Steering Timeout(seconds) : 5

Bridging Versus Tunneling

The bridged AP feature allows APs to be installed and managed at locations separated

from the controller by a WAN or ISP, for example, in a satellite office. Encryption can

be enabled on the bridged connection to provide security over ISP-based connec-

tions.

The controller, through a keep-alive signal, monitors the remote AP. Remote APs can

exchange control information, including authentication and accounting information

with the controller, but are unable to exchange data. (Remote bridged APs can,

however, exchange data with other APs within their subnet.)

Supported Features for Bridged ESS Profiles

The features supported by bridged ESS profiles are:

 WMM QoS AP300/AP400

 AP300/AP400 and AP1000 support bridged ESS profiles with a static VLAN. AP150

supports bridged ESS profiles without VLAN tagging.

 Virtual Cell/Virtual Port (AP300/AP400, AP1000)

 802.1X authentication (dynamic WEP, WPA, WPA2 or MIXED)

 Multiple ESSIDs

 All security modes/options except Captive Portal (both static and dynamic keying)

 RADIUS authentication and accounting ACL-based and RADIUS-based MAC filtering

 ACL-based and Radius-based MAC filtering

 Mapping IP DSCP or 802.1p to WMM Access Categories (AP300/AP400)

Because remote APs cannot exchange data-plane traffic (including DHCP) with the

controller, certain Meru Wireless LAN features are not available for remote AP config-

urations. These include: