Technical data

Bridged AP300 in a Remote Location

When bridged mode is configured in an ESSID, an AP using that ESSID can be installed

and managed at a location separated from the controller by a WAN or ISP, for example

at a satellite office. The controller monitors remote APs with a keep-alive signal.

Remote APs exchange control information, including authentication and accounting

information, with the controller but cannot exchange data. Remote APs exchange

data with other APs within their subnet.

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:

 QoS

 Captive Portal

 L3 mobility

The features that are available are:

 VLAN

 Virtual Cell

 802.1X authentication

 High user density

 Multiple ESSIDs

 Dataplane encryption for backhoe on L3 tunnel with AP150s

Configure Bridged Mode with the Web UI

Configure bridged mode when you add or modify an ESS with the Web UI; for direc-

tions, see Add an ESS with the Web UI.

Configure Bridged Mode with the CLI

This example creates the ESSID abcjk, sets its mode to bridged, assigns a tag, and

then gives top priority to abcjk.

test (config-essid)#

test# configure terminal

test (config)# essid abcjk

test (config-essid)# dataplane bridged

test (config-essid)# ap-vlan-tag 11

test (config-essid)# ap-vlan-priority

test (config-essid)# end

For details of the commands used here, see the Command Reference Guide.