Technical Tip: Static vs. Dynamic IP addressing in a FortiAP CAPWAP configuration
Description
Â
This article describes the pros and cons of statically assigning IP addresses and access controller (AC) addresses for FortiAPs vs. using dynamic addressing option (i.e. with DHCP Option 138).
Â
Scope
Â
FortiGate, FortiAP.
Â
Solution
Â
When managing FortiAPs with a FortiGate, the FortiAP must have its own IP address and must also know the IP address of its managing FortiGate so that it can establish an outgoing CAPWAP management connection. In terms of per-FortiAP IP addressing, administrators can configure this manually/statically or handle it with DHCP (Dynamic Host Configuration Protocol):
Â
Pros | Cons | |
|---|---|---|
Static IP addressing |
|
|
Dynamic IP addressing |
|
|
Â
The access controller (AC) IP address can also be configured separately from the FortiAP's local IP addressing, either statically or dynamically:
Â
Pros | Cons | |
|---|---|---|
Statically-set AC controller address |
|
|
Dynamically-learned AC controller address |
|
|
Â
Given the above, the following are some general recommendations for which option to use:
In environments with a small number of deployed FortiAPs, it is fine to use static addressing to ease administrative burden (no need to configure/depend on DHCP for wireless functionality). For guidance on configuration, refer to the following documentation: Static IP configuration.
It can also be appropriate for deployments where the FortiAP is unlikely to otherwise discover its access controller (i.e., when deployed behind another router or at a remote site such as an end-user's home). This ensures that the FortiAP always knows what the controller address is, as it may not be able to learn this from the local DHCP server.
For larger environments, consider using DHCP to serve IP and controller addressing to the FortiAPs. DHCP reservations allow for a defined mapping between a given FortiAP's MAC address and the assigned IP address, and the administrative burden is reduced since FortiAPs can be easily deployed or swapped out without requiring manual configuration.
This can also be appropriate for environments that already use FortiGates and FortiSwitches, as the FortiGate is often providing DHCP services to the network already and also has visibility/control into the VLAN/switchport configurations, so the administrative 'cost' of utilizing DHCP is substantially reduced.
It is possible to mix and match static/dynamic addressing for the FortiAP's own IP address and the access controller address. For example, a FortiAP could have a static access controller address but still receive IP addressing from a local DHCP server that is not under control of the FortiAP administrator (for example: Remote WLAN FortiAPs).
Regardless of the method, specifying the access controller to the FortiAP in some manner is useful for expediting controller discovery by the FortiAP, as this ensures that it connects faster following a reboot or first-time joining. For more information on how the FortiAP discovers its access controller, refer to the following document: Advanced WiFi controller discovery.
