Chapter 4 Management Mode
DHCP Option 43 allows the CAPWAP management request (from the AP in managed AP mode) to reach the AP controller in a different subnet, as shown in the following figure.
Figure 18 CAPWAP and DHCP Option 43
SUBNET 1 |
|
|
|
|
|
|
|
| SUBNET 2 | |
|
|
|
|
|
|
|
|
| DHCP | |
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| SERVER | |
|
|
|
|
|
|
|
|
| + OPTION 43 | |
|
|
| CAPWAP |
|
|
| ||||
|
| |||||||||
|
|
| TRAFFIC | |||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
AP
CONTROLLER (STATIC IP)
MANAGED
AP
(DYNAMIC
IP)
4.1.4 Notes on CAPWAP
This section lists some additional features of ZyXEL’s implementation of the CAPWAP protocol.
•When the AP controller uses its internal RADIUS server, managed APs also use the AP controller’s authentication server to authenticate wireless clients.
•Only one AP controller can exist in any single broadcast domain.
•If a managed AP’s link to the AP controller is broken, the managed AP continues to use the wireless settings with which it was last provided.
4.2The Management Mode Screen
Use this screen to configure the NWA as a CAPWAP controller AP or CAPWAP managed AP or to use it in its default standalone mode.
| 49 |
|
|