<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 14/02/2019 11:45, Tomek Mrugalski
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:0d0d36ba-1f3c-4290-be1c-024fac9f87bb@isc.org">
<pre class="moz-quote-pre" wrap="">On 14.02.2019 09:14, ѽ҉ᶬḳ℠ wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">being in the process of migrating from dnsmasq I have been looking for
an option in Kea to limit a particular subnet to static leases only,
something similar to dnsmasq's > dhcp-range=static <, but after having
perused the Kea admin documentation could not trace such?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">So you want a subnet without any dynamic allocation, just serve the
clients that have reservations?
Simply don't define dynamic pools. That should do the trick.
Tomek
</pre>
</blockquote>
<br>
I tried this various ways but none seems to be working.<br>
<br>
kea-dhcp4-server is running and listening either globally or on
specified faces. According to the kea log there are no dhcp requests
from clients on the subnet specified in the kea conf<br>
<br>
<i>"subnet4": [</i><i><br>
</i><i> {</i><i><br>
</i><i> "subnet": "172.24.0.0/16", </i><i><br>
</i><i> "reservations": [</i><i><br>
</i><i> {</i><i><br>
</i><i> "hw-address": "00:16:3e:88:e8:4e",</i><i><br>
</i><i> "ip-address": "172.24.41.10"</i><i><br>
</i><i> }</i><i><br>
</i><i> ]</i><i><br>
</i><i> },</i><br>
<br>
However, the log is showing dhcp requests from clients in other <u>s</u><u>ubnets
that are not in the kea conf</u> and that logically cannot be
satisfied by kea:<br>
<br>
<i>ERROR [kea-dhcp4.bad-packets/12145] DHCP4_PACKET_NAK_0001
[hwtype=1 00:16:3e:fc:25:3f],
cid=[ff:e0:55:d8:0c:00:02:00:00:ab:11:56:45:59:1d:16:60:db:75],
tid=0xac615c91: failed to select a subnet for incoming packet, src
172.25.120.76, type DHCPREQUEST</i><br>
<br>
As soon as specifying the other subnets in the kea conf however no
dhcp requests are logged either for those subnets.<br>
<br>
With dnsmasq running instead of kea, dnsmasq is of course stopped
when running kea, there is no such issue and the clients are being
assigned their static addresses as specified in the dnsmsaq conf.<br>
<br>
So either I am missing something here or this being rather some sort
of bug in kea. Either way I did not imagine that a transition from
dnsmasq to kea would bear such complications and I am rather
inclined to throw in the towel and stay with dnsmasq instead.<br>
<br>
</body>
</html>