Me again!
Just got 1.2.0 from src up and running perfectly using keactrl. Now taking a
further step in getting kea-ctrl-agent to work but having a couple of issues
when I send requests to the API on the DHCP server itself.
Remote Command:
curl -X POST -H "Content-Type: application/json" -d '{ "command": "config-get",
"service": [ "dhcp4" ] }' http://10.255.11.125:8000/
Returns:
[ { "result": 1, "text": "unable to forward command to the dhcp4 service:
Connection refused. The server is likely to be offline" } ]
So wondering if there is something like permissions on the centos DHCP server
stopping the connection. selinux off (if that makes any difference)!
Obviously getting a response from the CA as it’s responding with something.
Config on DHCP server:
kea.conf -
"Dhcp4":
"control-socket": {
"socket-type": "unix",
"socket-name": "/tmp/kea-dhcp4-ctrl.sock"
},
kea-ca.conf –
"Control-agent": {
"http-host": "10.255.11.125",
"http-port": 8000,
"control-sockets": {
"dhcp4-server": {
"socket-type": "unix",
"socket-name": "/tmp/kea-dhcp4-ctrl.sock"
},
Any ideas? So close with this one!
Neil Briscoe
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users