<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font face="Liberation Sans">Nicolas,<br>
<br>
<font face="Liberation Sans">I observed <font face="Liberation
Sans">similar</font> <font face="Liberation Sans">behavior.
For reasons I don<font face="Liberation Sans">'t want to go
into<font face="Liberation Sans"> her<font face="Liberation
Sans">e, <font face="Liberation Sans">we were doing a<font
face="Liberation Sans">n instant t<font
face="Liberation Sans">ime synchro<font
face="Liberation Sans">nization. </font></font></font></font></font></font></font></font></font><br>
<font face="Liberation Sans">This caused the dhcp clie<font
face="Liberation Sans">nt to s</font></font>end a DISCOVER
rather than a REQUEST, but included t<font face="Liberation Sans">he
obtained IP address<font face="Liberation Sans">. <br>
<font face="Liberation Sans">The server pinged the address
before <font face="Liberation Sans">OFFERing i<font
face="Liberation Sans">t, but got a reply from the <font
face="Liberation Sans">client, that haven<font
face="Liberation Sans">'t released it yet<font
face="Liberation Sans">, and <br>
<font face="Liberation Sans">so it was handing out
a new IP address. To my <font face="Liberation
Sans">knowledge</font>, <font
face="Liberation Sans">both the behavior <font
face="Liberation Sans">of the clie<font
face="Liberation Sans">nt and the serve
are correct<font face="Liberation Sans">.<br>
<font face="Liberation Sans">Do to the
time sync<font face="Liberation Sans">,
the state of the dhcp client jumped
trough the </font>renewal phase<font
face="Liberation Sans">.<font
face="Liberation Sans"> I didn<font
face="Liberation Sans">'t <font
face="Liberation Sans">find
anything specif<font
face="Liberation Sans">ic <br>
<font face="Liberation Sans">in
the sta<font
face="Liberation Sans">ndard
around this, so I <font
face="Liberation Sans">guess
<font face="Liberation
Sans">it<font
face="Liberation
Sans">'s
implementation
specifi<font
face="Liberation
Sans">c.<br>
<br>
<font
face="Liberation
Sans">--<font
face="Liberation
Sans"><br>
<font
face="Liberation
Sans"> Alpar </font></font></font>
</font></font></font></font></font></font><br>
</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font><br>
</font>
<div class="moz-cite-prefix">On 11/27/2012 08:07 PM, Nicolas C.
wrote:<br>
</div>
<blockquote cite="mid:50B5016C.6020102@nryc.fr" type="cite">Hello,
<br>
<br>
We have several cases of linux or windows clients loosing their
IPv4 address.
<br>
<br>
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).
<br>
<br>
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.
<br>
<br>
Is anyone experienced this behavior?
<br>
<br>
Regards,
<br>
<br>
Nicolas
<br>
_______________________________________________
<br>
dhcp-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a>
<br>
</blockquote>
<br>
</body>
</html>