Description |
This article describes how to resolve a scenario where the wireless clients are not able to authenticate to the wireless SSID while using the RADIUS-based security. |
Scope | All FortiGate. |
Solution |
On the FortiGate, the EAPOL client start message is seen after associating to the SSID, but FortiGate is not forwarding the frame to the radius on behalf of the client which is trying to authenticate.
The fnbamd debug output with the MAC showed the following messages:
2024-03-08 13:32:41 32057.857 46 xx:xx:xx:xx:xx:xx cwAcStaRbtAdd: I2C_STA_ADD insert sta xx:xx:xx:xx:xx:xx 10.10.9.50/1/0/4
In addition, the PCAP was showing the only start traffic and no request packets. Therefore, the EAPOL exchange didn't complete.
2024-03-19 12:26:09 74864.663 46 xx:xx:xx:xx:xx:xx<cc> STA_CFG_REQ(77) sta xx:xx:xx:xx:xx:xxdel ==> ws (0-10.10.9.50:5246) rId 1 wId 0
The PMF option was set to optional on the SSID:
config wireless-controller vap edit <vap_name> set pmf {disable | enable | optional} set pmf-assoc-comeback-timeout <integer> set pmf-sa-query-retry-timeout <integer> set okc {disable | enable} next end
PMF is considered to be enabled when set to optional. See this documentation page for more information. |
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.