Motorola RFS Series Reference Manual page 477

2. Uncheck the
automatically adopting new APs when they are connected to the switch.
3. Configure the client bridge back haul WLAN, base bridge and client bridge radios on the switch using the
Command Line Interface (CLI) commands listed below.
Client Bridge Back Haul WLAN Configuration:
RFS7000(config-wireless)#wlan 1 enable
RFS7000(config-wireless)#wlan 1 ssid meshWlan
RFS7000(config-wireless)#wlan 1 independent
RFS7000(config-wireless)#wlan 1 client-bridge-backhaul enable
Base Bridge Radio Configuration: (AP5131 that is wired to the switch)
RFS7000(config-wireless)#radio add 1 "base bridge radio mac" 11bg aap51x1
RFS7000(config-wireless)#radio add 2 "base bridge radio mac" 11a aap51x1
RFS7000(config-wireless)#radio 1 base-bridge enable
RFS7000(config-wireless)#radio 1 bss 1 1
(map the mesh WLAN if manual mapping is enabled, not needed otherwise)
Client Bridge Radios Configuration: (AP51x1's that are wirelessly
connected)
RFS7000(config-wireless)#radio add 3 "client bridge radio mac" 11bg
aap51x1
RFS7000(config-wireless)#radio add 4 "client bridge radio mac" 11a aap51x1
RFS7000(config-wireless)#radio 3 client-bridge enable
RFS7000(config-wireless)#radio 3 client-bridge ssid meshWlan
RFS7000(config-wireless)#radio 3 bss 1 1
(map the mesh WLAN if manual mapping is enabled, not needed otherwise)
4. Configure Adaptive AP support on the AP-5131 or AP-7131 by adopting the AP's base bridge as well as
client bridge. The client-bridge radios must be directly wired to the switch during this configuration step.
5. Once all AP5131 APs are adopted, wait for 3 minutes. After 3 minutes disconnect the client-bridge
AP5131s from the network. The client bridge AP5131s will continue to be adopted.
B.1.13 AAP Radius Proxy Support
When an Adaptive AP is adopted to a central switch over a WAN Link, the switch configures the Adaptive
AP for a WLAN with Radius authentication from a Radius server residing at the central site. When the
Adaptive AP gets a Radius MU associated, it sends the Radius packets on the wired side with its own IP
Address as the source IPof the request and the Destination IP Address of the Radius Server. In a local network
implementation, the Adaptive APs, switch and Radius Servers are all on the same LAN and the routing works
fine. However, when the Adaptive AP is adopted over a WAN link, the Radius Server IP Address will be an
internal address which is non-routable I over the Internet.
To access the Radius server's non-routable IP address over the WAN, you have the option to configure
Adaptive AP Radius Proxying for the WLAN. When this flag is enabled, the Adaptive AP is reconfigured to
send all radius traffic to the switch and the switch does the proxying to the real Radius server to handle
authentication. The switch automates the process of handling Radius proxy configuration and client
configurations. The switch supports only one real radius server configuration without the presence of realm
information. To support multiple radius servers, a realm has to be associated with the real Radius server.
When AAP radius proxying is enabled without specifying a realm, the switch can no longer process requests
on the on-board radius server. You cannot authenticate using the on-board Radius server any longer because
Adopt Unconfigured Radios Automatically option to prevent the switch from
B-7