Description | This article describes an issue when a wireless user is getting a private IP instead of the correct settings and AP reboot. |
Scope | FortiGate. |
Solution |
A wireless end user connecting to FortiAP only gets APIPA 169.254.x.x IP. Collect the below on Sniffer on FortiGate to verify packet flow between the User and the DHCP server:
diagnose sniffer packet <interface> "port 67 or port 68" 6 0 l
Note: <interface> SSID where the wireless user is connected
If DHCP(DORA) packets are missing in the capture, collect the following logs in the FortiAP. Log in to the affected AP and run the following command:
fap-tech
Access Point capture may show only DHCP Discovery messages, and no DHCP Offer. On the FortiGate DHCP captures, it may show DHCP Discover & Offer packets: Line 35: [36489.106316] [CWD_DHCP] cpu2 vap-13(wlanxx): __ftnt_sta_dhcp_parse dhcp_op43_insert f4:d1:08:xx:xx:xx sn rId 1 wId 3 ssid abcWireless
To fix the issue, use the steps below:
config system npu
Note: It will disconnect all wireless-connected users.
Related article: Technical Tip: How to restart the wireless controller daemon |
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.