HI Marek,
Here I am again and I'm afraid I'm probably going to rob you of your
sanity - I've probably already lost mine ...
Am 05.05.24 um 00:20 schrieb mxhajducze...@gmail.com:
PS. I am a tad confused about your mixes use of "" and '' in the config file.
Not sure whether it is formally supported.
O.K. So first of all, I used the last few days to read the documentation
at
https://kea.readthedocs.io/en/latest/arm/dhcp6-srv.html#dhcpv6-server-configuration
again and tried to understand it.
Here are a few framework values that may be relevant for further
consideration:
My host where's Kea running is an ArchLinux KVM based virtual machine:
root@vml000110:~# uname -a
Linux vml000110 6.6.30-2-lts #1 SMP PREEMPT_DYNAMIC Tue, 07 May 2024
21:45:29 +0000 x86_64 GNU/Linux
Here is the output of kea-dhcp6 -V :
root@vml000110:~# kea-dhcp6 -V
2.4.1
tarball
linked with:
log4cplus 2.1.0
OpenSSL 3.3.0 9 Apr 2024
database:
MySQL backend 19.0, library 3.3.9
PostgreSQL backend 18.0, library 160002
Memfile backend 5.0
This host has two network interfaces, eth0 and eth1. eth1 is where Kea
should listen for dhcp requests and offer.
root@vml000110:~# ip addr show eth1
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state
UP group default qlen 1000
link/ether 52:54:00:41:11:02 brd ff:ff:ff:ff:ff:ff
altname enp2s0
inet 10.0.10.110/24 brd 10.0.10.255 scope global eth1
valid_lft forever preferred_lft forever
inet6 2003:a:e0d:7607:10:0:10:110/64 scope global
valid_lft forever preferred_lft forever
inet6 fd00::7:10:0:0:110/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::7:10:ff:fe10:110/64 scope link
valid_lft forever preferred_lft forever
The firewall on the host is based on nftables and firewalld:
root@vml000110:~# firewall-cmd --zone=intra --list-all
intra (active)
target: default
ingress-priority: 0
egress-priority: 0
icmp-block-inversion: no
interfaces: eth1
sources:
services: dhcp dhcpv6 smtp ssh
ports:
protocols:
forward: no
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:
rule family="ipv6" source address="2003:a:e0d:7607::/64" service
name="ssh" accept
rule family="ipv6" source address="2003:a:e0d:7607::/64" destination
address="2003:a:e0d:7607:10:0:10:110/64" port port="123" protocol="udp"
accept
rule family="ipv4" source address="10.0.10.0/24" destination
address="10.0.10.110/32" port port="123" protocol="udp" accept
rule family="ipv6" source address="fd00::/10" destination
address="fd00::7:10:0:0:110/64" port port="123" protocol="udp" accept
rule family="ipv4" source address="10.0.10.0/24" service name="ssh"
accept
Following services are allowd: dhcp dhcpv6 smtp ssh
For testing purposes, I connected my laptop directly to the NIC of the
KVM host using a network cable. The laptop is assigned IPv4 addresses by
the kea-dhcp4 daemon and can also use this connection (IPv4), e.g. via
SSH (port 22) or SMTP (port 25).
root@vml000110:~# ss -tulpn
Netid State Recv-Q Send-Q
Local Address:Port
Peer Address:Port Process
udp UNCONN 0 0
10.0.10.110:67
0.0.0.0:*
users:(("kea-dhcp4",pid=1736,fd=17))
udp UNCONN 0 0
10.0.0.110:67
0.0.0.0:*
users:(("kea-dhcp4",pid=1736,fd=15))
So far so good, now we come to my <-redacted-> kea-dhcp6 problem ... :/
I have completely revised and rebuilt the DHCPv6 configuration file:
root@vml000110:~# cat /etc/kea/kea-dhcp6.conf
# This is our basic configuration for the Kea DHCPv6 server. See section
# 9.2 DHCPv6 Server Configuration for detailed informations.
#
# This configuration file contains only DHCPv6 server's configuration.
# If configurations for other Kea services are also included in this
# file they# are ignored by the DHCPv6 server.
{
# DHCPv6 configuration starts here. This section will be read by
# DHCPv6 server and will be ignored by other components.
"Dhcp6": {
# First we set up global values
# Global timers specified here apply to all subnets, unless there
# are subnet specific values defined in particular subnets. See
# section 9.2.1. Introduction.
"valid-lifetime": 4000,
"renew-timer": 1000,
"rebind-timer": 2000,
"preferred-lifetime": 3000,
# Kea supports control channel, which is a way to receive management
# commands while the server is running. For detailed description,
# see Sections 9.12, 16 and 15.
"control-socket": {
"socket-type": "unix",
"socket-name": "/var/lib/kea/kea6-ctrl-socket"
},
# Next we set up the interfaces to be used by the server.
# See section 9.2.4 Interface Configuration for more details.
"interfaces-config": {
"interfaces": [
"eth1/2003:a:e0d:7607:10:0:10:110"
]
},
# And we specify the type of lease database
# Use Memfile lease database backend to store leases in a CSV file.
# See Section 9.2.2.1 Memfile - Basic Storage for Leases
"lease-database": {
"type": "memfile",
"persist": true,
"name": "/var/lib/kea/kea-leases6.csv",
"lfc-interval": 1800,
"max-row-errors": 100
},
# Setup reclamation of the expired leases and leases affinity.
# See section 11. Lease Expiration for more and detailed
# informations.
"expired-leases-processing": {
"reclaim-timer-wait-time": 10,
"flush-reclaimed-timer-wait-time": 25,
"hold-reclaimed-time": 3600,
"max-reclaim-leases": 100,
"max-reclaim-time": 250,
"unwarned-reclaim-cycles": 5
},
# Many additional parameters can be specified here. Alle datails
# will be found in following sections:
# - 9.2.11. Standard DHCPv6 Options
# - 9.2.14. Custom DHCPv4 Options
# - 9.2.15. DHCPv6 Vendor-Specific Options
# - 9.2.16. Nested DHCPv6 Options (Custom Option Spaces)
# - 9.2.17. Unspecified Parameters for DHCPv6 Option Configuration
#
# For a complete list of options currently supported by Kea, see
# Section 9.2.11 "Standard DHCPv6 Options". Kea also supports
# vendor options (see Section 7.2.10) and allows users to define
# their own custom options (see Section 7.2.9).
"option-data": [
# Domain-Name-Server:
{
"name": "dns-servers",
"data": "2003:a:e0d:7607:10:0:10:110"
},
# Domain-Search-Liste:
{
"name": "domain-search",
"data": "edmz.nausch.org, idmz.nausch.org, intra.nausch.org"
}
],
# Finally, we list the subnets from which we will be leasing
# addresses. See section 9.2.5 IPv6 Subnet Identifier and the
# following sections for more details.
"subnet6": [
{
# This defines the whole subnet. Kea will use this information
# to determine where the clients are connected. This is the
# whole subnet in your network.
# Subnet identifier should be unique for each subnet.
"id": 7607,
# This is mandatory parameter for each subnet.
"subnet": "2003:a:e0d:7607::/64",
# Pools define the actual part of your subnet that is governed
# by Kea. Technically this is optional parameter, but it's
# almost always needed for DHCP to do its job. If you omit it,
# clients won't be able to get addresses, unless there are
# host reservations defined for them.
"pools": [ { "pool":
"2003:a:e0d:7607:10:0:10:1001-2003:a:e0d:7607:10:0:10:1fff" } ],
"option-data": [
# You can specify additional options here that are subnet
# specific. Also, you can override global options here.
{
"name": "dns-servers",
"data": "2003:a:e0d:7607:10:0:10:110"
}
],
# Host reservations can be defined for each subnet.
#
# Note that reservations are subnet-specific in Kea. This is
# different than ISC DHCP. Keep that in mind when migrating
# your configurations.
"reservations": [
# This is a simple host reservation. The host with DUID
# matching the specified value will get an address of
# 2003:a:e0d:7607::.
{
"duid": "01:02:03:04:05:0A:0B:0C:0D:0E",
"ip-addresses": [ "2003:a:e0d:7607:10:0:10:73" ]
},
# This is similar to the previous one, but this time the
# reservation is done based on hardware/MAC address. The
# server will do its best to extract the hardware/MAC
# address from received packets (see 'mac-sources'
# directive for details). This particular reservation
# also specifies two extra options to be available for
# this client. If there are options with the same code
# specified in a global, subnet or class scope, the
# values defined at host level take precedence.
{
"hw-address": "00:01:02:03:04:05",
"ip-addresses": [ "2003:a:e0d:7607:10:0:10:173" ]
}
]
}
],
# Logging configuration starts here. Kea uses different loggers to
# log various activities. For details (e.g. names of loggers), see
# Chapter 19.
"loggers": [
{
# This specifies the logging for kea-dhcp6 logger, i.e. all logs
# generated by Kea DHCPv6 server.
"name": "kea-dhcp6",
"output_options": [
{
# Specifies the output file. There are several special
# values supported:
# - stdout (prints on standard output)
# - stderr (prints on standard error)
# - syslog (logs to syslog)
# - syslog:name (logs to syslog using specified name)
# Any other value is considered a name of the file
"output": "/var/log/kea-dhcp6.log",
# Shorter log pattern suitable for use with systemd,
# avoids redundant information
# "pattern": "%-5p %m\n",
# This governs whether the log output is flushed to disk
# after every write.
# "flush": false,
# This specifies the maximum size of the file before it is
# rotated.
"maxsize": 1048576,
# This specifies the maximum number of rotated files to
# keep.
"maxver": 8
}
],
# This specifies the severity of log messages to keep. Supported
# values are: FATAL, ERROR, WARN, INFO, DEBUG
"severity": "DEBUG",
# If DEBUG level is specified, this value is used. 0 is least
# verbose, 99 is most verbose. Be cautious, Kea can generate
# lots and lots of logs if told to do so.
"debuglevel": 99
}
]
}
}
I would now boldly claim that the configuration is OK so far, or is it not?
If I check the configuration file syntax of my kea-dhcp6.conf file I can
see:
root@vml000110:~# kea-dhcp6 -t /etc/kea/kea-dhcp6.conf
2024-05-10 11:17:26.879 INFO [kea-dhcp6.hosts/1850.123272520762176]
HOSTS_BACKENDS_REGISTERED the following host backend types are
available: mysql postgresql
2024-05-10 11:17:26.879 WARN [kea-dhcp6.dhcpsrv/1850.123272520762176]
DHCPSRV_MT_DISABLED_QUEUE_CONTROL disabling dhcp queue control when
multi-threading is enabled.
2024-05-10 11:17:26.880 WARN [kea-dhcp6.dhcp6/1850.123272520762176]
DHCP6_RESERVATIONS_LOOKUP_FIRST_ENABLED Multi-threading is enabled and
host reservations lookup is always performed first.
2024-05-10 11:17:26.880 INFO [kea-dhcp6.dhcpsrv/1850.123272520762176]
DHCPSRV_CFGMGR_NEW_SUBNET6 a new subnet has been added to configuration:
2003:a:e0d:7607::/64 with params: t1=1000, t2=2000,
preferred-lifetime=3000, valid-lifetime=4000, rapid-commit is false
2024-05-10 11:17:26.880 INFO [kea-dhcp6.dhcpsrv/1850.123272520762176]
DHCPSRV_CFGMGR_SOCKET_TYPE_SELECT using socket type raw
2024-05-10 11:17:26.880 INFO [kea-dhcp6.dhcpsrv/1850.123272520762176]
DHCPSRV_CFGMGR_USE_UNICAST listening on unicast address
2003:a:e0d:7607:10:0:10:110, on interface eth1
Check the configuration file doing hooks load and extra checks shows:
root@vml000110:~# kea-dhcp6 -T /etc/kea/kea-dhcp6.conf
2024-05-10 11:18:52.117 INFO [kea-dhcp6.hosts/1855.129034817741632]
HOSTS_BACKENDS_REGISTERED the following host backend types are
available: mysql postgresql
2024-05-10 11:18:52.118 WARN [kea-dhcp6.dhcpsrv/1855.129034817741632]
DHCPSRV_MT_DISABLED_QUEUE_CONTROL disabling dhcp queue control when
multi-threading is enabled.
2024-05-10 11:18:52.118 WARN [kea-dhcp6.dhcp6/1855.129034817741632]
DHCP6_RESERVATIONS_LOOKUP_FIRST_ENABLED Multi-threading is enabled and
host reservations lookup is always performed first.
2024-05-10 11:18:52.118 INFO [kea-dhcp6.dhcpsrv/1855.129034817741632]
DHCPSRV_CFGMGR_NEW_SUBNET6 a new subnet has been added to configuration:
2003:a:e0d:7607::/64 with params: t1=1000, t2=2000,
preferred-lifetime=3000, valid-lifetime=4000, rapid-commit is false
2024-05-10 11:18:52.118 INFO [kea-dhcp6.dhcpsrv/1855.129034817741632]
DHCPSRV_MEMFILE_DB opening memory file lease database: lfc-interval=1800
max-row-errors=100 name=/var/lib/kea/kea-leases6.csv persist=true
type=memfile universe=6
2024-05-10 11:18:52.119 INFO [kea-dhcp6.dhcpsrv/1855.129034817741632]
DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file
/var/lib/kea/kea-leases6.csv.2
2024-05-10 11:18:52.119 INFO [kea-dhcp6.dhcpsrv/1855.129034817741632]
DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file
/var/lib/kea/kea-leases6.csv
2024-05-10 11:18:52.119 INFO [kea-dhcp6.dhcpsrv/1855.129034817741632]
DHCPSRV_MEMFILE_BUILD_EXTENDED_INFO_TABLES6 building extended info
tables saw 0 leases, extended info sanity checks modified 0 / updated 0
leases and 0 leases were entered into tables
2024-05-10 11:18:52.119 INFO [kea-dhcp6.dhcpsrv/1855.129034817741632]
DHCPSRV_MEMFILE_LFC_SETUP setting up the Lease File Cleanup interval to
1800 sec
2024-05-10 11:18:52.119 INFO [kea-dhcp6.dhcpsrv/1855.129034817741632]
DHCPSRV_CFGMGR_SOCKET_TYPE_SELECT using socket type raw
2024-05-10 11:18:52.119 INFO [kea-dhcp6.dhcpsrv/1855.129034817741632]
DHCPSRV_CFGMGR_USE_UNICAST listening on unicast address
2003:a:e0d:7607:10:0:10:110, on interface eth1
2024-05-10 11:18:52.119 INFO [kea-dhcp6.commands/1855.129034817741632]
COMMAND_ACCEPTOR_START Starting to accept connections via unix domain
socket bound to /var/lib/kea/kea6-ctrl-socket
Now let's start the kea-dhcp6 daemon with the help of systemd:
root@vml000110:~# systemctl start kea-dhcp6.service
The dhcp6-daemon is up and running:
root@vml000110:~# systemctl status kea-dhcp6.service -l
● kea-dhcp6.service - ISC Kea IPv6 DHCP daemon
Loaded: loaded (/usr/lib/systemd/system/kea-dhcp6.service;
disabled; preset: disabled)
Active: active (running) since Fri 2024-05-10 11:23:56 CEST; 10s ago
Docs: man:kea-dhcp6(8)
Main PID: 2003 (kea-dhcp6)
Tasks: 9 (limit: 9509)
Memory: 2.5M (peak: 3.5M)
CPU: 43ms
CGroup: /system.slice/kea-dhcp6.service
└─2003 /usr/bin/kea-dhcp6 -c /etc/kea/kea-dhcp6.conf
May 10 11:23:56 vml000110 systemd[1]: Started ISC Kea IPv6 DHCP daemon.
May 10 11:23:56 vml000110 kea-dhcp6[2003]: 2024-05-10 11:23:56.652 INFO
[kea-dhcp6.dhcp6/2003.127388013294400] DHCP6_STARTING Kea DHCPv6 server
version 2.4.1 (stable) starting
Logfile showing:
2024-05-10 11:23:56.654 DEBUG [kea-dhcp6.dhcp6/2003.127388013294400]
DHCP6_CONFIG_RECEIVED received configuration: { "control-socket": {
"socket-name": "/var/lib/kea/kea6-ctrl-socket", "socket-type": "unix" },
"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 }, "interfaces-config": { "interfaces": [
"eth1/2003:a:e0d:7607:10:0:10:110" ] }, "lease-database": {
"lfc-interval": 1800, "max-row-errors": 100, "name":
"/var/lib/kea/kea-leases6.csv", "persist": true, "type": "memfile" },
"loggers": [ { "debuglevel": 99, "name": "kea-dhcp6", "output_options":
[ { "maxsize": 1048576, "maxver": 8, "output": "/var/log/kea-dhcp6.log"
} ], "severity": "DEBUG" } ], "option-data": [ { "data":
"2003:a:e0d:7607:10:0:10:110", "name": "dns-servers" }, { "data":
"edmz.nausch.org, idmz.nausch.org, intra.nausch.org", "name":
"domain-search" } ], "preferred-lifetime": 3000, "rebind-timer": 2000,
"renew-timer": 1000, "subnet6": [ { "id": 7607, "option-data": [ {
"data": "2003:a:e0d:7607:10:0:10:110", "name": "dns-servers" } ],
"pools": [ { "pool":
"2003:a:e0d:7607:10:0:10:1001-2003:a:e0d:7607:10:0:10:1fff" } ],
"reservations": [ { "duid": "01:02:03:04:05:0A:0B:0C:0D:0E",
"ip-addresses": [ "2003:a:e0d:7607:10:0:10:73" ] }, { "hw-address":
"00:01:02:03:04:05", "ip-addresses": [ "2003:a:e0d:7607:10:0:10:173" ] }
], "subnet": "2003:a:e0d:7607::/64" } ], "valid-lifetime": 4000 }
2024-05-10 11:23:56.654 DEBUG [kea-dhcp6.dhcp6/2003.127388013294400]
DHCP6_CONFIG_START DHCPv6 server is processing the following
configuration: { "control-socket": { "socket-name":
"/var/lib/kea/kea6-ctrl-socket", "socket-type": "unix" },
"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 }, "interfaces-config": { "interfaces": [
"eth1/2003:a:e0d:7607:10:0:10:110" ] }, "lease-database": {
"lfc-interval": 1800, "max-row-errors": 100, "name":
"/var/lib/kea/kea-leases6.csv", "persist": true, "type": "memfile" },
"loggers": [ { "debuglevel": 99, "name": "kea-dhcp6", "output_options":
[ { "maxsize": 1048576, "maxver": 8, "output": "/var/log/kea-dhcp6.log"
} ], "severity": "DEBUG" } ], "option-data": [ { "data":
"2003:a:e0d:7607:10:0:10:110", "name": "dns-servers" }, { "data":
"edmz.nausch.org, idmz.nausch.org, intra.nausch.org", "name":
"domain-search" } ], "preferred-lifetime": 3000, "rebind-timer": 2000,
"renew-timer": 1000, "subnet6": [ { "id": 7607, "option-data": [ {
"data": "2003:a:e0d:7607:10:0:10:110", "name": "dns-servers" } ],
"pools": [ { "pool":
"2003:a:e0d:7607:10:0:10:1001-2003:a:e0d:7607:10:0:10:1fff" } ],
"reservations": [ { "duid": "01:02:03:04:05:0A:0B:0C:0D:0E",
"ip-addresses": [ "2003:a:e0d:7607:10:0:10:73" ] }, { "hw-address":
"00:01:02:03:04:05", "ip-addresses": [ "2003:a:e0d:7607:10:0:10:173" ] }
], "subnet": "2003:a:e0d:7607::/64" } ], "valid-lifetime": 4000 }
2024-05-10 11:23:56.654 INFO [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_BACKENDS_REGISTERED the following host backend types are
available: mysql postgresql
2024-05-10 11:23:56.655 WARN [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MT_DISABLED_QUEUE_CONTROL disabling dhcp queue control when
multi-threading is enabled.
2024-05-10 11:23:56.655 WARN [kea-dhcp6.dhcp6/2003.127388013294400]
DHCP6_RESERVATIONS_LOOKUP_FIRST_ENABLED Multi-threading is enabled and
host reservations lookup is always performed first.
2024-05-10 11:23:56.655 INFO [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_CFGMGR_NEW_SUBNET6 a new subnet has been added to configuration:
2003:a:e0d:7607::/64 with params: t1=1000, t2=2000,
preferred-lifetime=3000, valid-lifetime=4000, rapid-commit is false
2024-05-10 11:23:56.655 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_ADD_HOST add the host for reservations:
duid=01020304050A0B0C0D0E ipv6_subnet_id=7607 hostname=(empty)
ipv4_reservation=(no) siaddr=(no) sname=(empty) file=(empty) key=(empty)
ipv6_reservation0=2003:a:e0d:7607:10:0:10:73
2024-05-10 11:23:56.655 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv6
reservation for subnet id 7607, identified by duid=01020304050A0B0C0D0E
2024-05-10 11:23:56.655 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: duid=01020304050A0B0C0D0E
2024-05-10 11:23:56.655 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier
duid=01020304050A0B0C0D0E, found 0 host(s)
2024-05-10 11:23:56.655 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet
id 7607 and identifier duid=01020304050A0B0C0D0E
2024-05-10 11:23:56.655 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS6 get one host with reservation for
subnet id 7607 and having IPv6 address 2003:a:e0d:7607:10:0:10:73
2024-05-10 11:23:56.656 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS6 get all hosts with reservations for
subnet id 7607 and IPv6 address 2003:a:e0d:7607:10:0:10:73
2024-05-10 11:23:56.656 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS6_COUNT using subnet id 7607 and
address 2003:a:e0d:7607:10:0:10:73, found 0 host(s)
2024-05-10 11:23:56.656 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS6_NULL host not found using subnet id
7607 and address 2003:a:e0d:7607:10:0:10:73
2024-05-10 11:23:56.656 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_ADD_HOST add the host for reservations: hwaddr=000102030405
ipv6_subnet_id=7607 hostname=(empty) ipv4_reservation=(no) siaddr=(no)
sname=(empty) file=(empty) key=(empty)
ipv6_reservation0=2003:a:e0d:7607:10:0:10:173
2024-05-10 11:23:56.656 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv6
reservation for subnet id 7607, identified by hwaddr=000102030405
2024-05-10 11:23:56.656 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=000102030405
2024-05-10 11:23:56.656 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=000102030405,
found 0 host(s)
2024-05-10 11:23:56.656 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet
id 7607 and identifier hwaddr=000102030405
2024-05-10 11:23:56.656 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS6 get one host with reservation for
subnet id 7607 and having IPv6 address 2003:a:e0d:7607:10:0:10:173
2024-05-10 11:23:56.656 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS6 get all hosts with reservations for
subnet id 7607 and IPv6 address 2003:a:e0d:7607:10:0:10:173
2024-05-10 11:23:56.656 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS6_COUNT using subnet id 7607 and
address 2003:a:e0d:7607:10:0:10:173, found 0 host(s)
2024-05-10 11:23:56.656 DEBUG [kea-dhcp6.hosts/2003.127388013294400]
HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS6_NULL host not found using subnet id
7607 and address 2003:a:e0d:7607:10:0:10:173
2024-05-10 11:23:56.656 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_CFGMGR_ADD_SUBNET6 adding subnet 2003:a:e0d:7607::/64
2024-05-10 11:23:56.656 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_UNREGISTER_ALL_TIMERS unregistering all timers
2024-05-10 11:23:56.656 INFO [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_CFGMGR_SOCKET_TYPE_SELECT using socket type raw
2024-05-10 11:23:56.656 INFO [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_CFGMGR_USE_UNICAST listening on unicast address
2003:a:e0d:7607:10:0:10:110, on interface eth1
2024-05-10 11:23:56.656 INFO [kea-dhcp6.commands/2003.127388013294400]
COMMAND_ACCEPTOR_START Starting to accept connections via unix domain
socket bound to /var/lib/kea/kea6-ctrl-socket
2024-05-10 11:23:56.657 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_CFGMGR_CFG_DHCP_DDNS Setting DHCP-DDNS configuration to:
DHCP-DDNS updates disabled
2024-05-10 11:23:56.657 INFO [kea-dhcp6.dhcp6/2003.127388013294400]
DHCP6_CONFIG_COMPLETE DHCPv6 server has completed configuration: added
IPv6 subnets: 1; DDNS: disabled
2024-05-10 11:23:56.660 INFO [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_DB opening memory file lease database: lfc-interval=1800
max-row-errors=100 name=/var/lib/kea/kea-leases6.csv persist=true
type=memfile universe=6
2024-05-10 11:23:56.660 INFO [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file
/var/lib/kea/kea-leases6.csv.2
2024-05-10 11:23:56.660 INFO [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file
/var/lib/kea/kea-leases6.csv
2024-05-10 11:23:56.660 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_BEGIN_BUILD_EXTENDED_INFO_TABLES6 building extended info
tables with fix sanity check level, tables disabled
2024-05-10 11:23:56.660 INFO [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_BUILD_EXTENDED_INFO_TABLES6 building extended info
tables saw 0 leases, extended info sanity checks modified 0 / updated 0
leases and 0 leases were entered into tables
2024-05-10 11:23:56.660 INFO [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_LFC_SETUP setting up the Lease File Cleanup interval to
1800 sec
2024-05-10 11:23:56.660 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_REGISTER_TIMER registering timer: memfile-lfc, using
interval: 1800000 ms
2024-05-10 11:23:56.661 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_START_TIMER starting timer: memfile-lfc
2024-05-10 11:23:56.661 INFO [kea-dhcp6.dhcp6/2003.127388013294400]
DHCP6_USING_SERVERID server is using server-id
00:01:00:01:2d:c7:a3:0e:52:54:00:41:11:01 and stores in the file
/var/lib/kea/kea-dhcp6-serverid
2024-05-10 11:23:56.661 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_REGISTER_TIMER registering timer:
reclaim-expired-leases, using interval: 10000 ms
2024-05-10 11:23:56.661 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
2024-05-10 11:23:56.662 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_REGISTER_TIMER registering timer:
flush-reclaimed-leases, using interval: 25000 ms
2024-05-10 11:23:56.662 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_START_TIMER starting timer: flush-reclaimed-leases
2024-05-10 11:23:56.662 INFO [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_CFGMGR_USE_ALLOCATOR using the iterative allocator for IA_NA
leases in subnet 2003:a:e0d:7607::/64
2024-05-10 11:23:56.662 INFO [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_CFGMGR_USE_ALLOCATOR using the iterative allocator for IA_TA
leases in subnet 2003:a:e0d:7607::/64
2024-05-10 11:23:56.662 INFO [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_CFGMGR_USE_ALLOCATOR using the iterative allocator for IA_PD
leases in subnet 2003:a:e0d:7607::/64
2024-05-10 11:23:56.662 WARN [kea-dhcp6.dhcp6/2003.127388013294400]
DHCP6_MULTI_THREADING_INFO enabled: yes, number of threads: 4, queue
size: 64
2024-05-10 11:23:56.662 INFO [kea-dhcp6.dhcp6/2003.127388013294400]
DHCP6_STARTED Kea DHCPv6 server version 2.4.1 started
2024-05-10 11:24:06.674 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
reclaim-expired-leases
2024-05-10 11:24:06.674 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_START starting reclamation of expired
leases (limit = 100 leases or 250 milliseconds)
2024-05-10 11:24:06.674 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_GET_EXPIRED6 obtaining maximum 101 of expired IPv6 leases
2024-05-10 11:24:06.674 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.056 ms
2024-05-10 11:24:06.674 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_NO_MORE_EXPIRED_LEASES all expired leases have been
reclaimed
2024-05-10 11:24:06.674 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
2024-05-10 11:24:16.686 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
reclaim-expired-leases
2024-05-10 11:24:16.686 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_START starting reclamation of expired
leases (limit = 100 leases or 250 milliseconds)
2024-05-10 11:24:16.686 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_GET_EXPIRED6 obtaining maximum 101 of expired IPv6 leases
2024-05-10 11:24:16.686 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.052 ms
2024-05-10 11:24:16.686 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_NO_MORE_EXPIRED_LEASES all expired leases have been
reclaimed
2024-05-10 11:24:16.686 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
2024-05-10 11:24:21.692 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
flush-reclaimed-leases
2024-05-10 11:24:21.692 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_RECLAIMED_LEASES_DELETE begin deletion of reclaimed
leases expired more than 3600 seconds ago
2024-05-10 11:24:21.692 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_DELETE_EXPIRED_RECLAIMED6 deleting reclaimed IPv6 leases
that expired more than 3600 seconds ago
2024-05-10 11:24:21.692 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_RECLAIMED_LEASES_DELETE_COMPLETE successfully deleted 0
expired-reclaimed leases
2024-05-10 11:24:21.692 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_START_TIMER starting timer: flush-reclaimed-leases
2024-05-10 11:24:26.698 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
reclaim-expired-leases
2024-05-10 11:24:26.698 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_START starting reclamation of expired
leases (limit = 100 leases or 250 milliseconds)
2024-05-10 11:24:26.698 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_GET_EXPIRED6 obtaining maximum 101 of expired IPv6 leases
2024-05-10 11:24:26.698 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.055 ms
2024-05-10 11:24:26.698 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_NO_MORE_EXPIRED_LEASES all expired leases have been
reclaimed
2024-05-10 11:24:26.698 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
2024-05-10 11:24:36.709 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
reclaim-expired-leases
2024-05-10 11:24:36.709 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_START starting reclamation of expired
leases (limit = 100 leases or 250 milliseconds)
2024-05-10 11:24:36.710 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_GET_EXPIRED6 obtaining maximum 101 of expired IPv6 leases
2024-05-10 11:24:36.710 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.062 ms
2024-05-10 11:24:36.710 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_NO_MORE_EXPIRED_LEASES all expired leases have been
reclaimed
2024-05-10 11:24:36.710 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
2024-05-10 11:24:46.721 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
flush-reclaimed-leases
2024-05-10 11:24:46.721 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_RECLAIMED_LEASES_DELETE begin deletion of reclaimed
leases expired more than 3600 seconds ago
2024-05-10 11:24:46.721 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_DELETE_EXPIRED_RECLAIMED6 deleting reclaimed IPv6 leases
that expired more than 3600 seconds ago
2024-05-10 11:24:46.721 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_RECLAIMED_LEASES_DELETE_COMPLETE successfully deleted 0
expired-reclaimed leases
2024-05-10 11:24:46.721 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_START_TIMER starting timer: flush-reclaimed-leases
2024-05-10 11:24:46.721 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
reclaim-expired-leases
2024-05-10 11:24:46.721 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_START starting reclamation of expired
leases (limit = 100 leases or 250 milliseconds)
2024-05-10 11:24:46.721 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_GET_EXPIRED6 obtaining maximum 101 of expired IPv6 leases
2024-05-10 11:24:46.721 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.024 ms
2024-05-10 11:24:46.721 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_NO_MORE_EXPIRED_LEASES all expired leases have been
reclaimed
2024-05-10 11:24:46.721 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
2024-05-10 11:24:56.733 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
reclaim-expired-leases
2024-05-10 11:24:56.733 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_START starting reclamation of expired
leases (limit = 100 leases or 250 milliseconds)
2024-05-10 11:24:56.733 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_GET_EXPIRED6 obtaining maximum 101 of expired IPv6 leases
2024-05-10 11:24:56.733 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.051 ms
2024-05-10 11:24:56.733 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_NO_MORE_EXPIRED_LEASES all expired leases have been
reclaimed
2024-05-10 11:24:56.733 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
2024-05-10 11:25:06.744 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
reclaim-expired-leases
2024-05-10 11:25:06.745 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_START starting reclamation of expired
leases (limit = 100 leases or 250 milliseconds)
2024-05-10 11:25:06.745 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_GET_EXPIRED6 obtaining maximum 101 of expired IPv6 leases
2024-05-10 11:25:06.745 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.051 ms
2024-05-10 11:25:06.745 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_NO_MORE_EXPIRED_LEASES all expired leases have been
reclaimed
2024-05-10 11:25:06.745 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
Following ports are open:
root@vml000110:~# ss -tulpn
Netid State Recv-Q Send-Q
Local Address:Port
Peer Address:Port Process
udp UNCONN 0 0
10.0.10.110:67
0.0.0.0:*
users:(("kea-dhcp4",pid=1736,fd=17))
udp UNCONN 0 0
10.0.0.110:67
0.0.0.0:*
users:(("kea-dhcp4",pid=1736,fd=15))
udp UNCONN 0 0
0.0.0.0:123
0.0.0.0:*
users:(("chronyd",pid=496,fd=8))
udp UNCONN 0 0
127.0.0.1:323
0.0.0.0:*
users:(("chronyd",pid=496,fd=5))
udp UNCONN 0 0
[::]:123
[::]:*
users:(("chronyd",pid=496,fd=7))
udp UNCONN 0 0
[::1]:323
[::]:*
users:(("chronyd",pid=496,fd=6))
udp UNCONN 0 0
[2003:a:e0d:7607:10:0:10:110]:547
[::]:*
users:(("kea-dhcp6",pid=2003,fd=15))
udp UNCONN 0 0
[fe80::7:10:ff:fe10:110]%eth1:547
[::]:*
users:(("kea-dhcp6",pid=2003,fd=16))
udp UNCONN 0 0
[ff02::1:2]%eth1:547
[::]:*
users:(("kea-dhcp6",pid=2003,fd=17))
tcp LISTEN 0 128
0.0.0.0:22
0.0.0.0:*
users:(("sshd",pid=518,fd=3))
tcp LISTEN 0 128
[::]:22
[::]:* users:(("sshd",pid=518,fd=4))
Now it's getting exciting, I'm watching the log file of the kea-dhcp6
daemon in a shell window and in another window I'm trying to find out
what's happening on the network interface eth1 with regard to IPv6.
Here is the output of the logfile of kea-dhcp6:
2024-05-10 11:28:06.956 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
flush-reclaimed-leases
2024-05-10 11:28:06.956 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_RECLAIMED_LEASES_DELETE begin deletion of reclaimed
leases expired more than 3600 seconds ago
2024-05-10 11:28:06.957 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_DELETE_EXPIRED_RECLAIMED6 deleting reclaimed IPv6 leases
that expired more than 3600 seconds ago
2024-05-10 11:28:06.957 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_RECLAIMED_LEASES_DELETE_COMPLETE successfully deleted 0
expired-reclaimed leases
2024-05-10 11:28:06.957 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_START_TIMER starting timer: flush-reclaimed-leases
2024-05-10 11:28:06.957 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
reclaim-expired-leases
2024-05-10 11:28:06.957 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_START starting reclamation of expired
leases (limit = 100 leases or 250 milliseconds)
2024-05-10 11:28:06.957 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_GET_EXPIRED6 obtaining maximum 101 of expired IPv6 leases
2024-05-10 11:28:06.957 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.067 ms
2024-05-10 11:28:06.957 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_NO_MORE_EXPIRED_LEASES all expired leases have been
reclaimed
2024-05-10 11:28:06.957 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
2024-05-10 11:28:16.968 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
reclaim-expired-leases
2024-05-10 11:28:16.969 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_START starting reclamation of expired
leases (limit = 100 leases or 250 milliseconds)
2024-05-10 11:28:16.969 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_MEMFILE_GET_EXPIRED6 obtaining maximum 101 of expired IPv6 leases
2024-05-10 11:28:16.969 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.077 ms
2024-05-10 11:28:16.969 DEBUG
[kea-dhcp6.alloc-engine/2003.127388013294400]
ALLOC_ENGINE_V6_NO_MORE_EXPIRED_LEASES all expired leases have been
reclaimed
2024-05-10 11:28:16.969 DEBUG [kea-dhcp6.dhcpsrv/2003.127388013294400]
DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
And here is the output of tcpdump:
root@vml000110:/var/log# tcpdump -v -i eth1 | grep IP6
tcpdump: listening on eth1, link-type EN10MB (Ethernet), snapshot length
262144 bytes
11:28:04.155993 IP6 (hlim 1, next-header Options (0) payload length: 56)
:: > ff02::16: HBH (rtalert: 0x0000) (padn) [icmp6 sum ok] ICMP6,
multicast listener report v2, 2 group record(s) [gaddr ff02::1:ff44:b000
to_ex, 0 source(s)] [gaddr ff02::fb to_ex, 0 source(s)]
11:28:05.036133 IP6 (hlim 255, next-header ICMPv6 (58) payload length:
32) :: > ff02::1:ff44:b000: [icmp6 sum ok] ICMP6, neighbor solicitation,
length 32, who has fe80::e9a6:bb03:1544:b000
11:28:05.068155 IP6 (hlim 1, next-header Options (0) payload length: 56)
:: > ff02::16: HBH (rtalert: 0x0000) (padn) [icmp6 sum ok] ICMP6,
multicast listener report v2, 2 group record(s) [gaddr ff02::1:ff44:b000
to_ex, 0 source(s)] [gaddr ff02::fb to_ex, 0 source(s)]
11:28:06.060325 IP6 (hlim 1, next-header Options (0) payload length: 56)
fe80::e9a6:bb03:1544:b000 > ff02::16: HBH (rtalert: 0x0000) (padn)
[icmp6 sum ok] ICMP6, multicast listener report v2, 2 group record(s)
[gaddr ff02::1:ff44:b000 to_ex, 0 source(s)] [gaddr ff02::fb to_ex, 0
source(s)]
11:28:06.182053 IP6 (flowlabel 0xf2caa, hlim 255, next-header UDP (17)
payload length: 148) fe80::e9a6:bb03:1544:b000.mdns > ff02::fb.mdns:
[udp sum ok] 0*- [0q] 2/0/0
0.0.0.b.4.4.5.1.3.0.b.b.6.a.9.e.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa.
(Cache flush) PTR nitropad.local., nitropad.local. (Cache flush) AAAA
fe80::e9a6:bb03:1544:b000 (140)
11:28:06.236151 IP6 (flowlabel 0x05605, hlim 255, next-header ICMPv6
(58) payload length: 8) fe80::e9a6:bb03:1544:b000 > ff02::2: [icmp6 sum
ok] ICMP6, router solicitation, length 8
11:28:06.292177 IP6 (hlim 1, next-header Options (0) payload length: 56)
fe80::e9a6:bb03:1544:b000 > ff02::16: HBH (rtalert: 0x0000) (padn)
[icmp6 sum ok] ICMP6, multicast listener report v2, 2 group record(s)
[gaddr ff02::1:ff44:b000 to_ex, 0 source(s)] [gaddr ff02::fb to_ex, 0
source(s)]
11:28:07.241431 IP6 (flowlabel 0xf2caa, hlim 255, next-header UDP (17)
payload length: 149) fe80::e9a6:bb03:1544:b000.mdns > ff02::fb.mdns:
[udp sum ok] 0 [9q] PTR (QM)? _ipps._tcp.local. PTR (QM)?
_ftp._tcp.local. PTR (QM)? _webdav._tcp.local. PTR (QM)?
_webdavs._tcp.local. PTR (QM)? _sftp-ssh._tcp.local. PTR (QM)?
_smb._tcp.local. PTR (QM)? _afpovertcp._tcp.local. PTR (QM)?
_nfs._tcp.local. PTR (QM)? _ipp._tcp.local. (141)
11:28:08.323873 IP6 (flowlabel 0xf2caa, hlim 255, next-header UDP (17)
payload length: 148) fe80::e9a6:bb03:1544:b000.mdns > ff02::fb.mdns:
[udp sum ok] 0*- [0q] 2/0/0
0.0.0.b.4.4.5.1.3.0.b.b.6.a.9.e.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa.
(Cache flush) PTR nitropad.local., nitropad.local. (Cache flush) AAAA
fe80::e9a6:bb03:1544:b000 (140)
11:28:09.959337 IP6 (flowlabel 0x05605, hlim 255, next-header ICMPv6
(58) payload length: 8) fe80::e9a6:bb03:1544:b000 > ff02::2: [icmp6 sum
ok] ICMP6, router solicitation, length 8
11:28:11.244406 IP6 (flowlabel 0xf2caa, hlim 255, next-header UDP (17)
payload length: 149) fe80::e9a6:bb03:1544:b000.mdns > ff02::fb.mdns:
[udp sum ok] 0 [9q] PTR (QM)? _ipps._tcp.local. PTR (QM)?
_ftp._tcp.local. PTR (QM)? _webdav._tcp.local. PTR (QM)?
_webdavs._tcp.local. PTR (QM)? _sftp-ssh._tcp.local. PTR (QM)?
_smb._tcp.local. PTR (QM)? _afpovertcp._tcp.local. PTR (QM)?
_nfs._tcp.local. PTR (QM)? _ipp._tcp.local. (141)
^C111 packets captured
111 packets received by filter
0 packets dropped by kernel
fe80::e9a6:bb03:1544:b000 is the the link local address of the network
card of my laptop!
So Marek, I confess that I have absolutely no idea what is going wrong
here. What is going on here? Why does the kea-dhcp6 daemon not seem to
receive, understand or process any requests? I only get the IPv4 address
assigned on the connected laptop, but as far as IPv6 is concerned, it's
absolutely dead!
I hope you have a crucial tip in store that will help me!
ttyl
Django
--
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
Kea-users mailing list
Kea-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/kea-users
