>> I encourage you to open an issue at https://gitlab.isc.org/isc-projects/kea to request a feature to enable your use case. I seem to remember we once discussed some sort of ‘automatically create a reservation’ feature but I didn’t really understand the use case for it. It really helps when users describe how they expect the feature to work. For example, how do you know what to put in the HR to identify the client if you don’t have any identifier for the client?? >> >> I don’t know what to do about affinity after a release - I think that might be a protocol issue… >> >> Vicky > > Thanks Vicky, > > I just wrote another reply describing what I have found out while investigating this. In short, this seems to only affect some clients and I'm probably able to configure them to change their behaviour into something that would work for me. I will look a bit more into it and get back to you if I find that such a feature still seems legit. It's certain that KEA does nothing wrong in this case, so this feature would ask it to refrain from following standards by ignoring the DHCP release package. > > All the best, > Johannes
Hi again, Vicky, With the excellent tip I got from Peter Davies about using the built-in DROP client-class, which adds the functionality I'm after, I see no reason to open an issue about this. My problem is solved and I'm even more happy with KEA :-) Greetings, Johannes
_______________________________________________ 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
