[kea-dev] Transitioning Openwrt to Kea

[Victoria Risk]

> On Aug 3, 2024, at 12:33 PM, Philip Prindeville <philipp_subx at redfish-solutions.com> wrote:
> 
> Also, please allow pprindeville to fork Kea.

Philip,

You should be able to create a project and fork Kea now in our Gitlab. Please disable creation of issues in your new project though, because that has become a massive target for spammers.

Regards,

Vicky

> 
> 
>> On Aug 3, 2024, at 12:04 AM, Philip Prindeville <philipp_subx at redfish-solutions.com> wrote:
>> 
>> Thanks for those answers.
>> 
>> The “ip-reservations-unique” helped a lot.
>> 
>> I’ve noticed that certain devices (like IoT smart switches) need to have their renew-timer explicitly given (even if it’s not one of the parameters in their request) or they’ll keep renewing their lease every minute or something insane like that.
>> 
>> I’ve had to use something like:
>> 
>> host fire-purple {
>> hardware ethernet xx:xx:xx:xx:xx;
>> fixed-address 192.168.6.29;
>> option host-name "fire-purple";
>> if exists dhcp-parameter-request-list {
>> option dhcp-parameter-request-list = concat(option dhcp-parameter-request-list, 0c);
>> }
>> }
>> 
>> what is the equivalent to always send the renew-timer?  I tried:
>> 
>> {
>> “hostname”: “upstairs-bedroom-thermostat”,
>> “hw-address”: “xx:xx:xx:xx:xx”,
>> “ip-address”: “192.168.6.218”,
>> “option-data”: [
>>   {
>>     “name”: “host-name”,
>>     “data”: “upstairs-bedroom-thermostat”,
>>     “always-send”: true
>>   },
>>   {
>>     “name”: “renew-timer”,
>>     “data”: 1800,
>>     “always-send”: true,
>>   }
>> ]
>> }
>> 
>> but that doesn’t parse.
>> 
>> And is there an option to deny unknown clients or only to ignore them via the UNKNOWN membership and DROP client-class?  I don’t want them to keep on try.  I want them to report to their user that they’re being explicitly denied.
>> 
>> I’ve figured out that having a “pool” enables booting unknown clients, that’s straightforward enough.
>> 
>> Thanks,
>> 
>> -Philip
>> 
>> 
>> 
>>> On Aug 1, 2024, at 3:22 AM, Peter Davies <peterd at isc.org> wrote:
>>> 
>>> Hi Philip,
>>>  It is excellent to hear you are trying to help users migrate to Kea.
>>> 
>>> You should be able to add the "renew-timer" parameter globally and within a 
>>> subnet definition. The following is an example of this:
>>> 
>>> "subnet4": [{
>>>    "id": 1,
>>>    "subnet": "10.0.1.0/24",
>>>    "renew-timer": 1000,
>>>    "pools": [ { "pool": "10.0.1.1-10.0.1.200" } ] },{
>>>    "id": 2,
>>>    "subnet": "10.0.2.0/24",
>>>    "renew-timer": 2000,
>>>    "pools": [ { "pool": "10.0.2.1-10.0.2.200" } ]      
>>> }],
>>> 
>>> There is no equivalent to ISC DHCPD's  "always-broadcast" keyword. Localnet dhcp 
>>> traffic processing can be enabled for an interface by setting the "dhcp-socket-type" 
>>> to  "raw". For example:
>>> 
>>> "interfaces-config": { "interfaces": [ "eth0" ], "dhcp-socket-type": "raw" },
>>> 
>>> The "authoritative" setting can be specified in global, shared-network, and subnet 
>>> configuration scopes and is automatically inherited from the parent scope, if 
>>> not specified.
>>> 
>>> To allow multiple reservations for the same address, you will need to set the 
>>> global parameter "ip-reservations-unique" to false; the default is true.
>>> 
>>>       "ip-reservations-unique": false,
>>> 
>>> Let us hear how you get on.
>>> 
>>> Kind Regards Peter
>>> -- 
>>> Peter Davies
>>> Support Engineer 
>>> Internet Systems Corporation
>>> 
>>> -- 
>>> kea-dev mailing list
>>> kea-dev at lists.isc.org
>>> https://lists.isc.org/mailman/listinfo/kea-dev
>> 
>> -- 
>> kea-dev mailing list
>> kea-dev at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/kea-dev
>