Operational Defect Database
BugZero found this defect 1357 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
WatchGuard Technologies | kA10H000000bpL1SAI
DHCP process might not respond to requests
Last update date:
9/2/2020
Affected products:
Firebox M200
Firebox M300
Firebox M270
Firebox M370
Firebox M470
Firebox M570
Firebox M670
Firebox M290
Firebox M390
Firebox M400
Firebox M500
Firebox M440
Affected releases:
All
Fireware
12.x
12.5.x
12.6.x
Fixed releases:
v12.5.5 U1 and Fireware v12.6.2 U2
Description:
Issue
The DHCP process on the Firebox might stop responding to DHCP requests where the Firebox acts as the DHCP server for the network. When this issue occurs, in the Status Report process list, the DHCP process takes up more CPU than usual (sometimes up to 50% of the CPU). 1930 R 48.40 7232 3880 1460 Mon Aug 31 07:50:09 2020 43:59.36 /usr/bin/dhcpd -f -d -cf /tmp/dhcpd.conf -lf /tmp/csync/dhcp/dhcpd.leases vlan1 -ls 15785 Client devices might also adopt random APIPA IP addresses that start with 169.254.x.x.
Workaround/Solution
Remove all DHCP reservations from all DHCP scopes.Reboot the Firebox
