Hi Russell, One CA is able to interface with dhcp4 and dhcp6. Why do you want to run two of them? Is this about listening on v4 and v6 sockets? We could talk about some extension to control agent, so it would maintain two sockets. Would such a thing address your problem?
Also, for the specific issue, the location of pid file can be controlled with KEA_PIDFILE_DIR environment variable. Since you're using packaged version, the alternative does not appeal to you, but if you compile Kea yourself, you can also alter localstatedir in configure script. On 25.01.2019 18:25, russell aspinwall wrote: > It would be nice to configure two kea-ctrl-agents with in a single > file with processes spawned to handle the different ip/socket combinations > > "Control-agent": { > "http-host": "192.168.26.248", > "http-port": 8080, > > "control-sockets": { > "dhcp4": { > "socket-type": "unix", > "socket-name": "/tmp/kea-dhcp4-ctrl.sock" > } > } > }, > "Control-agent": { > "http-host": "fd22:318a:1212:1:8456:1466:9675:5991", > "http-port": 8081, > > "control-sockets": { > "dhcp6": { > "socket-type": "unix", > "socket-name": "/tmp/kea-dhcp6-ctrl.sock" > } > } > > }, That's not a valid JSON. So no, that's not possible. Tomek _______________________________________________ Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users