From Peter Davies ([email protected] <mailto:[email protected]>):
> Hi Johathan,
> ?? The kea-ctrl-agent listens for commands on http://192.168.20.254:8000
> <http://192.168.20.254:8000/> .
>
> The kea-dhcp6 and kea-dhcp4 processes create and listen on the Unix sockets.
> Have you configured kea-dhcp6 and kea-dhcp4 to listen on these sockets,
> and are
> these processes running?
Hi Peter (and list),
It looks like my mistake was the assumption that the control agent was
responsible for creating the sockets. Digging a little deeper into the
documentation, I was able to find where socket creation was managed within the
dhcp4 and dhcp6 server configurations. With the following stanzas inserted
into dhcp configuration files, everything works as advertised:
(from /etc/kea/kea-dhcp4.conf)
"peers": [
{
"name": “host2",
"url": "http://192.168.20.253:8000/";,
"role": "standby",
"basic-auth-user": "kea-api",
"basic-auth-password-file": "/etc/kea/kea-api-password",
"auto-failover": true
},
{
"name": “host1",
"url": "http://192.168.20.254:8000/";,
"role": "primary",
"basic-auth-user": "kea-api",
"basic-auth-password-file": "/etc/kea/kea-api-password",
"auto-failover": true
}
]
Many thanks for your help and I hope that the above snippet might be found by
other Kea neophytes and save them from making the same mistake that I did.
Thanks,
Jonathan.--
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
