<html><head></head><body><div style="color:#000; background-color:#fff; font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1504718409303_19958">Hello Kea Users!</div><div id="yui_3_16_0_1_1504718409303_19959"><br></div><div id="yui_3_16_0_1_1504718409303_19822" dir="ltr"><span id="yui_3_16_0_1_1504718409303_20022">I'm using Kea 1.2.0 in an environment that uses only Option82 (for IPv4) and Option18 (for IPv6) in order to always provide the same addresses to the same client (in fact, the same VLAN ID that asks for IPs).</span></div><div dir="ltr" id="yui_3_16_0_1_1504718409303_20068"><span id="yui_3_16_0_1_1504718409303_20022"><br></span></div><div dir="ltr" id="yui_3_16_0_1_1504718409303_20067"><span id="yui_3_16_0_1_1504718409303_20022">Since I don't have the flex-id hook library, I'm implementing IPv4 with the usual "reservations" based on "circuit-id". But for IPv6 I've defined several "subnets" based on "interface-id" provided by DHCPv6 relay agent. Inside each subnet I've declared "pools" (with only one address) and "pd-pools" (with only one prefix).</span></div><div dir="ltr" id="yui_3_16_0_1_1504718409303_20273"><span id="yui_3_16_0_1_1504718409303_20022"><br></span></div><div dir="ltr" id="yui_3_16_0_1_1504718409303_20209"><span id="yui_3_16_0_1_1504718409303_20022">Considering this implementation, I've two questions:</span></div><div dir="ltr" id="yui_3_16_0_1_1504718409303_20200"><span id="yui_3_16_0_1_1504718409303_20022"><br></span></div><div dir="ltr" id="yui_3_16_0_1_1504718409303_20201"><span id="yui_3_16_0_1_1504718409303_20022">(1) Is there any "hard" limit on the number of "reservations" (for IPv4) or "subnets & pools & pd-pools" (for IPv6)? Today I'm running about 260 of each, but they tend to increase in the future. <br></span></div><div dir="ltr" id="yui_3_16_0_1_1504718409303_20274"><span id="yui_3_16_0_1_1504718409303_20022">Note: I'm not using any DB backend, just the default TXT-based memfiles.<br></span></div><div id="yui_3_16_0_1_1504718409303_19817"><div id="yui_3_16_0_1_1504718409303_21573"><br></div><div id="yui_3_16_0_1_1504718409303_21574" dir="ltr">(2) I know that my question will be a bit strange, but... Is there a way to disable any kind of lease control in Kea? What I mean is that, in my environment, the DHCP and DHCPv6 servers just have to answer *always* the same IPv4 address and IPv6 address/prefix, based on Options 82 and 18, no matter of *who* (or what MAC/client-ID) is asking for it.</div><div dir="ltr" id="yui_3_16_0_1_1504718409303_22949">I ask this because If the client changes it's CPE device (changing MAC address), the DHCP won't provide any addresses until the lease expire. To workaround this I've configured low values to timers (about 10 min.), but this increases "the conversation" between clients and the servers. <br></div><div dir="ltr" id="yui_3_16_0_1_1504718409303_21696"><br></div><div dir="ltr" id="yui_3_16_0_1_1504718409303_21697">Thanks in advance!<br></div></div><div class="signature" id="yui_3_16_0_1_1504718409303_19931"><div id="yui_3_16_0_1_1504718409303_19974">--</div><div id="yui_3_16_0_1_1504718409303_20146">
Joelson Vendramin</div></div></div></body></html>