DHCP clients losing address / backdated lease date
alpar-istvan.torok at hp.com
Thu Nov 29 08:29:00 UTC 2012
I observed similar behavior. For reasons I don't want to go intohere, we
were doing an instant time synchronization.
This caused the dhcp client to send a DISCOVER rather than a REQUEST,
but included the obtained IP address.
The server pinged the address before OFFERing it, but got a reply from
the client, that haven't released it yet, and
so it was handing out a new IP address. To my knowledge, both the
behavior of the client and the serve are correct.
Do to the time sync, the state of the dhcp client jumped trough the
renewal phase.I didn't find anything specific
in the standard around this, so I guess it's implementation specific.
On 11/27/2012 08:07 PM, Nicolas C. wrote:
> We have several cases of linux or windows clients loosing their IPv4
> We noticed that sometimes, the date the client is supposed to have
> obtained the lease is way in the past (like in the year 1876).
> The version of DHCP is 4.2.2 (Debian Wheezy), two DHCP are in
> failover. We suspect some security features on the ethernet switches
> but they have been deactivated.
> Is anyone experienced this behavior?
> dhcp-users mailing list
> dhcp-users at lists.isc.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dhcp-users