Because Fortinet won't post bug lists...
Known bug in 5.2, seems that it handed out a DHCP address to a new device when the old device hadn't timed out and had only been powered off for a day. When it came back on the network the device said 'ip conflict', asked for a new IP, the FGT said - 'ok here you go' but then went thru every IP left in the range. Had to dhcp lease-clear to resolve.
It's the second device I had this happen on.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
pkley wrote:Because Fortinet won't post bug lists...
Known bug in 5.2, seems that it handed out a DHCP address to a new device when the old device hadn't timed out and had only been powered off for a day. When it came back on the network the device said 'ip conflict', asked for a new IP, the FGT said - 'ok here you go' but then went thru every IP left in the range. Had to dhcp lease-clear to resolve.
It's the second device I had this happen on.
Try to see the parameter: conflicted-ip-timeout
Maybe isn't properly configured.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
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 2024 Fortinet, Inc. All Rights Reserved.