Ok. I'm up and running on kea-dhcp4, but it wasn't painless. My
reservations by hw-address all worked, but that's all.
1) it seems to have paid no attention to the leases I tried to import. It
started over assigning the first address from the pool. If I had
remembered to shorten the timeout/re
Hi Jason,
That actually isn't intended. It will (probably) be fixed in 2.7.7:
https://gitlab.isc.org/isc-projects/kea/-/issues/3702
Thank you,
Darren Ankney
On Thu, Feb 13, 2025 at 4:21 PM Jason Creviston
wrote:
> Thanks for the reply Darren! You got my brain working again, as I had
> basical
Thanks for the reply Darren! You got my brain working again, as I had basically
given up on this.
As it turns out, enabling "store-extended-info" clashes with the functionality
of the limits hook, since both of them write to the user-context object via a
property named "ISC". We had this enable
On Thursday, February 13, 2025 7:20:16 PM CET Scott LaCroix via Kea-users
wrote:
> Hello all,
>
> We're trying to create a custom configuration file for the kea-dhcp4-server
> in our deployment. Currently what I've tried is a simple systemd dropin:
>
> $ cat /etc/systemd/system/kea-dhcp4-server.
Hi Jim,
It seems that the ascii content of the option:
00:00:00:09:59:0a:57:00:00:00:00:52:51:01:39:4e:4c:43:4f:54:65:73:74:2d:45:37:2d:4c:41:42:3a:31:2f:32:2f:31:2f:46:53:41:4e:3a:43:58:4e:4b:30:30:32:39:45:33:41:36:2f:4f:4e:54:4c:6f:67:69:63:61:6c:49:44:3a:38:31:32:2f:02:14:2f:4f:4e:54:50:6f:72
Hi Geoff,
You might need to specify your IP address on which to listen in your
interfaces-config. You can check with the command: `ss -ulnp`. In
the output, look what address is listed with 547. It might be your
LLA for the interface. If it is that instead of your GLA for the
interface, then y
Hello all,
We're trying to create a custom configuration file for the kea-dhcp4-server in
our deployment. Currently what I've tried is a simple systemd dropin:
$ cat /etc/systemd/system/kea-dhcp4-server.service.d/override.conf
[Service]
ExecStart=
ExecStart=/usr/sbin/kea-dhcp4 -c /etc/kea/kea-dh
I noticed on one host, you gave 0.0.0.0 as its IP, but this is not a routable
address. Can you please switch to a different routable address and make sure
you have ping connectivity between them?
Best Regards,
Yu
From: Kea-users on behalf of Zenz, Thomas via
Kea-users
Date: Thursday, Febr
Hi,
While writing this eMail I was collecting all data and checking the Ports with
curl:
>curl -X POST -H "Content-Type: application/json" -d '{ "command":
>"list-commands", "service": [ "dhcp4" ] }' http://***:***@10.89.100.39:8001/
I recognized, that the Control Connection was working, but n