Symptoms Run the following DHCP debug processes:
diagnose debug reset
diagnose debug application dhcpc -1
diagnose debug console timestamp enable
diagnose debug enable
To stop the debugging:
diagnose debug reset
diagnose debug disable
DHCP debug will display the following output:
2026-09-25 12:43:57 timer 0x556224bbf0(send_discover -> send_discover) will expire in 9 secs
2026-09-25 12:43:58 timer 0x556224bbf0(send_discover -> send_discover) will expire in 8 secs
2026-09-25 12:43:59 timer 0x556224bbf0(send_discover -> send_discover) will expire in 7 secs
2026-09-25 12:44:00 timer 0x556224bbf0(send_discover -> send_discover) will expire in 6 secs
PCAPs will show the following output:
5 44.368021 0.0.0.0 255.255.255.255 DHCP 590 DHCP Discover - Transaction ID 0x35b0f614
7 50.458023 0.0.0.0 255.255.255.255 DHCP 590 DHCP Discover - Transaction ID 0x35b0f614
13 65.678047 0.0.0.0 255.255.255.255 DHCP 590 DHCP Discover - Transaction ID 0x35b0f614
This failure is due to a change in behavior in 8.0.1 which transitions DHCP daemon from a raw L2 socket which read frames straight from the interface before the IP stack->L3 socket where incoming DHCPOFFER/ACK packets are received via UDP and subsequently hit 'config firewall local-in-policy'. If the user configuration has a deny-all entry, it will drop the DHCP offer and will not complete the DORA process.
This change is documented in the 8.0.1 release notes under "changes in default behavior" bug id 1301413.
The following policy is required to allow DHCP traffic before the DENY policy:
config firewall local-in-policy
edit 2
set intf "x"
set srcaddr "all"
set dstaddr "all"
set action accept
set service "DHCP"
set schedule "always"
end
Here, "x" is the interface name.
Related articles:
Technical Tip: Diagnosing DHCP on a FortiGate 8.0.1 FortiOS Release Notes |