====== kea-dhcp4-server ====== Pakete: * Debian (ab 12): ''kea-dhcp4-server'' { "Dhcp4": { "interfaces-config": { "interfaces": [ "ens3" ] }, "control-socket": { "socket-type": "unix", "socket-name": "/run/kea/kea4-ctrl-socket" }, "host-reservation-identifiers": [ "hw-address" ], // wird schneller verarbeitet als der default, sinnvoll wenn man client id/hostname, duid usw. nicht nutzt "subnet4": [ { "subnet": "192.168.242.0/24", "id": 1, // Subnet identifier should be unique for each subnet // "reservation-mode": "out-of-pool", // oder "disabled" // beides wird schneller verarbeitet als der default "all" // "pools": [ { "pool": "192.168.242.128 - 192.168.242.191" } ], "option-data": [ { "name": "routers", "data": "192.168.242.1" }, { "name": "domain-name-servers", "data": "192.168.1.5" }, { "name": "domain-search", "data": "linuxhotel.de" } ], "reservations": [ { "hw-address": "52:54:00:00:01:02", "ip-address": "192.168.242.12" } ] } ], "loggers": [ { "name": "kea-dhcp4", "severity": "INFO", "output_options": [ { "output": "stdout", "pattern": "%-5p %m\n" } ] } ] } } kea-dhcp4 -t /etc/kea/kea-dhcp4.conf ++++ Debian 13| sudo -u _kea kea-dhcp4 -t /etc/kea/kea-dhcp4.conf ++++ systemctl restart kea-dhcp4-server.service bzw. systemctl kill --signal=HUP kea-dhcp4-server.service Prüfen, ob kea läuft: lsof -Pni :67 -> ''kea-dhcp4'' systemctl status kea-dhcp4-server.service journalctl -fu kea-dhcp4-server.service Reload für kea-dhcp4 aktivieren: systemctl edit kea-dhcp4-server.service [Service] ExecReload=kill -HUP $MAINPID systemctl cat kea-dhcp4-server.service ====== kea-ctrl-agent ====== Pakete: * Debian 12: ''kea-ctrl-agent curl jq'' Aktuelle dhcp4-Konfiguration ausgeben: curl -X POST -H "Content-Type: application/json" -d '{ "command": "config-get", "service": [ "dhcp4" ] }' http://127.0.0.1:8000/ | jq TODO für Debian 13: dpkg-reconfigure kea-ctrl-agent