Troubleshooting Tip: FortiGate is not providing DHCP with error DHCP DECLINE
| Description | This article helps to troubleshoot the FortiGate DHCP when it is receiving an error DHCP DECLINE on debug. |
| Scope | FortiGate is the DHCP server, and the client is not getting a DHCP IP.
When running the debug 'diagnose debug application dhcpc -1', the error DHCP DECLINE is visible.
Sample 1:
2022-06-08 18:28:52 [note]DHCPDECLINE on 172.22.1.2 from 98:fa:9b:89:da:d6 via port4(ethernet)
Sample 2:
Receive packet:
Use the following debug commands to capture the relevant parameters:
FortiGate is the DHCP Server:
diagnose debug reset diagnose debug console timestamp enable
To stop the debug:
diagnose debug reset |
| Solution |
config firewall ippool
By default, the IPpool is configured to have the 'arp reply' enabled, which will cause the FortiGate itself to respond to the DHCP probe.
To be sure, it is possible to use the sniffer command to check the ARP:
diagnose sniff pac <port> "arp" 4
Remove the IPpool or change the DHCP IP to another range.
The MAC IP address of the PC is blocked from getting an IP address from the DHCP server:
After this rule is configured, the device associated with the specified MAC address will no longer be eligible to receive a DHCP lease from the FortiGate DHCP server. This approach helps ensure that only authorized devices are granted automatic IP address assignments, thereby enhancing overall network security.
|



