pfSense

Steven Cedrone wrote:

Changed from ISC to KEA DHCP and the service would not stay running.

After going through System Log it reported an error to do with NTP servers being assigned to DHCP Clients.

After removing NTP server information from DHCP server client listings to give them specific NTP Servers to use the service started running.

I attempted to copy the exact error from the log but due to the clients my PfSense Plus Firewall is serving it quickly out numbered the 2000 log entries before I could grab it to paste it here.

To me it's a bug that the NTP information whether supported or not by KEA should be either ignored when changing from ISC to KEA or there is a bug.

Changed at.pool.ntp.org to the IP address in system->advanced->networking - still not working, kea dhcp keeps using filekea-dhcp4.conf, which presumably generated first time kea was activated. Switching back to ISC and reactivate kea did not help.
ERROR [kea-dhcp4.dhcp4.0xbe6c7012000] DHCP4_INIT_FAIL failed to initialize Kea server: configuration error using file '/usr/local/etc/kea/kea-dhcp4.conf': option data does not match option definition (space: dhcp4, code: 42): Failed to convert string to address 'at.pool.ntp.org': Invalid argument (/usr/local/etc/kea/kea-dhcp4.conf:377:33)

Harald Holzner Thanks for adding this to my report. Appreciate it.

Testing this it appears that Kea cannot accept hostnames, but can accept IP addresses just fine.

Tested this with ISC DHCP and it accepted both IP addresses and hostnames without issue.

Confirming bug. Seems that FQDNs in the NTP server fields for the main configuration or for static reservations causes Kea to not start.

Brilliant pfSense DevTeam!

Just confirm the same bug.

I reproduce the same environment and receive the same bug/behavior.

This even MAKE IMPOSSIBLE TIME SYNC inside all infrastructure behind pfSenseif. (Or You need entering FQDN / IP of internal time server MANUALLY ON EACH DEVICE in infrastructure).

Please fix.