Meru Technical Note - How to configure Bridged and Tunneled settings in ESSID configuration?
How to configure Bridged and Tunneled settings in ESSID configuration?
Scope
KB Article Type: Configuration
RELATED PRODUCTS: controller
RELATED SOFTWARE VERSIONS: N/A
KEYWORDS: ESSID, Tunnel, dataplane
Solution
By default the ESSID when configured is for tunneled traffic.
This command determines the type of traffic that is passed between the controller and the AP. By default, tunneled mode is active where a controller and an AP are connected with a data tunnel so that data from a mobile station is tunneled to the controller from the AP and vice-versa.
When bridged mode is used, an AP can be installed and managed at a location separated from the controller by a WAN or ISP, for example a satellite office. The controller monitors the remote APs through a keep-alive signal. Remote APs can exchange control information, including authentication and accounting information, with the controller but are unable to exchange data. Remote APs can exchange data with other APs within their subnet.
CONFIGURATION STEPS:
CLI Steps:
STEP 1: Enter the ESSID configuration mode and set the dataplane mode to bridged:
controller# configure terminal
controller(config)# essid profile_name
controller(config-ap)# dataplane bridged
controller(config-ap)# exit
STEP 2: To secure the bridged connection over the public airwaves, use the AP Configuration mode command dataplane-encryption:
controller# configure terminal
controller(config)# ap ap#
controller(config-ap)# dataplane-encryption on
controller(config-ap)# exit
LIMITATIONS IF ANY: Because remote APs cannot exchange data-plane traffic (including DHCP) with the controller, these System Director features are not available for Remote AP configuration: Virtual Cell, VLAN, Captive Portal, L3 Mobility, and QoS.