// This is an example of a configuration for Control-Agent (CA) listening // for incoming HTTP traffic. This is necessary for handling API commands, // in particular lease update commands needed for HA setup. { "Control-agent": { // We need to specify where the agent should listen to incoming HTTP // queries. "http-host": "192.168.1.2", // This specifies the port CA will listen on. "http-port": 8000, "control-sockets": { // This is how the Agent can communicate with the DHCPv4 server. "dhcp4": { "comment": "socket to DHCP4 server", "socket-type": "unix", "socket-name": "/tmp/kea4-ctrl-socket" }, // Location of the DHCPv6 command channel socket. "dhcp6": { "socket-type": "unix", "socket-name": "/tmp/kea6-ctrl-socket" }, // Location of the D2 command channel socket. "d2": { "socket-type": "unix", "socket-name": "/tmp/kea-ddns-ctrl-socket", "user-context": { "in-use": false } } }, // Similar to other Kea components, CA also uses logging. "loggers": [ { "name": "kea-ctrl-agent", "output_options": [ { "output": "/var/log/kea-ctrl-agent.log", // Several additional parameters are possible in addition // to the typical output. Flush determines whether logger // flushes output to a file. Maxsize determines maximum // filesize before the file is being rotated. maxver // specifies the maximum number of rotated files being // kept. "flush": true, "maxsize": 204800, "maxver": 4, // We use pattern to specify custom log message layout "pattern": "%d{%y.%m.%d %H:%M:%S.%q} %-5p [%c/%i] %m\n" } ], "severity": "INFO", "debuglevel": 0 // debug level only applies when severity is set to DEBUG. } ] } }