Description When a ticket is created, provide a specific set of data
aimed at facilitating ticket resolution is requested. To troubleshoot
complex incidents the support teams need to fully understand the network
topology and role of the Fortinet unit...
Purpose The purpose of this document is to explain how to reject CAPWAP
discovery requests coming from an unknown AP. Scope By default, the
FortiGate will reject unknown Access Points to be discovered by the
Wireless Controller. However, an attacker ...
PurposeThis article explains how to connect to a FortiAP from the
Wireless Controller using telnet.ScopeThe FortiAP IP address is
reachable by the Wireless Controller.Expectations, RequirementsOnce the
FortiAP is Discovered by the Wireless Controller...
Purpose The purpose of this document is to help configuring Windows
server to send option 138 to FortiAPs. This will push the Wireless
Controller's IP address to the FortiAP. If you use DHCP to assign an IP
address to your FortiAP unit, you can also ...
Purpose From version 5.0, the FortiAP has the feature to sniff wireless
traffic using its radio. This feature is not present in version 4.0 MR3.
This article provides a workaround to this and explains how to sniff
traffic in the air using wireshark.S...
Hello, the CAPWAP process is properly started (CAPWAP discovery request
from the FAP to the FGT and response from the FGT to the FAP), but the
dtls session is not being started.This will require further
investigations on the FAP side and it will requ...
Hello, this might require a bit of troubleshooting.I would start with
the following:# execute wireless-controller restart-acdif it still does
not work: # diag sniffer packet any "port 5246" 6 0 ataken on the FGT
for about 2 min (and please capture th...