Kea issueshttps://gitlab.isc.org/isc-projects/kea/-/issues2023-10-12T08:04:56Zhttps://gitlab.isc.org/isc-projects/kea/-/issues/3068CA returns number overflow on ipv6 stats2023-10-12T08:04:56ZPeter DaviesCA returns number overflow on ipv6 statsSending a statistic-get command IPv6 statistics to the control-agent can cause a
number overflow error to be returned to the caller.
Sending the command directly to the Kea process's control socket does not generate
this error.
...Sending a statistic-get command IPv6 statistics to the control-agent can cause a
number overflow error to be returned to the caller.
Sending the command directly to the Kea process's control socket does not generate
this error.
[RT #22759]( https://support.isc.org/Ticket/Display.html?id=22759)kea2.5.3Andrei Pavelandrei@isc.orgAndrei Pavelandrei@isc.orghttps://gitlab.isc.org/isc-projects/kea/-/issues/3066ctrl agent: cannot listen on ipv62023-09-26T13:22:27ZJohn Doectrl agent: cannot listen on ipv6**Describe the bug**
The kea control agent cannot listen on IPv6 addresses via the `http-host` option. We've tried several IPv6 types (GUA, ULA, link local including interface scope) and notations (with brackets and without). For the no...**Describe the bug**
The kea control agent cannot listen on IPv6 addresses via the `http-host` option. We've tried several IPv6 types (GUA, ULA, link local including interface scope) and notations (with brackets and without). For the notation without brackets, the agent silently does not listen at all on an IP address, the notation with brackets, a configuration parsing error occurs.
**To Reproduce**
Steps to reproduce the behavior:
We're using a configuration e.g.
```json
{
"Control-agent": {
"http-host": "$HOST",
"http-port": 8000
// ...
}
}
```
where `$HOST` is
- (empty string) causes `ERROR [kea-ctrl-agent.dctl/433402.140592497919872] DCTL_PARSER_FAIL : Failed to convert to IP address:Failed to convert string to address '': Invalid argument`
- *http-host* line does not exist: listens on 127.0.0.1:8000
- `2001:db8::1` causes about 10 log lines of `RROR [kea-ctrl-agent.dctl/433486.140500168120192] DCTL_PARSER_FAIL : unable to setup TCP acceptor for listening to the incoming HTTP requests: open: Permission denied` and does not listen on the IPv6.
- `[2001:db8::1]` causes about 10 log lines of `ERROR [kea-ctrl-agent.dctl/433528.140127554930560] DCTL_PARSER_FAIL : Failed to convert [2001:db8::1] to IP address:Failed to convert string to address '[2001:db8::1]': Invalid argument` and does not listen on the IPv6
Since we're also loading the HA module, we configure a list of peers with the bracketed IPv6 notation (non-bracketed causes parsing errors):
```json
{
"Dhcp4": {
"hooks-libraries": [
{
"library": "/usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_lease_cmds.so",
"parameters": {}
},
{
"library": "/usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_ha.so",
"parameters": {
"high-availability": [
{
"this-server-name": "host1",
"mode": "hot-standby",
"heartbeat-delay": 10000,
"max-response-delay": 10000,
"max-ack-delay": 5000,
"max-unacked-clients": 5,
"peers": [
{
"name": "host1",
"url": "https://[2001:db8::1]:8000",
"trust-anchor": "/etc/kea/bundle.pem",
"cert-file": "/etc/kea/host.crt",
"key-file": "/etc/kea/host.key",
"auto-failover": true,
"basic-auth-user": "admin",
"basic-auth-password": "..."
# ...
},
{
"name": "host2",
"url": "https://[2001:db8::2]:8000",
"trust-anchor": "/etc/kea/bundle.pem",
"cert-file": "/etc/kea/host.crt",
"key-file": "/etc/kea/host.key",
"role": "standby",
"auto-failover": true,
"basic-auth-user": "admin",
"basic-auth-password": "..."
}
]
...
```
This configuration seems to be accepted correctly.
**Expected behavior**
We expect IPv6 to be fully supported for a top notch project like kea. Are we missing a configuration option?
**Environment:**
- Kea version: version 2.2.0
- OS: debian 11
- Which features were compiled in (in particular which backends)
- If/which hooks where loaded in: HAkea2.5.3https://gitlab.isc.org/isc-projects/kea/-/issues/2475Control Agent config-set command does not work when hook is loaded2022-07-22T13:33:57ZWlodzimierz WencelControl Agent config-set command does not work when hook is loadedVersion: current master
When Control Agent is configured with a hook (we just have rbac for now) and I try to use `config-set` command to change any part of a configuration, Control agent reply with:
```
[
{
"result": 1,
"tex...Version: current master
When Control Agent is configured with a hook (we just have rbac for now) and I try to use `config-set` command to change any part of a configuration, Control agent reply with:
```
[
{
"result": 1,
"text": "some libraries are still opened"
}
]
```
making any remote reconfiguration of control agent impossible. When hook is not loaded `config-set` works correctlykea2.2.0 - a new stable branchFrancis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/2310CA extend COMMAND_RECEIVED message2022-02-10T14:15:32ZPeter DaviesCA extend COMMAND_RECEIVED messageCA extend COMMAND_RECEIVED message:
On the Control Agent would it be possible to log the IP address of the sending client on the same line as the COMMAND_RECEIVED message.
for example:
2022-02-10 13:18:03.145 INFO [kea-ct...CA extend COMMAND_RECEIVED message:
On the Control Agent would it be possible to log the IP address of the sending client on the same line as the COMMAND_RECEIVED message.
for example:
2022-02-10 13:18:03.145 INFO [kea-ctrl-agent.commands/31927.140456776408625] COMMAND_RECEIVED Received command 'subnet4-list' from 10.0.2.15
[RT #15938 ](https://support.isc.org/Ticket/Display.html?id=15938)https://gitlab.isc.org/isc-projects/kea/-/issues/2100systemd dependency problem means isc-kea-ctrl-agent does not autostart at bootup2023-06-16T08:35:18ZBrian Candlersystemd dependency problem means isc-kea-ctrl-agent does not autostart at bootupI have the following packages installed under Ubuntu 18.04 from `deb https://dl.cloudsmith.io/public/isc/kea-1-6/deb/ubuntu bionic main`:
```
ii isc-kea-common 1.6.3-isc0044120200730112858 amd64 Common li...I have the following packages installed under Ubuntu 18.04 from `deb https://dl.cloudsmith.io/public/isc/kea-1-6/deb/ubuntu bionic main`:
```
ii isc-kea-common 1.6.3-isc0044120200730112858 amd64 Common libraries for the ISC Kea DHCP server
ii isc-kea-ctrl-agent 1.6.3-isc0044120200730112858 amd64 ISC Kea DHCP server REST API service
ii isc-kea-dhcp4-server 1.6.3-isc0044120200730112858 amd64 ISC Kea IPv4 DHCP server
ii isc-kea-dhcp6-server 1.6.3-isc0044120200730112858 amd64 ISC Kea IPv6 DHCP server
```
PROBLEM: isc-kea-ctrl-agent is not automatically started by systemd when the machine reboots (but it does start if you manually run `systemctl start isc-kea-ctrl-agent`)
CAUSE: `/lib/systemd/system/isc-kea-ctrl-agent.service` contains:
```
[Install]
WantedBy=kea-dhcp4-server.service
WantedBy=kea-dhcp6-server.service
```
This should instead say:
```
[Install]
WantedBy=isc-kea-dhcp4-server.service
WantedBy=isc-kea-dhcp6-server.service
```
WORKAROUND:
* `systemctl edit isc-kea-ctrl-agent.service`
* enter the `[Install]` section exactly as above, and save.
* `systemctl reenable isc-kea-ctrl-agent.service`kea2.1.0Wlodzimierz WencelWlodzimierz Wencelhttps://gitlab.isc.org/isc-projects/kea/-/issues/2006CA: store credentials in file2022-02-21T08:12:55ZTomek MrugalskiCA: store credentials in fileRight now supports storing user credentials in the config file directly:
```json
"authentication": {
"type": "basic",
"realm": "kea-control-agent",
"clients": [
{
"user": "...Right now supports storing user credentials in the config file directly:
```json
"authentication": {
"type": "basic",
"realm": "kea-control-agent",
"clients": [
{
"user": "admin",
"password": "1234"
} ]
}
```
This is considered insecure as it shows on all config-get results and is being shown in Stork for example. An alternative would be to add credentials file, a file that would contain the same content as `clients: [ ... ]`.kea2.1.2Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/1766Document how to set up secure connections between HA peers in versions before...2022-01-27T13:55:57ZAndrei Pavelandrei@isc.orgDocument how to set up secure connections between HA peers in versions before 1.9.5https://kea.readthedocs.io/en/latest/arm/agent.html?highlight=Secure%20connections#secure-connections-version-before-1-9-5 documents how to secure the connection to a single CA and only works if you have an HTTPS-knowledgeable client. Fo...https://kea.readthedocs.io/en/latest/arm/agent.html?highlight=Secure%20connections#secure-connections-version-before-1-9-5 documents how to secure the connection to a single CA and only works if you have an HTTPS-knowledgeable client. For HA, where all involved entities i.e. CAs don't speak HTTPS, it's a bit more complex and involves changes to both ngins and Kea configuration too. Let's document that.
RT#18110kea2.1.1https://gitlab.isc.org/isc-projects/kea/-/issues/1461Kea 1.8.0 kea-dhcp-ddns missing build info2020-12-04T09:34:55ZPeter DaviesKea 1.8.0 kea-dhcp-ddns missing build info
Kea Arm Chapter 13.2 "Starting and Stopping the DHCP-DDNS Server" suggest that the following command should produce a config.report.
```
strings path/kea-dhcp-ddns | sed -n 's/;;;; //p
```
The binary appear to be missing these string...
Kea Arm Chapter 13.2 "Starting and Stopping the DHCP-DDNS Server" suggest that the following command should produce a config.report.
```
strings path/kea-dhcp-ddns | sed -n 's/;;;; //p
```
The binary appear to be missing these strings on a default build from git (ubuntu 19.10)kea1.9.3Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/1459redact basic HTTP authentication passwords in logs2020-10-19T19:13:11ZFrancis Dupontredact basic HTTP authentication passwords in logsThis ticket proposes to do the same thing as Kea already does with database passwords: they are redacted in logs.
Note that RBAC has a similar output filter which can be applied to config-get responses so it can be extended to basic HTT...This ticket proposes to do the same thing as Kea already does with database passwords: they are redacted in logs.
Note that RBAC has a similar output filter which can be applied to config-get responses so it can be extended to basic HTTP authentication too.kea1.9.1Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/1364Control agent fails forwarding message to DHCP server => hot-standby server d...2020-09-02T14:44:38ZTalkaboutControl agent fails forwarding message to DHCP server => hot-standby server does not start?Hi guys,
I have a question as I might not completely understand the concept behind it.
I am running 2 KEA Dhcp servers, one as primary, one as standby. On the primary I have 2 processes: "kea-ctrl-agent" and "kea-dhcp4". Now I stop "ke...Hi guys,
I have a question as I might not completely understand the concept behind it.
I am running 2 KEA Dhcp servers, one as primary, one as standby. On the primary I have 2 processes: "kea-ctrl-agent" and "kea-dhcp4". Now I stop "kea-dhcp4"... I was assuming that the standby server will pick up serving DHCP requests, but it doesnt. It simply prints:
HA_HEARTBEAT_FAILED heartbeat to dhcp1 (http://192.168.XX.XX:8080/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1
In my opinion in such a case the hot standby server also needs to assume that the primary server is down and needs to be replaced, but obviously, as the control process responds, it does not. Is this expected behavior?
Thanks!
Byekea1.9.0Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/kea/-/issues/1304basic HTTP authentication2020-11-25T21:13:52ZFrancis Dupontbasic HTTP authenticationRelated to #1120 and #1263 but addressing only the access to the control agent by local unprivileged users.
The idea is to implement the basic HTTP authentication (https://tools.ietf.org/html/rfc7617):
- add user and optionally passwor...Related to #1120 and #1263 but addressing only the access to the control agent by local unprivileged users.
The idea is to implement the basic HTTP authentication (https://tools.ietf.org/html/rfc7617):
- add user and optionally password (for the user:password form) in HA config
- add user and optionally password to Kea shell
- add user and password list and realm to CA config
- add the capability to pass the basic credential (i.e. base64(user:password)) to HTTP client code
- add the basic authentication support (require header and check credential from a reversed map) to HTTP listener code
- add support from octet string to UTF-8 translation (JSON is Unicode32, we support its 8 bit subset)
- update the Kea secure shell and the RBAC reverse proxykea1.9.0Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/1263Role based access controls to CA2022-05-25T08:34:40ZVicky Riskvicky@isc.orgRole based access controls to CAThis is related to support RT#15938 and GL #1120.
Along with providing a mechanism for authentication on the CA interface (from Kea, not requiring the reverse proxy - #1120), we have a request for role-based access controls.
Requireme...This is related to support RT#15938 and GL #1120.
Along with providing a mechanism for authentication on the CA interface (from Kea, not requiring the reverse proxy - #1120), we have a request for role-based access controls.
Requirements: https://gitlab.isc.org/isc-projects/kea/-/wikis/designs/rbac-tls-requirements
Design: https://gitlab.isc.org/isc-projects/kea/-/wikis/designs/rbac-tls-designkea2.1.6Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/1234kea logs error every time command channel command is received2020-06-19T16:48:17ZWlodzimierz Wencelkea logs error every time command channel command is received1. setup is simple Kea4 + kea-ctrl-agent, configs at the bottom, important thing is that here I am sending commands on the same interface as dhcp traffic (in system tests we use separate networks)
2. send command via http to ctrl-agent, ...1. setup is simple Kea4 + kea-ctrl-agent, configs at the bottom, important thing is that here I am sending commands on the same interface as dhcp traffic (in system tests we use separate networks)
2. send command via http to ctrl-agent, logs:
```
May 14 15:59:16 ubuntu20-64-1 kea-ctrl-agent: INFO [kea-ctrl-agent.commands.140266868430400] COMMAND_RECEIVED Received command 'config-get'
May 14 15:59:16 ubuntu20-64-1 kea-ctrl-agent: INFO [kea-ctrl-agent.ctrl-agent.140266868430400] CTRL_AGENT_COMMAND_FORWARDED command config-get successfully forwarded to the service dhcp4
```
kea-dhcp4 logs:
```
2020-05-14 15:59:16.351 ERROR [kea-dhcp4.packets/6770.140286406021056] DHCP4_BUFFER_RECEIVE_FAIL error on attempt to receive packet: received data over unknown socket
2020-05-14 15:59:16.351 INFO [kea-dhcp4.commands/6770.140286406021056] COMMAND_RECEIVED Received command 'config-get'
```
4. commands actually works
```
[
{
"arguments": {
"Control-agent": {
"control-sockets": {
"dhcp4": {
"socket-name": "/tmp/control_socket",
"socket-type": "unix"
}
},
"hooks-libraries": [],
"http-host": "192.168.59.2",
"http-port": 8000,
"loggers": [
{
"debuglevel": 0,
"name": "kea-ctrl-agent",
"output_options": [
{
"flush": true,
"maxsize": 10240000,
"maxver": 1,
"output": "syslog",
"pattern": ""
}
],
"severity": "INFO"
}
]
}
},
"result": 0
}
```
```
[
{
"arguments": {
"Dhcp4": {
"authoritative": false,
"boot-file-name": "",
"calculate-tee-times": false,
"config-control": {
"config-databases": [
{
"name": "keatest",
"password": "keatest",
"type": "mysql",
"user": "keatest"
}
],
"config-fetch-wait-time": 0
},
"control-socket": {
"socket-name": "/tmp/control_socket",
"socket-type": "unix"
},
"ddns-generated-prefix": "myhost",
"ddns-override-client-update": false,
"ddns-override-no-update": false,
"ddns-qualifying-suffix": "",
"ddns-replace-client-name": "never",
"ddns-send-updates": true,
"decline-probation-period": 86400,
"dhcp-ddns": {
"enable-updates": false,
"max-queue-size": 1024,
"ncr-format": "JSON",
"ncr-protocol": "UDP",
"sender-ip": "0.0.0.0",
"sender-port": 0,
"server-ip": "127.0.0.1",
"server-port": 53001
},
"dhcp-queue-control": {
"capacity": 500,
"enable-queue": false,
"queue-type": "kea-ring4"
},
"dhcp4o6-port": 0,
"echo-client-id": true,
"expired-leases-processing": {
"flush-reclaimed-timer-wait-time": 25,
"hold-reclaimed-time": 3600,
"max-reclaim-leases": 100,
"max-reclaim-time": 250,
"reclaim-timer-wait-time": 10,
"unwarned-reclaim-cycles": 5
},
"hooks-libraries": [
{
"library": "/home/wlodek/kea_bin/lib/kea/hooks/libdhcp_mysql_cb.so"
},
{
"library": "/home/wlodek/kea_bin/lib/kea/hooks/libdhcp_cb_cmds.so"
}
],
"host-reservation-identifiers": [
"hw-address",
"duid",
"circuit-id",
"client-id"
],
"hostname-char-replacement": "",
"hostname-char-set": "[^A-Za-z0-9.-]",
"interfaces-config": {
"interfaces": [
"enp0s8"
],
"re-detect": true
},
"lease-database": {
"type": "memfile"
},
"loggers": [
{
"name": "kea-dhcp4",
"output_options": [
{
"output": "stdout"
}
],
"severity": "DEBUG"
}
],
"match-client-id": true,
"multi-threading": {
"enable-multi-threading": false,
"packet-queue-size": 64,
"thread-pool-size": 0
},
"next-server": "0.0.0.0",
"option-data": [],
"option-def": [],
"reservation-mode": "all",
"sanity-checks": {
"lease-checks": "warn"
},
"server-hostname": "",
"server-tag": "abc",
"shared-networks": [],
"statistic-default-sample-age": 0,
"statistic-default-sample-count": 20,
"store-extended-info": false,
"subnet4": [],
"t1-percent": 0.5,
"t2-percent": 0.875,
"valid-lifetime": 7200
}
},
"result": 0
}
]
```kea1.7.9Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/1120Refine reverse proxy for kea2021-06-28T08:22:33ZRazvan BecheriuRefine reverse proxy for keaWhen we implemented Kea Control Agent we considered whether we should provide a built-in solution for https or not. At that time, it seemed reasonable to rely on third party HTTP servers, such as nginx to provide reverse proxy function b...When we implemented Kea Control Agent we considered whether we should provide a built-in solution for https or not. At that time, it seemed reasonable to rely on third party HTTP servers, such as nginx to provide reverse proxy function because we don't have the maintain the security critical code. The third party HTTP servers are trustworthy when it comes to security. However, we've had reports that installing such a third party software is not always possible, especially when talking about large installations.
This ticket resumes the discussion how we could possibly provide a viable alternative to third party reverse proxies and ship something with Kea that would provide similar function and would be easy to install, deploy and run.
A discussion/high level design page is here: https://gitlab.isc.org/isc-projects/kea/-/wikis/designs/https-wrapper-for-control-agent-discussionKea1.9-backloghttps://gitlab.isc.org/isc-projects/kea/-/issues/910kea-ctrl-agent config-set and config-test commands not working properly2020-09-10T09:33:16ZWlodzimierz Wencelkea-ctrl-agent config-set and config-test commands not working properlyControl-agent accept almost anything as correct config while using `config-set` and `config-test` commands, it's just need to be proper JSON.
send:
```
{'arguments': {'Control-agent': {'AaAASDASDAsd': 'oijsadoeifbias'}},
'command': 'co...Control-agent accept almost anything as correct config while using `config-set` and `config-test` commands, it's just need to be proper JSON.
send:
```
{'arguments': {'Control-agent': {'AaAASDASDAsd': 'oijsadoeifbias'}},
'command': 'config-set'}
```
response:
```
{
"result": 0,
"text": "Configuration applied successfully."
}
```
send:
```
{'arguments': {'Control-agent': {'control-sockets': {'dhcp6': {'socket-name': '/tmp/control_socket',
'socket-type': 'SOMETHING'}},
'hooks-libraries': [],
'http-host': '192.168.50.252',
'http-port': 8000,
'reverse-ddns': {}}},
'command': 'config-test'}
```
response:
```
{
"result": 0,
"text": "Configuration check successful"
}
```
Kea configuration file:
```
{
"Control-agent": {
"control-sockets": {
"dhcp6": {
"socket-name": "/home/wlodek/installed/git/var/run/kea/control_socket",
"socket-type": "unix"
}
},
"http-host": "192.168.50.252",
"http-port": 8000
}
}
```
Kea/OS versions:
```
sbin/kea-ctrl-agent -V
1.7.0-git
git f07587f8c62ac1f431487cf591b2b38d08f1303f
```
```
lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.11 (stretch)
Release: 9.11
Codename: stretch
```
```
Kea source configure results:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Package:
Name: kea
Version: 1.7.0-git
Extended version: 1.7.0-git (git f07587f8c62ac1f431487cf591b2b38d08f1303f)
OS Family: Linux
Prefix: /home/wlodek/installed/git
Hooks directory: /home/wlodek/installed/git/lib/kea/hooks
Premium hooks: yes
Included Hooks: forensic_log flex_id host_cmds subnet_cmds radius host_cache class_cmds cb_cmds
C++ Compiler:
CXX: ccache g++
CXX_VERSION: g++ (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
CXX_STANDARD: 201402
DEFS: -DHAVE_CONFIG_H
CPPFLAGS: -DOS_LINUX
CXXFLAGS: -g -O2
LDFLAGS: -lpthread
KEA_CXXFLAGS: -Wall -Wextra -Wnon-virtual-dtor -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -pthread -Wno-missing-field-initializers -fPIC
Python:
PYTHON: /usr/bin/python3
PYTHON_VERSION: 3.5
Boost:
BOOST_VERSION: 1.62
BOOST_INCLUDES:
BOOST_LIBS: -lboost_system
OpenSSL:
CRYPTO_VERSION: OpenSSL 1.0.2s 28 May 2019
CRYPTO_CFLAGS:
CRYPTO_INCLUDES:
CRYPTO_LDFLAGS:
CRYPTO_LIBS: -lcrypto
Botan: no
Log4cplus:
LOG4CPLUS_VERSION: 1.1.2
LOG4CPLUS_INCLUDES: -I/usr/include
LOG4CPLUS_LIBS: -L/usr/lib -llog4cplus
Flex/bison:
FLEX: flex
BISON: /usr/bin/bison
MySQL:
MYSQL_VERSION: 10.1.38
MYSQL_CPPFLAGS: -I/usr/include/mysql
MYSQL_LIBS: -L/usr/lib/x86_64-linux-gnu -lmariadbclient -lpthread -lz -lm -ldl -lcrypto
PostgreSQL:
PGSQL_VERSION: PostgreSQL 9.6.15
PGSQL_CPPFLAGS: -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I/usr/include/libxml2 -I/usr/include/tcl8.6 -I/usr/include/postgresql -I/usr/include/postgresql/9.6/server
PGSQL_LIBS: -L/usr/lib/x86_64-linux-gnu -lpq
Cassandra CQL:
no
Sysrepo:
SYSREPO_VERSION: 0.7.8
SYSREPO_CPPFLAGS: -I/usr/local/include
SYSREPO_LIBS: -L/usr/local/lib -lsysrepo -L/usr/local/lib -lSysrepo-cpp
SYSREPO_REPO: /etc/sysrepo
Google Test:
no
Google Benchmark:
no
FreeRADIUS client:
FREERADIUS_INCLUDE: -I/usr/local/include
FREERADIUS_LIB: -L/usr/local/lib -lfreeradius-client
FREERADIUS_DICTIONARY: /usr/local/etc/radiusclient/dictionary
Developer:
Enable Debugging: no
Google Tests: no
Google Benchmark: no
Valgrind: found
C++ Code Coverage: no
Logger checks: no
Generate Documentation: no
Generate Parser: no
Generate Messages Files: no
Perfdhcp: yes
Kea-shell: yes, install to ${prefix}/lib/python3.5/site-packages
```https://gitlab.isc.org/isc-projects/kea/-/issues/795Path to control socket in DHCP4 example does not match CA example2019-10-25T14:23:21ZTomek MrugalskiPath to control socket in DHCP4 example does not match CA exampledoc/example/kea4/advanced.json uses `/tmp/kea4-ctrl-socket` and the config installed in /etc/kea/kea-ctrl-agent.conf uses `"/tmp/kea-dhcp4-ctrl.sock`.
As a result, the CA is unable to contact DHCP4 and returns misleading information: `[...doc/example/kea4/advanced.json uses `/tmp/kea4-ctrl-socket` and the config installed in /etc/kea/kea-ctrl-agent.conf uses `"/tmp/kea-dhcp4-ctrl.sock`.
As a result, the CA is unable to contact DHCP4 and returns misleading information: `[ { "result": 1, "text": "unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline" } ]`kea1.7.1Tomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/kea/-/issues/721kea-shell is not working when installed from a debian package2019-08-15T15:07:07ZMichal Nowikowskikea-shell is not working when installed from a debian packageThe problem is with hardcoded path for importing of kea_conn.
In kea-shell, this should be removed:
```python
sys.path.append('@PKGPYTHONDIR@')
```
and this:
```python
from kea_conn import CARequest # CAResponse
```
should be change...The problem is with hardcoded path for importing of kea_conn.
In kea-shell, this should be removed:
```python
sys.path.append('@PKGPYTHONDIR@')
```
and this:
```python
from kea_conn import CARequest # CAResponse
```
should be changed to:
```python
from kea.kea_conn import CARequest # CAResponse
```Kea1.6-finalTomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/kea/-/issues/491kea-ctrl-agent crashing due to HttpMessage::create() must be called first2019-07-22T10:51:58ZGhost Userkea-ctrl-agent crashing due to HttpMessage::create() must be called first---
name: Bug report
about: Create a report to help us improve
---
**Describe the bug**
From time to time we're unable to poll the API for statistics (monitoring purposes). It seems that either the kea-ctrl-agent or kea-server and the ...---
name: Bug report
about: Create a report to help us improve
---
**Describe the bug**
From time to time we're unable to poll the API for statistics (monitoring purposes). It seems that either the kea-ctrl-agent or kea-server and the agent die without any further ado. Please see attached informations.
**To Reproduce**
Steps to reproduce the behavior:
1. Run Kea (dhcpv4 + dhcpv6)
2. Periodicly poll the statistics from web-api
**Expected behavior**
A clear and concise description of what you expected to happen:
Consistent answering of requests
**Environment:**
- Kea version: 1.5.0
- OS: CentOS x64 7
**Additional Information**
`
2019-02-21 06:05:37.668 FATAL [kea-ctrl-agent.ctrl-agent/60721] CTRL_AGENT_FAILED application experienced a fatal error: unable to retrieve values of HTTP message because the HttpMessage::create() must be called first. This is a programmatic error
2019-02-21 06:07:53.545 FATAL [kea-ctrl-agent.ctrl-agent/81818] CTRL_AGENT_FAILED application experienced a fatal error: unable to retrieve values of HTTP message because the HttpMessage::create() must be called first. This is a programmatic error
2019-02-21 06:09:37.191 FATAL [kea-ctrl-agent.ctrl-agent/81849] CTRL_AGENT_FAILED application experienced a fatal error: unable to retrieve values of HTTP message because the HttpMessage::create() must be called first. This is a programmatic error
2019-02-21 06:11:37.570 FATAL [kea-ctrl-agent.ctrl-agent/81864] CTRL_AGENT_FAILED application experienced a fatal error: unable to retrieve values of HTTP message because the HttpMessage::create() must be called first. This is a programmatic error
2019-02-21 06:13:37.177 FATAL [kea-ctrl-agent.ctrl-agent/81880] CTRL_AGENT_FAILED application experienced a fatal error: unable to retrieve values of HTTP message because the HttpMessage::create() must be called first. This is a programmatic error
2019-02-21 06:16:37.769 FATAL [kea-ctrl-agent.ctrl-agent/81893] CTRL_AGENT_FAILED application experienced a fatal error: unable to retrieve values of HTTP message because the HttpMessage::create() must be called first. This is a programmatic error
`Kea1.6-beta2Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/148lib process servers without arguments2018-10-19T22:25:15ZFrancis Dupontlib process servers without argumentsAll servers that use CPL architecture (D2, CA, netconf) are unable to print out usage information when run without any parameters. Instead, they print out cryptic error message as shown below:
```$ kea-ctrl-agent
2018-10-01 22:28:51.285...All servers that use CPL architecture (D2, CA, netconf) are unable to print out usage information when run without any parameters. Instead, they print out cryptic error message as shown below:
```$ kea-ctrl-agent
2018-10-01 22:28:51.285 FATAL [kea-ctrl-agent.dctl/23508] DCTL_PID_FILE_ERROR
Control-agent could not create a PID file: Daemon::makePIDFileName config file name is not set
Service failed: Launch failed: Daemon::makePIDFileName config file name is not set'''Kea1.5-beta1