Hi Bret, The client-identifier is a DHCP option so you could use the flex-option hook to remove the option in certain situations. You can match on membership in a class, for example, if you can classify these clients in some way. Then use the remove mechanism of flex option to remove the dhcp-client-id (option 61) from the response. This KB article has an example of performing a similar action: https://kb.isc.org/docs/redefining-standard-options
Thank you, Darren Ankney On Wed, Sep 25, 2024 at 2:17 PM Giddings, Bret via Kea-users <kea-users@lists.isc.org> wrote: > > Hi, > > > > I’m migrating a site with about 11000 leases to kea and have found a small > subnet (~200 devices) that don’t work if echo-client-id is true. Is there a > more granular way to control this setting as I’d prefer to stick with current > RFC defaults which then means I need a second kea instance just for this > small subnet of legacy devices. I could easily assign this subnet to a > different client class, but I can’t see any way of controlling the echoing of > client id at this level. > > > > Currently using ISC supplied packages > > > > # kea-dhcp4 -V > > 2.4.1 > > tarball > > linked with: > > log4cplus 2.0.8 > > OpenSSL 3.0.14 4 Jun 2024 > > database: > > MySQL backend 19.0, library 3.3.8 > > PostgreSQL backend 18.0, library 150008 > > Memfile backend 3.0 > > > > Regards, > > > > Bret > > -- > 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
