Actions
Bug #14991
closed
Kea does not allow FQDNs for NTP servers but input validation does not prevent them from being added
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
24.03
Release Notes:
Default
Affected Version:
Affected Architecture:
Description
It looks like kea does not allow FQDNs for NTP servers.
ntp-servers 42 ipv4-address true false
Apparently ISC DHCPD did. If a user has an FQDN there kea will not start.
Related issues
Updated by Jim Pingle 5 months ago
- Subject changed from Kea does not allow FQDNs for ntp-servers - pfSense allows one to be entered. to Kea does not allow FQDNs for NTP servers but input validation does not prevent them from being added
- Target version set to 2.8.0
- Plus Target Version set to 24.03
Updated by Danilo Zrenjanin 5 months ago
- Status changed from New to Confirmed
I can confirm this behavior on 23.09.
Updated by Jim Pingle 5 months ago
- Has duplicate Bug #15012: NTP assigned to KEA DHCP Clients causes service to fail added
Updated by Jim Pingle 5 months ago
- Has duplicate Bug #15023: KEA DHCP and ERROR [kea-dhcp4.dhcp4.0x545c1212000] DHCP4_PARSER_FAIL failed to create or run parser for configuration element subnet4: option data does not match option definition (space: dhcp4, code: 42) added
Updated by Sergei Shablovsky 2 months ago
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.
Updated by Jim Pingle about 1 month ago
- Status changed from Confirmed to Feedback
- % Done changed from 0 to 100
Applied in changeset 216df8ac250e2fe705c90f07c2a5e1811e7011e9.
Updated by Jim Pingle about 1 month ago
- Status changed from Feedback to Resolved
Validation is working, as is the backend filtering. Kea starts properly every time now.
Actions