<div dir="ltr">Just a shot in the dark without seeing your configuration or anything, but when I had that problem (admittedly it was DHCPv6) Kea was allowing me to set impossible lease length values (max lease length or so greater than valid lease length). There is a rather long thread about it in the list here - was in November 2016. If you have different values set for your lease lengths - try setting them all the same and see if that helps.</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 7, 2016 at 10:04 AM, Ralf Hildebrandt <span dir="ltr"><<a href="mailto:Ralf.Hildebrandt@charite.de" target="_blank">Ralf.Hildebrandt@charite.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We're trying to replace a working installation of isc-dhcp-server<br>
4.3.3 with KEA 1.1.0 on the same box.<br>
<br>
* isc-dhcp hands out IP addresses AND the client accepts them - all is<br>
well<br>
<br>
* KEA on the other hand does hand out IP addresses:<br>
<br>
2016-12-07 15:59:02.562 INFO [kea-dhcp4.leases/35075] DHCP4_LEASE_ADVERT [hwtype=1 40:6c:8f:52:7d:60], cid=[01:40:6c:8f:52:7d:60], tid=0x1194bc8e: lease 10.31.192.5 will be advertised<br>
2016-12-07 15:59:18.596 INFO [kea-dhcp4.leases/35075] DHCP4_LEASE_ADVERT [hwtype=1 40:6c:8f:52:7d:60], cid=[01:40:6c:8f:52:7d:60], tid=0x1194bc8f: lease 10.31.192.6 will be advertised<br>
2016-12-07 15:59:34.627 INFO [kea-dhcp4.leases/35075] DHCP4_LEASE_ADVERT [hwtype=1 40:6c:8f:52:7d:60], cid=[01:40:6c:8f:52:7d:60], tid=0x1194bc90: lease 10.31.192.7 will be advertised<br>
2016-12-07 15:59:50.659 INFO [kea-dhcp4.leases/35075] DHCP4_LEASE_ADVERT [hwtype=1 40:6c:8f:52:7d:60], cid=[01:40:6c:8f:52:7d:60], tid=0x1194bc91: lease 10.31.192.8 will be advertised<br>
<br>
and these DHCPOFFERS arrive at the client. But then the client<br>
doesn't seem to accept them at all. It just keeps asking over and over<br>
again.<br>
<br>
On the same box, we basically shut down KEA, start up ISC-DHCPD and<br>
vice versa. We're currently using wireshark to record the traffic, but<br>
in the meantime: anbody got an idea what might be wrong?<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Ralf Hildebrandt Charite Universitätsmedizin Berlin<br>
<a href="mailto:ralf.hildebrandt@charite.de">ralf.hildebrandt@charite.de</a> Campus Benjamin Franklin<br>
<a href="http://www.charite.de" rel="noreferrer" target="_blank">http://www.charite.de</a> Hindenburgdamm 30, 12203 Berlin<br>
Geschäftsbereich IT, Abt. Netzwerk fon: <a href="tel:%2B49-30-450.570.155" value="+4930450570155">+49-30-450.570.155</a><br>
______________________________<wbr>_________________<br>
Kea-users mailing list<br>
<a href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/<wbr>listinfo/kea-users</a><br>
</font></span></blockquote></div><br></div>