Hi Adrian,
The best way would be to breakup the pools around any addresses of
this type. You can specify multiple pools as noted here:
https://kea.readthedocs.io/en/kea-2.4.1/arm/dhcp4-srv.html#configuration-of-ipv4-address-pools
for example:
{
"subnet": "192.0.4.0/24",
"pools": [
{
"pool": "192.0.4.1 - 192.0.4.14",
"pool": "192.0.4.20 - 192.0.4.254"
}
]
}
Thank you,
Darren Ankney
On Sat, Apr 27, 2024 at 4:52 PM Adrian L Lange <[email protected]> wrote:
>
> Hi,
>
> I have a IPv4 pool used for a lot of services, and I usually reserve
> addresses either dynamically or manually.
> However, I now need to make sure an address in this pool won't get allocated
> by accident, and I can't reserve it when it doesn't have a client identifier
> (it's a floating virtual IP). It would be nice if reservations didn't require
> a client identifier or one could be set to "none". As this is not the case,
> and unless I've missed something in the documentation, how can I exclude an
> address from being allocated from a pool?
>
> Regards,
>
> Adrian
> --
> 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
> [email protected]
> 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
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
