Motorola WiNG 4.4, Reference Manual, Page: 543 / 598

B - 11
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)
1. Configure Adaptive AP support on the AP-5131 or AP-7131 by adopting the APs base bridge as well as client bridge.
The client-bridge radios must be wired directly wired to the switch during this configuration step.
2. 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 IP of 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 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 multiple RADIUS servers. 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 all authentications done by users
without a realm are forwarded to the external radius server, as configured for the WLAN with Adaptive AP Radius Proxy.
NOTE The Motorola Solutions RF Series Wireless Switches support Adaptive AP Radius
proxy without specifying realm information. If AAP Proxy Radius is enabled
without specifying realm information, the onboard Radius server can no longer be
used to authenticate users. If AAP Proxy Radius is enabled for a WLAN with
realm configured, then the onboard Radius server can perform as usual.
NOTE If AAP Proxy Radius is configured, the onboard Radius server has to be enabled.
By default the onboard Radius server is disabled. To enable the onboard Radius
server use the Web UI or issue the “service radius” command in the CLI.