Description |
This article describes why a new FortiExtender could not being shown under the 'Authorization' page after the discovery process, even with a correct FortiExtender configuration.
In this case, the FortiGate unit receives the discovery packets from the FortiExtender unit, but it is not able to reply those CAPWAP packets. As shown in the output below, the firewall (IP 192.168.100.1) is receiving CAPWAP traffic from the FortiExtender (IP 192.168.200.2), but there is no response:
As a result, the FortiExtender is not shown to be authorized: |
Scope |
FortiGate and FortiExtender. |
Solution |
The wireless-controller module needs to be enabled for the CAPWAP activation:
FW01 # config global
After enabling it, there is a correct CAPWAP flow and the FortiExtender unit is able to be authorized: FW01 # diag sniffer packet any 'port 5246' 4 0 a
The wireless-controller module is enabled by default in FortiOS. If there are no FortiAPs suitable to disable this function, if the 'disable' is done from the CLI, there is a warning message shown regarding the CAPWAP deactivation:
FW01 (global) # config system global
Note: Disabling the feature from the GUI will not show any alert when applied: |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.