Hi Darren, Many thanks – that certainly sounds like it should work.
Regards, Bret From: Darren Ankney <darren.ank...@gmail.com> Date: Thursday, 26 September 2024 at 11:08 To: Kea user's list <kea-users@lists.isc.org> Cc: Giddings, Bret <b...@essex.ac.uk> Subject: Re: [Kea-users] Per-host or client-class echo-client-id CAUTION: This email originated from outside our organisation. Do not click links or open attachments unless you recognise the sender and know the content is safe. If you are not sure it is safe, please contact the IT Helpdesk. 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://linkprotect.cudasvc.com/url?a=https%3a%2f%2fkb.isc.org%2fdocs%2fredefining-standard-options&c=E,1,UH_Zg7E85WMZSeMxE0HroaDx0fTWuyisuMCinvQq_AEdxHQYOMNKSnxRqe9C8izaQvbky0ivE2WJ-DjVGP4r2EfEhfUxAeK08o8ExFBf5pz9IQ,,&typo=1 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://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.isc.org%2fcontact%2f&c=E,1,iqzdWUHe1J1Ior2h0Xf3PMGTIgowANWTKpbfVXJVK9V8ZEsgKrLRomJSL6-x9lKtV98IQRvS5rBsBh_S6qN236Cp1lJrUxZdRIMx_7oZkIMB2lJ0uA,,&typo=1 > for more information. > > To unsubscribe visit > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.isc.org%2fmailman%2flistinfo%2fkea-users&c=E,1,Ta1lTeeoA6FSV1JqtfgdcWtZTQ_53yqGYc19bimDq7gc-208KcZqxez99q8X3XeUI4tkp1vhQCZnh3xxv6PYAxOSxMjt-r0ifEmLDjSALaywJBc,&typo=1. > > Kea-users mailing list > Kea-users@lists.isc.org > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.isc.org%2fmailman%2flistinfo%2fkea-users&c=E,1,8-t4NmWKM-zJhTebuc0FW6JxjvPrKAjaErtfQmdnrbC8VPCIgc1LMnOl-EJtULoVYfsilmwn__SDufcAKG8LDx58JcciPpfO-Mb3oLWA8jaknw,,&typo=1
-- 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
