ISC Open Source Projects issueshttps://gitlab.isc.org/groups/isc-projects/-/issues2023-10-05T13:49:05Zhttps://gitlab.isc.org/isc-projects/kea/-/issues/3090Move the krb5.conf config file in hammer2023-10-05T13:49:05ZFrancis DupontMove the krb5.conf config file in hammerWhen a Kerberos V library is installed a kerb5.conf config file is installed. Often it interferes with the gss_tig hook unit tests making some of them to fail. As documented in the ARM the default setting from this config file can be inc...When a Kerberos V library is installed a kerb5.conf config file is installed. Often it interferes with the gss_tig hook unit tests making some of them to fail. As documented in the ARM the default setting from this config file can be incompatible with these tests. The solution is to remove or rename it: this ticket is about doing this in hammer.next-stable-2.6https://gitlab.isc.org/isc-projects/stork/-/issues/1167Stop asking about server access token when registering a client in an automat...2023-10-17T13:24:29ZPeter MagnussonStop asking about server access token when registering a client in an automated manner---
name: Feature request
about: Stop asking about server access token when registering a client in an automated manner
When automating the registration of a stork agent it still asks for
`>>>> Server access token (optional):` if I pro...---
name: Feature request
about: Stop asking about server access token when registering a client in an automated manner
When automating the registration of a stork agent it still asks for
`>>>> Server access token (optional):` if I provide all other arguments.
It's really helpful when you are in some kind of interactive session
but it creates some mess if you want to automate it with a script.outstandinghttps://gitlab.isc.org/isc-projects/kea/-/issues/3089Sanity checks for Kea 2.5.2 rc22023-10-05T13:45:56ZMarcin GodzinaSanity checks for Kea 2.5.2 rc2We are now at step SANITY CHECKS of Kea 2.5.2 rc2.
Please verify the tarballs and packages according to [chapter `4. Sanity Checks` of the release procedure](https://gitlab.isc.org/isc-private/qa-dhcp/-/wikis/Kea/Release-Process#user-co...We are now at step SANITY CHECKS of Kea 2.5.2 rc2.
Please verify the tarballs and packages according to [chapter `4. Sanity Checks` of the release procedure](https://gitlab.isc.org/isc-private/qa-dhcp/-/wikis/Kea/Release-Process#user-content-4-sanity-checks) and according to your imagination.
Before starting, please state what you are checking in a thread/discussion (not as comment).
When you finish a check, state in the same thread/discussion what the result is.
This way we know what is covered upfront and we can avoid repeating ourselves.
#### Tarballs on repo.isc.org
* `/data/shared/sweng/kea/releases/2.5.2-rc2`
* `/data/shared/sweng/kea/releases/premium-2.5.2-rc2`
* `/data/shared/sweng/kea/releases/subscription-2.5.2-rc2`
* `/data/shared/sweng/kea/releases/enterprise-2.5.2-rc2`
```
SHA256 (kea-2.5.2.tar.gz) = 47198bcdb9e30a694230997d1ece4569f01c5b003125655a91700586fe5243a7
SHA256 (kea-enterprise-2.5.2.tar.gz) = f1c564d434a872f48a8b646bd2adc223cc824de7390e1bc08aed744d0973fc42
SHA256 (kea-premium-2.5.2.tar.gz) = 4ef952ad3acb0cb3569a53206f9185221c1a59b1fcfed6ccfd08b6e270c23963
SHA256 (kea-subscription-2.5.2.tar.gz) = 9916be550c65dc8e4544f36d82f9caa3440e56fd31c200e9c3fe0563e884f7de
```
#### Packages on packages.aws.isc.org
* [APK: 2.5.2-r20230926095551](https://packages.aws.isc.org/#browse/search/raw=format%3Draw%20AND%20name.raw%3D*r20230926095551.apk)
* [deb: 2.5.2-isc20230926095551](https://packages.aws.isc.org/#browse/search/apt=format%3Dapt%20AND%20version%3D2.5.2-isc20230926095551)
* [RPM: 2.5.2-isc20230926095551.\[os\]](https://packages.aws.isc.org/#browse/search/yum=format%3Dyum%20AND%20version%3D2.5.2-isc20230926095551*)
You can find the name for all the packages attached as build artifacts in the pkg job: https://jenkins.aws.isc.org/job/kea-dev/job/pkg/1294/
Instructions for installing packages are at point 9 of [chapter `4. Sanity Checks` of the release procedure](https://gitlab.isc.org/isc-private/qa-dhcp/-/wikis/Kea/Release-Process#user-content-4-sanity-checks).https://gitlab.isc.org/isc-projects/kea-docker/-/issues/23add ping-check package2023-09-26T09:55:37ZMarcin Godzinaadd ping-check packageadd ping-check packageadd ping-check packageMarcin GodzinaMarcin Godzinahttps://gitlab.isc.org/isc-projects/kea-docker/-/issues/22Allow package version in docker file2023-09-26T09:18:15ZMarcin GodzinaAllow package version in docker fileMarcin GodzinaMarcin Godzinahttps://gitlab.isc.org/isc-projects/stork/-/issues/1165Session manager is never closed.2023-10-03T13:47:21ZSlawek FigielSession manager is never closed.The session manager allocates two heavy resources:
- Database connection
- Forever running goroutine that operates on the database
These resources are never free. It should not be a problem in production as they are cleaned up by the o...The session manager allocates two heavy resources:
- Database connection
- Forever running goroutine that operates on the database
These resources are never free. It should not be a problem in production as they are cleaned up by the operating system on the application shutdown. But it may cause confusing issues in the development environment.backloghttps://gitlab.isc.org/isc-projects/kea/-/issues/3088Sanity checks for Kea 2.5.2 rc12023-09-26T18:15:38ZMarcin GodzinaSanity checks for Kea 2.5.2 rc1We are now at step SANITY CHECKS of Kea 2.5.2 rc1.
Please verify the tarballs and packages according to [chapter `4. Sanity Checks` of the release procedure](https://gitlab.isc.org/isc-private/qa-dhcp/-/wikis/Kea/Release-Process#user-co...We are now at step SANITY CHECKS of Kea 2.5.2 rc1.
Please verify the tarballs and packages according to [chapter `4. Sanity Checks` of the release procedure](https://gitlab.isc.org/isc-private/qa-dhcp/-/wikis/Kea/Release-Process#user-content-4-sanity-checks) and according to your imagination.
Before starting, please state what you are checking in a thread/discussion (not as comment).
When you finish a check, state in the same thread/discussion what the result is.
This way we know what is covered upfront and we can avoid repeating ourselves.
#### Tarballs on repo.isc.org
* `/data/shared/sweng/kea/releases/2.5.2-rc1`
* `/data/shared/sweng/kea/releases/premium-2.5.2-rc1`
* `/data/shared/sweng/kea/releases/subscription-2.5.2-rc1`
* `/data/shared/sweng/kea/releases/enterprise-2.5.2-rc1`
```
SHA256 (kea-2.5.2.tar.gz) = f61ec5bb5c5400ee65a56a11f031ac2e26dbb517824d09a247c233a6985ca475
SHA256 (kea-enterprise-2.5.2.tar.gz) = d7905e34f72766e4ef23269529aa5932c735bf4f38bb644c4e0d5120b213f4fb
SHA256 (kea-premium-2.5.2.tar.gz) = 7ec8d48aafd167920731d85bf7719b85002ed15bd4d38683297e71d9fc9b4b84
SHA256 (kea-subscription-2.5.2.tar.gz) = db46c0f61f35426b6b6116a351b5fea0f397e3588e76aa5f09fa0155109d3366
```
#### Packages on packages.aws.isc.org
* [APK: 2.5.2-r20230925151810](https://packages.aws.isc.org/#browse/search/raw=format%3Draw%20AND%20name.raw%3D*r20230925151810.apk)
* [deb: 2.5.2-isc20230925151810](https://packages.aws.isc.org/#browse/search/apt=format%3Dapt%20AND%20version%3D2.5.2-isc20230925151810)
* [RPM: 2.5.2-isc20230925151810.\[os\]](https://packages.aws.isc.org/#browse/search/yum=format%3Dyum%20AND%20version%3D2.5.2-isc20230925151810*)
You can find the name for all the packages attached as build artifacts in the pkg job: https://jenkins.aws.isc.org/job/kea-dev/job/pkg/1292/
Instructions for installing packages are at point 9 of [chapter `4. Sanity Checks` of the release procedure](https://gitlab.isc.org/isc-private/qa-dhcp/-/wikis/Kea/Release-Process#user-content-4-sanity-checks).https://gitlab.isc.org/isc-projects/kea-packaging/-/issues/20move radius hook based on freeradius to old_radius hook and introduce new pkg...2023-09-25T13:53:29ZWlodzimierz Wencelmove radius hook based on freeradius to old_radius hook and introduce new pkg for new radiusiiWlodzimierz WencelWlodzimierz Wencelhttps://gitlab.isc.org/isc-projects/kea-docker/-/issues/21remove curl2023-09-25T10:54:22ZWlodzimierz Wencelremove curlThere is a cve https://www.cve.org/CVERecord?id=CVE-2023-38039 we have to remove curlThere is a cve https://www.cve.org/CVERecord?id=CVE-2023-38039 we have to remove curlWlodzimierz WencelWlodzimierz Wencelhttps://gitlab.isc.org/isc-projects/kea/-/issues/3082kea-ctrl-agent and dual stack listening2024-03-21T11:45:53ZDarren Ankneykea-ctrl-agent and dual stack listeningThe `kea-ctrl-agent` can presently only listen on one address, be that an IPv4 or IPv6 address. If you have a dual stack on the equipment where you want to listen, then you have to choose either the IPv4 or the IPv6 address to configure...The `kea-ctrl-agent` can presently only listen on one address, be that an IPv4 or IPv6 address. If you have a dual stack on the equipment where you want to listen, then you have to choose either the IPv4 or the IPv6 address to configure in the `kea-ctrl-agent.json`.
I propose to add a new parameter to the kea-ctrl-agent configuration "http-hosts" as shown:
```
{
"Control-agent": {
"http-hosts": [
"2001:db8::2",
"10.1.2.2"
],
"http-port": 8000,
"control-sockets": {
"dhcp4": {
"socket-type": "unix",
"socket-name": "/tmp/socket4"
}
}
}
}
```
This would allow listening on multiple IP addresses especially in a dual stack environment. Also, the new parameter would preserve backward compatibility.
FYI: I did solve this problem by running two copies of the `kea-ctrl-agent`. However, I'm not convinced that is a good solution. Configurations and other details included below for illustration.
<details><summary>kea-dhcp4.json</summary>
```
{
"Dhcp4": {
"control-socket": {
"socket-type": "unix",
"socket-name": "/tmp/socket4"
},
"interfaces-config": {
"interfaces": [
"ens256"
]
},
"lease-database": {
"type": "memfile",
"persist": false
},
"subnet4": [
{
"subnet": "10.1.2.0/24",
"id": 1,
"option-data": [
{
"name": "routers",
"data": "10.1.2.1"
}
],
"pools": [
{
"pool": "10.1.2.100 - 10.1.2.254"
}
]
}
],
"loggers": [
{
"name": "kea-dhcp4",
"severity": "INFO",
"output_options": [
{
"output": "stdout"
}
]
}
]
}
}
```
</details>
<details><summary>kea-ctrl-agent-v4.json</summary>
```
{
"Control-agent": {
"http-host": "10.1.2.2",
"http-port": 8000,
"control-sockets": {
"dhcp4": {
"socket-type": "unix",
"socket-name": "/tmp/socket4"
}
}
}
}
```
</details>
<details><summary>kea-ctrl-agent-v6.json</summary>
```
{
"Control-agent": {
"http-host": "2001:db8::2",
"http-port": 8000,
"control-sockets": {
"dhcp4": {
"socket-type": "unix",
"socket-name": "/tmp/socket4"
}
}
}
}
```
</details>
<details><summary>Configuration of ens256</summary>
```
3: ens256: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:29:c0:5f:47 brd ff:ff:ff:ff:ff:ff
altname enp26s0
inet 10.1.2.2/24 brd 10.1.2.255 scope global ens256
valid_lft forever preferred_lft forever
inet6 2001:db8::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::20c:29ff:fec0:5f47/64 scope link
valid_lft forever preferred_lft forever
```
</details>
<details><summary>Daemon command lines</summary>
```
kea-dhcp4 -c kea-dhcp4.json
```
```
kea-ctrl-agent -c kea-ctrl-agent-v4.json
```
```
kea-ctrl-agent -c kea-ctrl-agent-v6.json
```
</details>
<details><summary>Send config-get with curl to both</summary>
```
curl -X POST -H "Content-Type: application/json" -d '{ "command": "config-get", "service": [ "dhcp4" ] }' http://10.1.2.2:8000/ | jq
```
```
curl -X POST -H "Content-Type: application/json" -d '{ "command": "config-get", "service": [ "dhcp4" ] }' http://[2001:db8::2]:8000/
```
</details>
Both returned a result successfully.
[SF1260](https://isc.lightning.force.com/lightning/r/Case/5007V00002X2x4cQAB/view)next-stable-3.0https://gitlab.isc.org/isc-projects/bind9/-/issues/4329BIND starting before network is completely online2023-09-22T14:00:22ZJon FullmerBIND starting before network is completely online<!--
If the bug you are reporting is potentially security-related - for example,
if it involves an assertion failure or other crash in `named` that can be
triggered repeatedly - then please make sure that you make the new issue
confident...<!--
If the bug you are reporting is potentially security-related - for example,
if it involves an assertion failure or other crash in `named` that can be
triggered repeatedly - then please make sure that you make the new issue
confidential!
-->
### Summary
On system boot, BIND is attempting to start before network services are completely online
### BIND version used
```
BIND 9.18.19 (Extended Support Version) <id:c78cd36>
running on Linux x86_64 5.14.0-284.25.1.el9_2.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jul 20 09:11:28 EDT 2023
built by make with '--build=x86_64-redhat-linux-gnu' '--host=x86_64-redhat-linux-gnu' '--program-prefix=' '--disable-dependency-tracking' '--prefix=/opt/isc/isc-bind/root/usr' '--exec-prefix=/opt/isc/isc-bind/root/usr' '--bindir=/opt/isc/isc-bind/root/usr/bin' '--sbindir=/opt/isc/isc-bind/root/usr/sbin' '--sysconfdir=/etc/opt/isc/scls/isc-bind' '--datadir=/opt/isc/isc-bind/root/usr/share' '--includedir=/opt/isc/isc-bind/root/usr/include' '--libdir=/opt/isc/isc-bind/root/usr/lib64' '--libexecdir=/opt/isc/isc-bind/root/usr/libexec' '--localstatedir=/var/opt/isc/scls/isc-bind' '--sharedstatedir=/var/opt/isc/scls/isc-bind/lib' '--mandir=/opt/isc/isc-bind/root/usr/share/man' '--infodir=/opt/isc/isc-bind/root/usr/share/info' '--enable-warn-error' '--disable-static' '--enable-dnstap' '--with-pic' '--with-gssapi' '--with-json-c' '--with-libxml2' '--without-lmdb' 'build_alias=x86_64-redhat-linux-gnu' 'host_alias=x86_64-redhat-linux-gnu' 'CC=gcc' 'CFLAGS=-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer' 'LDFLAGS=-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -L/opt/isc/isc-bind/root/usr/lib64' 'CPPFLAGS= -I/opt/isc/isc-bind/root/usr/include' 'LT_SYS_LIBRARY_PATH=/usr/lib64' 'PKG_CONFIG_PATH=:/opt/isc/isc-bind/root/usr/lib64/pkgconfig:/opt/isc/isc-bind/root/usr/share/pkgconfig' 'SPHINX_BUILD=/builddir/build/BUILD/bind-9.18.19/sphinx/bin/sphinx-build'
compiled by GCC 11.3.1 20221121 (Red Hat 11.3.1-4)
compiled with OpenSSL version: OpenSSL 3.0.7 1 Nov 2022
linked to OpenSSL version: OpenSSL 3.0.7 1 Nov 2022
compiled with libuv version: 1.44.2
linked to libuv version: 1.44.2
compiled with libnghttp2 version: 1.43.0
linked to libnghttp2 version: 1.43.0
compiled with libxml2 version: 2.9.13
linked to libxml2 version: 20913
compiled with json-c version: 0.14
linked to json-c version: 0.14
compiled with zlib version: 1.2.11
linked to zlib version: 1.2.11
compiled with protobuf-c version: 1.4.1
linked to protobuf-c version: 1.4.1
threads support is enabled
DNSSEC algorithms: RSASHA256 RSASHA512 ECDSAP256SHA256 ECDSAP384SHA384 ED25519 ED448
DS algorithms: SHA-1 SHA-256 SHA-384
HMAC algorithms: HMAC-MD5 HMAC-SHA1 HMAC-SHA224 HMAC-SHA256 HMAC-SHA384 HMAC-SHA512
TKEY mode 2 support (Diffie-Hellman): yes
TKEY mode 3 support (GSS-API): yes
default paths:
named configuration: /etc/opt/isc/scls/isc-bind/named.conf
rndc configuration: /etc/opt/isc/scls/isc-bind/rndc.conf
DNSSEC root key: /etc/opt/isc/scls/isc-bind/bind.keys
nsupdate session key: /var/opt/isc/scls/isc-bind/run/named/session.key
named PID file: /var/opt/isc/scls/isc-bind/run/named/named.pid
named lock file: /var/opt/isc/scls/isc-bind/run/named/named.lock
```
### Steps to reproduce
Using RHEL 9.2:
1) add additional IPv4 addresses to the system's default interface
2) Install latest BIND from ISC COPR repo
3) Make sure that BIND will start on boot: systemctl enable isc-bind-named
4) Use views in the named.conf that "match-destinations" to one or more of the additional IPv4 addresses in step 1
5) Reboot the OS
### What is the current *bug* behavior?
BIND fails to start on boot. Error messages include (from /var/log/messages file):
```
could not get query source dispatcher (<ip-mentioned-in-step1-reproduce>#0)
loading configuration: address not available
exiting (due to fatal error)
```
### What is the expected *correct* behavior?
I expect isc-bind-named to start on system boot, after the network addresses are completely online.
### Relevant configuration files
Sample /etc/sysconfig/network-scripts/ifcfg-eth0 file:
```
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
TYPE=Ethernet
IPADDR=<primary-IPv4-address>
PREFIX=24
NETMASK=255.255.255.0
IPADDR1=<secondary-IPv4-address-in-same-subnet>
PREFIX1=24
NETMASK1=255.255.255.0
```
Sample /etc/opt/isc/scls/isc-bind/named.conf file (view portion):
```
view "my-view" {
match-destinations {
<secondary-IPv4-address>;
};
notify-source <secondary-IPv4-address>;
transfer-source <secondary-IPv4-address>;
query-source <secondary-IPv4-address>;
recursion yes;
minimal-responses yes;
allow-query { any; };
};
```
### Possible fixes
The problem is in the /usr/lib/systemd/system/isc-bind-named.service file. The first two lines are currently:
```
[Unit]
After=network.target
```
A workaround is to:
1) Create a directory: /etc/systemd/system/isc-bind-named.service.d
2) Create a supplemental conf file in the above directory (must have the suffix ".conf") **EXAMPLE:** 00-latestart.conf:
```
[Unit]
After=network-online.target
```
This overrides the isc-bind-named.service file setting of "After=network.target", and changes the setting to "After=network-online.target". This will correctly wait until all interfaces are configured and online before attempting to start BIND.
It should be noted that one can temporarily achieve the same outcome by manually editing the /usr/lib/systemd/system/isc-bind-named.service file, but the change will be overwritten the next time the package is updated.
I would respectfully encourage a permanent change to the isc-bind-named.service file to change the "After" value to "network-online.target".https://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/47Add authoritative flag to Global Settings mechanism2023-11-07T21:39:56ZDarren AnkneyAdd authoritative flag to Global Settings mechanismThe authoritative flag may be important in some situations (especially an unfriendly environment such as a service provider network) so it is probably important to add this flag to the settings to make users aware of its existence.The authoritative flag may be important in some situations (especially an unfriendly environment such as a service provider network) so it is probably important to add this flag to the settings to make users aware of its existence.0.3Darren AnkneyDarren Ankneyhttps://gitlab.isc.org/isc-projects/kea-packaging/-/issues/19backport fixes to v2_42023-10-02T12:03:52ZWlodzimierz Wencelbackport fixes to v2_4Backport fixes included in:
* isc-projects/kea-packaging!52
* isc-projects/kea-packaging!50
* isc-projects/kea-packaging!45Backport fixes included in:
* isc-projects/kea-packaging!52
* isc-projects/kea-packaging!50
* isc-projects/kea-packaging!45Wlodzimierz WencelWlodzimierz Wencelhttps://gitlab.isc.org/isc-projects/kea-docker/-/issues/20migrate from root user to run kea in docker2023-09-25T10:53:07ZWlodzimierz Wencelmigrate from root user to run kea in dockerfor now kea services are executed by root, migrate to kea usersfor now kea services are executed by root, migrate to kea usersWlodzimierz WencelWlodzimierz Wencelhttps://gitlab.isc.org/isc-projects/keama/-/issues/50Remove unnecessary libraries and links to nonexistent ones2023-09-21T07:37:05ZMarcin GodzinaRemove unnecessary libraries and links to nonexistent oneshttps://gitlab.isc.org/isc-projects/keama/-/issues/39#note_403811
https://gitlab.isc.org/isc-projects/keama/-/issues/39#note_403703https://gitlab.isc.org/isc-projects/keama/-/issues/39#note_403811
https://gitlab.isc.org/isc-projects/keama/-/issues/39#note_4037034.5.1https://gitlab.isc.org/isc-projects/keama/-/issues/49remove unnecessary configure and build options2023-09-21T07:37:31ZMarcin Godzinaremove unnecessary configure and build optionshttps://gitlab.isc.org/isc-projects/keama/-/issues/39#note_403690https://gitlab.isc.org/isc-projects/keama/-/issues/39#note_4036904.5.1https://gitlab.isc.org/isc-projects/keama/-/issues/48Printing debug info to stderr was not a good idea.2023-09-21T07:38:42ZMarcin GodzinaPrinting debug info to stderr was not a good idea.Per Francis:
> keama emits some trace logs on stderr: this breaks error tests are logs are mixed with error messages. The easiest way to solve this is to add a command line flag to disable them.
https://gitlab.isc.org/isc-projects/keama...Per Francis:
> keama emits some trace logs on stderr: this breaks error tests are logs are mixed with error messages. The easiest way to solve this is to add a command line flag to disable them.
https://gitlab.isc.org/isc-projects/keama/-/issues/39#note_4038174.5.1https://gitlab.isc.org/isc-projects/keama-leases/-/issues/21Lease filename must be in the same directory2023-09-20T14:59:55ZAlessandro VeselyLease filename must be in the same directoryI keep git clones in a `source` directory, so I did the following:
```sh
ale@pcale:~/tmp$ cd source/
ale@pcale:~/tmp/source$ git clone https://gitlab.isc.org/isc-projects/keama-leases.git
Cloning into 'keama-leases'...
remote: Enumeratin...I keep git clones in a `source` directory, so I did the following:
```sh
ale@pcale:~/tmp$ cd source/
ale@pcale:~/tmp/source$ git clone https://gitlab.isc.org/isc-projects/keama-leases.git
Cloning into 'keama-leases'...
remote: Enumerating objects: 151, done.
remote: Total 151 (delta 0), reused 0 (delta 0), pack-reused 151
Receiving objects: 100% (151/151), 747.81 KiB | 2.22 MiB/s, done.
Resolving deltas: 100% (61/61), done.
ale@pcale:~/tmp/source$ python3 keama-leases/dhcp2kea/dhcp2kea.py ../dhcpd.leases
Traceback (most recent call last):
File "/home/ale/tmp/source/keama-leases/dhcp2kea/dhcp2kea.py", line 328, in <module>
with open(fname.replace('.','-')+"-kea.csv","w") as f:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '--/dhcpd-leases-kea.csv'
```
There's an easy workaround, so this is a minor issue. Thank you for a convenient tool.https://gitlab.isc.org/isc-projects/keama/-/issues/46Remove or rewrite Contributing.md2023-09-21T07:38:53ZMarcin GodzinaRemove or rewrite Contributing.mdhttps://gitlab.isc.org/isc-projects/keama/-/blob/master/CONTRIBUTING.md
This document references ISC-DHCP code and former employers.https://gitlab.isc.org/isc-projects/keama/-/blob/master/CONTRIBUTING.md
This document references ISC-DHCP code and former employers.4.5.1https://gitlab.isc.org/isc-projects/keama/-/issues/45Clean up, or mark as "do not use" legacy/broken tests2023-09-21T07:39:24ZMarcin GodzinaClean up, or mark as "do not use" legacy/broken testshttps://gitlab.isc.org/isc-projects/keama/-/issues/39#note_403622
https://gitlab.isc.org/isc-projects/keama/-/issues/39#note_403692https://gitlab.isc.org/isc-projects/keama/-/issues/39#note_403622
https://gitlab.isc.org/isc-projects/keama/-/issues/39#note_4036924.5.1