From philipp_subx at redfish-solutions.com Mon Sep 8 23:27:46 2025 From: philipp_subx at redfish-solutions.com (Philip Prindeville) Date: Mon, 8 Sep 2025 17:27:46 -0600 Subject: [kea-dev] boot-unknown-clients equivalent? In-Reply-To: <1010392082.2383438.1682851694258.JavaMail.zimbra@isc.org> References: <1010392082.2383438.1682851694258.JavaMail.zimbra@isc.org> Message-ID: Thanks. And what is the name to get a request explicitly NAK?d (rejected)? Are there any other special names? > On Apr 30, 2023, at 4:48?AM, Peter Davies wrote: > > Hi Philip, > > If you only employ host reservations, then the built-in "KNOW" class may be use to restrict clients. > > For example: > > "client-classes": [{ > "name": "DROP", > "test": "not member('KNOWN')"} ], > > ... > > I advise caution, as this will drop all packet that are not associated with a host reservation. > > /Peter > > > On 25/04/2023 03.46, Philip Prindeville wrote: >> Hi, >> >> I'm trying to port the isc-dhcp support in OpenWrt to migrate to Kea transparently. >> >> I've tried to use keama to show me what the synthesized configs should look like, but there's a lot that keama doesn't handle that seems to be in the scope of what Kea is capable of. >> >> For instance, "boot-unknown-clients false;" can be handled using the DROP class an not(member(KNOWN)) but I can't figure out the exact notation. >> >> Can someone point me at an example? I couldn't turn one up via google. >> >> BTW, the existing code to take UCI config blocks and synthesize dhcpd.conf lives here: >> >> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init >> >> Thanks, >> >> -Philip >> > -- > kea-dev mailing list > kea-dev at lists.isc.org > https://lists.isc.org/mailman/listinfo/kea-dev