Hi Jason, Something like this might work:
"client-classes": [ { "name": "short-lease", "test": "member('KNOWN')", "valid-lifetime": 300 } ], ... "subnet4": [ { "subnet": "10.1.2.0/24", "id": 1, "option-data": [ { "name": "routers", "data": "10.1.2.1" } ], "valid-lifetime": 300, "pools": [ { "pool": "10.1.2.100-10.1.2.200", "client-class": [ "short-lease" ] } ] } ], On Wed, Apr 3, 2024 at 10:56 AM Jason Keltz <j...@yorku.ca> wrote: > > Hi Darren, > > Yes - "lease-lifetime" was my error - I meant "valid-lifetime". > I understand that I cannot apply "valid-lifetime" to a pool (although I > feel like I should be able to). > I already define client-class as "KNOWN" in all my pools so that unknown > hosts can't get an IP, and I understand that I can't use a second > client-class of "short-lease" in each pool. > I looked in the Kea code where options are defined, and thought I would > be able to add: > > { > "name": "dhcp-lease-time", > "data": "300" > } > > ... to "option-data" section for each host, but this didn't work > either. I see that in the Kea docs, all-options.json skips from code 49 > to code 52, thereby skipping over code 51 which is lease time. > > I tried adding "code": 51, to the section to my option above, but it > didn't make any difference. > > I tried adding "valid-lifetime" to the "reservations" section to see if > that would work, but it would not. > > Therefore, I'm still not sure how to implement different lease times for > pools. > > Jason. > > On 4/3/24 06:35, Darren Ankney wrote: > > Hi Jason, > > > > > >> would it be valid syntax to also set lease-lifetime in the pool instead of > >> using the class? > >> > >> "pools": [ > >> { > >> "pool": "10.1.2.100-10.1.2.200", > >> "lease-lifetime": "300" > >> } > >> ] > > I cannot find evidence of a parameter called "lease-lifetime" but > > "valid-lifetime" cannot be set inside a pools [] block. > > > >> I already assign the pools to "client-class": "KNOWN" - can I specify > >> multiple classes? "client-class": "KNOWN", "short-lease"? > >> If I use a class to do this, is the "valid-lifetime": 300 inside the > >> subnet definition necesary? It is repeated in both the subnet and the > >> client-class short-lease. > > The "valid-lifetime" inside the subnet was a mistake. That was a > > relic of some earlier testing. You cannot specify multiple classes on > > a client-class line. I don't know if you can have both client-class > > and client-classes as I've never tried. "client-class" does not do > > the same thing that "client-classes" does. > > > > Thank you, > > Darren Ankney > > -- > ISC funds the development of this software with paid support subscriptions. > Contact us at https://www.isc.org/contact/ for more information. > > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. > > Kea-users mailing list > Kea-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/kea-users -- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users