Hi Francis, Thanks for the feedback. Your first point seems like the best practice implementation, although in practice just using a dummy MAC for a blocked-out address will work well enough.
We manage reservations through an external application talking to MySQL directly, and so don't store reservations in the config file itself. cheers, Klaus On Fri, Jun 15, 2018 at 12:38 AM, Francis Dupont <[email protected]> wrote: > I don't fully understand your problem but: > - the simplest is to not have addresses you want reserve in a pool > > - using host reservations work too but with a performance penalty > (cf out-of-pool text in the doc) and with a hairy but handle case > if you change dynamically the config (cf conflict text in the doc). > > Note you do not need to use an existing MAC in a host reservation, > the only constraint is to use a different MAC (or identifier in general) > between host reservations. > > Regards > > Francis Dupont <[email protected]> >
_______________________________________________ Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
