Hello,
On 12/5/25 07:01, Oliver wrote:
kea-shell --auth-user ... lease4-del ...
That above, of course, not a valid kea-shell command. It is *part*
of a command. The parts you omitted are likely necessary for us to
understand what is going on. By all means, substitute placeholders for
things like passwords and names and such, but please provide complete
information. We cannot diagnose a partial command. We need to know all
the kea-shell options you used, and the API content you fed into it.
A complete invocation of kea-shell, with HTTP authentication, is
generally going to look something like this (all one line):
echo ' "ip-address": "192.0.2.202" ' | kea-shell --service dhcp4
--auth-user bscott --auth-pass drowssap
I also noticed that the Control Agent rejects attempts to use absolute
> paths (e.g., /run/kea/kea4-ctrl-socket) with the error:> “invalid
path specified, supported path is /etc/kea”
so I cannot use explicit absolute socket paths.
Well, you can use absolute paths, but they are restricted to the
directory acceptable for the type of file in question. These and other
restrictions were introduced in Kea 2.6.3, 2.7.8, and 3.0.0, in an
effort to harden Kea against abuse. The acceptable directories are set
at build time, but can be overridden with environment variables. See
the release notes for more information.
For example, see the following page, starting at item #32:
https://gitlab.isc.org/isc-projects/kea/-/wikis/Release-Notes/release-notes-3.0.0
Hope this helps,
-- Ben
--
Any opinions expressed in this message are those of the author alone.
All information is provided without warranty of any kind.
--
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.
[email protected]
