Dear Francis, thanks for confirming.
Indeed,
https://kea.readthedocs.io/en/latest/arm/dhcp4-srv.html?highlight=8.3#global-reservations-in-dhcpv4
clearly says:
"global reservations that assign addresses bypass the whole topology
determination provided by the DHCP logic implemented in Kea. It is
Veronique Lefebure writes:
> I would like to understand why KEA allocates an IP which should not be alloc
> ated.
>
>
> I have, on purpose (for testing KEA behaviour), declared the following globa
> l host reservation:
=> the answer is here: you use a global host reservation with a reserved
ad
Hi,
I would like to understand why KEA allocates an IP which should not be
allocated.
I have, on purpose (for testing KEA behaviour), declared the following global
host reservation:
{
"boot-file-name": "",
"client-classes": [ ],
"hostname": "cs-test-1a",
"hw-address": "xx:xx:xx:
