kea-dhcp does not start
-
This post is deleted! -
@Mauricio-Joel-Maidl check your logs? I assume you’re enabling Kea when you test this?
There was a post that using an NTP hostname in DHCP settings was not (yet?) supported, IIRC. (Along with many other things, in the preview/alpha)
-
@Mauricio-Joel-Maidl I have the same issue, was there was there a resolution?
-
@holtdw
Probably : he checked the DHCP log, saw the issue, correct it, and it was solved.
I said 'probably' because people tend to say 'problem' without showing .... -
This post is deleted! -
@Mauricio-Joel-Maidl said in kea-dhcp does not start:
problem still unsolved... enabling kea-dhcp the devices disconnect
If "kea-dhcp does not start" is the case, then cliets can't get a lease.
So, again : what does the system and dhcp log show ? -
This post is deleted! -
This post is deleted! -
This post is deleted! -
@Mauricio-Joel-Maidl said in kea-dhcp does not start:
I am using an NTP hostname in the DHCP settings
This is an IP address :
not a host name ^^
If you were actually using host name like ntp.server.tld, KEA (and also ISC-DHCP) would fail to start.
The popup - this popup :
is wrong.
Only IP v4 and v6 addresses are allowed - a DHCP server will not (and shall not ?) resolve.
