@LaUs3r said in How to change Kea DHCP log level:
keactrl.conf:
Afaik, the process (program) keactrl isn't used by pfSense.
The GUI starts "/usr/local/sbin/kea-dhcp4" (with config file /usr/local/etc/kea/kea-dhcp4.conf)
and
/usr/local/sbin/kea-dhcp6 with config file /usr/local/etc/kea/kea-dhcp6.conf
if you have IPv6 LAN(s) directly.
Your 2) is .... well ... will work only ones.
You've said it yourself :
@LaUs3r said in How to change Kea DHCP log level:
The change to the kea-dhcp.conf is not persistent, i.e. does not survive a reboot
Consider this over simplified description of pfSense - the GUI.
It's a nice looking super config file creator.
So the very next time a process, like the DHCPv4 server kea-dhcp4, gets restarted, first, the config file is re created using GUI stored settings, and then the process is started.
At that moment, your own edits of a file like /usr/local/etc/kea/kea-dhcp4.conf are gone.
So, it won't survive a reboot, and it won't survive the very next process restart, for example when you save the DHCPv4 server settings page, for example.
If you want to change the log "severity", have a look at /etc/inc/services.inc
I presume you use 24.11 - pfSense Plus.
Look here.
Change you /etc/inc/services.inc, locate the same line, change WARN for INFO, save, restart DHCPv4 (kea) and voila.
Btw :
I've myself this :
38ed983a-2c2c-464e-8aa6-f6977d4fb192-image.png
so the "severity" setting gets its info from the kea/loglevel pfSense config file - but I never bothered to change also the GUI pages to select from an INFO, WARN ERROR etc list.
These edit won't survive a pfSense version upgrade. But that's not an issue as the next update will include this option in the GUI for sure.
@LaUs3r said in How to change Kea DHCP log level:
I was relying on the logs of the DHCP server to get the MAC first
Lol, I always do exactly that.
And maybe the kea DHCPv4 logs are less detailed.
But : you'll would find the lease (MAC) here :
d09524f2-d8ac-44a6-9946-72b4239c4efb-image.png
and this works out of the box ^^