Hi Cody,
Please have a look at the forensic logging hook for a way to log
circuit IDs with leases:
https://kea.readthedocs.io/en/kea-2.4.0/arm/hooks.html#libdhcp-legal-log-so-forensic-logging
Thank you,
Darren Ankney
On Fri, Oct 20, 2023 at 9:47 AM Cody Shultz via Kea-users
wrote:
>
> Hello,
Hi,
> Does the Kea Lease Migration support ISC DHCP Failover Lease Files?
The only difference between a non-failover lease file and failover
lease file in ISC DHCP, AFAIK, was that there were some extra entries
about peers and status. I don't think there was anything in the
actual leases
Hi Kraishak,
In the URL for the primary server set the URL including the IP you
want it to listen on for the primary. Same on the secondary using the
IP you want the secondary to listen on. It doesn't matter if you are
serving DHCP on the same IP or not.
Thank you,
Darren Ankney
On Thu, Oct
Hi Vladimir,
You can set it "ddns-qualifying-suffix": "", which resets it to empty
in the block in which you do that. You could also only specify inside
subnets where you need it specified and not specify at global level.
There would have to be some way to flag hostnames that you wanted to
Hi Ben,
I'm not sure what to make of those errors. It does appear that
changing database ownership is the correct course of action:
https://gitlab.isc.org/isc-projects/kea/-/issues/2773
I'd say perform some tests and make sure that leases are successfully
stored in the database (perhaps use the
