Skip to main content
Add information about wiresharking lo0 traffic
Source Link
{ "Dhcp4": { "valid-lifetime": 300, "interfaces-config": { "interfaces": [ "em0" ] }, "lease-database": { "type": "memfile", "persist": true, "name": "/var/lib/kea/dhcp4.leases" }, "subnet4": [ { "id": 1, "subnet": "192.168.0.0/24", "pools": [ { "pool": "192.168.0.100-192.168.0.254" } ], "option-data": [ { "name": "routers", "data": "192.168.0.1" } ], "reservations": [ { "hw-address": "dc:a6:32:12:2f:d2", "hostname": "dnsbox.voncorax.internal", "ip-address": "192.168.0.2" }, { "hw-address": "b8:ca:3a:7d:69:ad", "hostname": "prometheus.voncorax.internal", "ip-address": "192.168.0.98" } ] } ], "option-data": [ { "name": "domain-name-servers", "data": "192.168.0.97, 192.168.0.2" } ], "loggers": [ { "name": "kea-dhcp4", "output_options": [ { "output": "/var/log/kea-dhcp4.log" } ], "severity": "INFO", "debuglevel": 1 } ], "ddns-send-updates": true, "ddns-qualifying-suffix": "voncorax.internal", "ddns-override-no-update": true, "ddns-override-client-update": true, "dhcp-ddns": { "enable-updates": true, "server-ip": "127.0.0.1" } } } 
{ "Dhcp4": { "valid-lifetime": 300, "interfaces-config": { "interfaces": [ "em0" ] }, "lease-database": { "type": "memfile", "persist": true, "name": "/var/lib/kea/dhcp4.leases" }, "subnet4": [ { "id": 1, "subnet": "192.168.0.0/24", "pools": [ { "pool": "192.168.0.100-192.168.0.254" } ], "option-data": [ { "name": "routers", "data": "192.168.0.1" } ], "reservations": [ { "hw-address": "dc:a6:32:12:2f:d2", "hostname": "dnsbox.voncorax.internal", "ip-address": "192.168.0.2" }, { "hw-address": "b8:ca:3a:7d:69:ad", "hostname": "prometheus.voncorax.internal", "ip-address": "192.168.0.98" } ] } ], "option-data": [ { "name": "domain-name-servers", "data": "192.168.0.97, 192.168.0.2" } ], "loggers": [ { "name": "kea-dhcp4", "output_options": [ { "output": "/var/log/kea-dhcp4.log" } ], "severity": "INFO", "debuglevel": 1 } ], "ddns-send-updates": true, "ddns-qualifying-suffix": "voncorax.internal", "ddns-override-no-update": true, "ddns-override-client-update": true, "dhcp-ddns": { "enable-updates": true, "server-ip": "127.0.0.1" } } } 
{ "DhcpDdns": { "ip-address": "127.0.0.1", "port": 53001, "control-socket": { "socket-type": "unix", "socket-name": "/tmp/kea-ddns-ctrl-socket" }, "tsig-keys": [ { "name": "tsig-key", "algorithm": "hmac-sha256", "secret": "Shh! It's a secret!" } ], "forward-ddns" : { "ddns-domains": [ { "name": "voncorax.internal.", "key-name": "tsig-key", "dns-servers": [ { "ip-address": "192.168.0.97" } ] } ] }, "reverse-ddns" : { "ddns-domains": [ { "name": "0.168.192.in-addr.arpa.", "key-name": "tsig-key", "dns-servers": [ { "ip-address": "192.168.0.97" } ] } ] }, "loggers": [ { "name": "kea-dhcp-ddns", "output_options": [ { "output": "/var/log/kea-ddns.log" } ], "severity": "INFO", "debuglevel": 1 } ] } } 
{ "DhcpDdns": { "ip-address": "127.0.0.1", "port": 53001, "control-socket": { "socket-type": "unix", "socket-name": "/tmp/kea-ddns-ctrl-socket" }, "tsig-keys": [ { "name": "tsig-key", "algorithm": "hmac-sha256", "secret": "Shh! It's a secret!" } ], "forward-ddns" : { "ddns-domains": [ { "name": "voncorax.internal.", "key-name": "tsig-key", "dns-servers": [ { "ip-address": "192.168.0.97" } ] } ] }, "reverse-ddns" : { "ddns-domains": [ { "name": "0.168.192.in-addr.arpa.", "key-name": "tsig-key", "dns-servers": [ { "ip-address": "192.168.0.97" } ] } ] }, "loggers": [ { "name": "kea-dhcp-ddns", "output_options": [ { "output": "/var/log/kea-ddns.log" } ], "severity": "INFO", "debuglevel": 1 } ] } } 

This isn't an excerpt; that is literally the entirety of what's been logged since I restarted the daemon several days ago.

EDIT: I've hacked around with Wireshark a bit (from a Server Fault post) and it appears that kea-dhcp4 is not sending anything to kea-ddns over the lo0 interface. Can anyone suggest why not, or how I can figure out why not?

{ "Dhcp4": { "valid-lifetime": 300, "interfaces-config": { "interfaces": [ "em0" ] }, "lease-database": { "type": "memfile", "persist": true, "name": "/var/lib/kea/dhcp4.leases" }, "subnet4": [ { "id": 1, "subnet": "192.168.0.0/24", "pools": [ { "pool": "192.168.0.100-192.168.0.254" } ], "option-data": [ { "name": "routers", "data": "192.168.0.1" } ], "reservations": [ { "hw-address": "dc:a6:32:12:2f:d2", "hostname": "dnsbox.voncorax.internal", "ip-address": "192.168.0.2" }, { "hw-address": "b8:ca:3a:7d:69:ad", "hostname": "prometheus.voncorax.internal", "ip-address": "192.168.0.98" } ] } ], "option-data": [ { "name": "domain-name-servers", "data": "192.168.0.97, 192.168.0.2" } ], "loggers": [ { "name": "kea-dhcp4", "output_options": [ { "output": "/var/log/kea-dhcp4.log" } ], "severity": "INFO", "debuglevel": 1 } ], "ddns-send-updates": true, "ddns-qualifying-suffix": "voncorax.internal", "ddns-override-no-update": true, "ddns-override-client-update": true, "dhcp-ddns": { "enable-updates": true, "server-ip": "127.0.0.1" } } } 
{ "DhcpDdns": { "ip-address": "127.0.0.1", "port": 53001, "control-socket": { "socket-type": "unix", "socket-name": "/tmp/kea-ddns-ctrl-socket" }, "tsig-keys": [ { "name": "tsig-key", "algorithm": "hmac-sha256", "secret": "Shh! It's a secret!" } ], "forward-ddns" : { "ddns-domains": [ { "name": "voncorax.internal.", "key-name": "tsig-key", "dns-servers": [ { "ip-address": "192.168.0.97" } ] } ] }, "reverse-ddns" : { "ddns-domains": [ { "name": "0.168.192.in-addr.arpa.", "key-name": "tsig-key", "dns-servers": [ { "ip-address": "192.168.0.97" } ] } ] }, "loggers": [ { "name": "kea-dhcp-ddns", "output_options": [ { "output": "/var/log/kea-ddns.log" } ], "severity": "INFO", "debuglevel": 1 } ] } } 
{ "Dhcp4": { "valid-lifetime": 300, "interfaces-config": { "interfaces": [ "em0" ] }, "lease-database": { "type": "memfile", "persist": true, "name": "/var/lib/kea/dhcp4.leases" }, "subnet4": [ { "id": 1, "subnet": "192.168.0.0/24", "pools": [ { "pool": "192.168.0.100-192.168.0.254" } ], "option-data": [ { "name": "routers", "data": "192.168.0.1" } ], "reservations": [ { "hw-address": "dc:a6:32:12:2f:d2", "hostname": "dnsbox.voncorax.internal", "ip-address": "192.168.0.2" }, { "hw-address": "b8:ca:3a:7d:69:ad", "hostname": "prometheus.voncorax.internal", "ip-address": "192.168.0.98" } ] } ], "option-data": [ { "name": "domain-name-servers", "data": "192.168.0.97, 192.168.0.2" } ], "loggers": [ { "name": "kea-dhcp4", "output_options": [ { "output": "/var/log/kea-dhcp4.log" } ], "severity": "INFO", "debuglevel": 1 } ], "ddns-send-updates": true, "ddns-qualifying-suffix": "voncorax.internal", "ddns-override-no-update": true, "ddns-override-client-update": true, "dhcp-ddns": { "enable-updates": true, "server-ip": "127.0.0.1" } } } 
{ "DhcpDdns": { "ip-address": "127.0.0.1", "port": 53001, "control-socket": { "socket-type": "unix", "socket-name": "/tmp/kea-ddns-ctrl-socket" }, "tsig-keys": [ { "name": "tsig-key", "algorithm": "hmac-sha256", "secret": "Shh! It's a secret!" } ], "forward-ddns" : { "ddns-domains": [ { "name": "voncorax.internal.", "key-name": "tsig-key", "dns-servers": [ { "ip-address": "192.168.0.97" } ] } ] }, "reverse-ddns" : { "ddns-domains": [ { "name": "0.168.192.in-addr.arpa.", "key-name": "tsig-key", "dns-servers": [ { "ip-address": "192.168.0.97" } ] } ] }, "loggers": [ { "name": "kea-dhcp-ddns", "output_options": [ { "output": "/var/log/kea-ddns.log" } ], "severity": "INFO", "debuglevel": 1 } ] } } 

This isn't an excerpt; that is literally the entirety of what's been logged since I restarted the daemon several days ago.

EDIT: I've hacked around with Wireshark a bit (from a Server Fault post) and it appears that kea-dhcp4 is not sending anything to kea-ddns over the lo0 interface. Can anyone suggest why not, or how I can figure out why not?

Change logfile excerpt
Source Link

I won't post the entire log from kea-dhcp4 because it's huge, but it appears that dhcp4 is doing its thing correctly, just not talking to d2. The following is an excerpt from the output ofkea-dhcp4.log which appears grep ddns kea-dhcp4.log(to my inexperienced eye) to be all of a piece:

2024-05-28 1417:3925:0655.403169 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c12000] DHCP4_BUFFER_RECEIVED received buffer from 192.168.0.98:68 to 192.168.0.97:67 over interface em0 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.options/11509.0x1a25f9c15f00] DHCP4_BUFFER_UNPACK parsing buffer received from 192.168.0.98 to 192.168.0.97 over interface em0 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_PACKET_RECEIVED [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: DHCPREQUEST (type 3) received from 192.168.0.98 to 192.168.0.97 on interface em0 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_QUERY_DATA [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501, packet details: local_address=192.168.0.97:67, remote_address=192.168.0.98:68, msg_type=DHCPREQUEST (3), transid=0xd3f53501, options: type=012, len=010: "prometheus" (string) type=053, len=001: 3 (uint8) type=055, len=010: 1(uint8) 28(uint8) 2(uint8) 121(uint8) 3(uint8) 15(uint8) 6(uint8) 12(uint8) 119(uint8) 26(uint8) type=061, len=007: 01:b8:ca:3a:7d:69:ad 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_SUBNET4_SELECT_NO_RAI_OPTIONS No RAI options found to use for subnet selection. 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_SUBNET4_SELECT_NO_RELAY_ADDRESS Relay address (giaddr) in client packet is empty. 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 192.168.0.0/24 for packet received by matching address 192.168.0.98 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_SUBNET_SELECTED [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: the subnet with ID 1 was selected for client assignments 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_SUBNET_DATA [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: the selected subnet details: 192.168.0.0/24 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation for subnet id 1, identified by hwaddr=B8CA3A7D69AD 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using identifier: hwaddr=B8CA3A7D69AD 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_IDENTIFIER_HOST using identifier: hwaddr=B8CA3A7D69AD, found host: hwaddr=B8CA3A7D69AD ipv4_subnet_id=1 hostname=prometheus.voncorax.internal ipv4_reservation=192.168.0.98 siaddr=(no) sname=(empty) file=(empty) key=(empty) ipv6_reservations=(none) 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=B8CA3A7D69AD, found 1 host(s) 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_HOST using subnet id 1 and identifier hwaddr=B8CA3A7D69AD, found host: hwaddr=B8CA3A7D69AD ipv4_subnet_id=1 hostname=prometheus.voncorax.internal ipv4_reservation=192.168.0.98 siaddr=(no) sname=(empty) file=(empty) key=(empty) ipv6_reservations=(none) 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.dhcp4/11509.0x1a25f9c15f00] DHCP4_CLASS_ASSIGNED [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: client packet has been assigned to the following class(es): KNOWN 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.dhcp4/11509.0x1a25f9c15f00] DHCP4_CLASS_ASSIGNED [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: client packet has been assigned to the following class(es): ALL, KNOWN 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.ddns/11509.0x1a25f9c16600]0x1a25f9c15f00] DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 b8:ca:3a:7d:6469:00]ad], cid=[01:b8:ca:3a:7d:6469:00]ad], tid=0x8e83a985tid=0xd3f53501: processing client's Hostname option 2024-05-28 1417:3925:0655.403170 DEBUG [kea-dhcp4.ddns/11509.0x1a25f9c16600]0x1a25f9c15f00] DHCP4_CLIENT_HOSTNAME_DATA [hwtype=1 b8:ca:3a:7d:6469:00]ad], cid=[01:b8:ca:3a:7d:6469:00]ad], tid=0x8e83a985tid=0xd3f53501: client sent Hostname option: proteusprometheus 2024-05-28 1417:3925:0655.403170 DEBUG [kea-dhcp4.ddns/11509.0x1a25f9c16600]0x1a25f9c15f00] DHCP4_CLIENT_HOSTNAME_DATADHCP4_RESERVED_HOSTNAME_ASSIGNED [hwtype=1 b8:ca:3a:7d:6469:00]ad], cid=[01:b8:ca:3a:7d:6469:00]ad], tid=0x8e83a985tid=0xd3f53501: server assigned reserved hostname prometheus.voncorax.internal 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_MEMFILE_GET_CLIENTID obtaining IPv4 leases for client sentID Hostname01:b8:ca:3a:7d:69:ad 2024-05-28 option17:25:55.170 proteusDEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4 get one host with reservation for subnet id 1 and IPv4 address 192.168.0.98 2024-05-28 1417:3925:0655.403170 DEBUG [kea-dhcp4.ddnshosts/11509.0x1a25f9c16600]0x1a25f9c15f00] DHCP4_RESPONSE_HOSTNAME_DATAHOSTS_CFG_GET_ALL_ADDRESS4 get all hosts with reservations for IPv4 address 192.168.0.98 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_ADDRESS4_HOST using address 192.168.0.98 found host: hwaddr=B8CA3A7D69AD ipv4_subnet_id=1 hostname=prometheus.voncorax.internal ipv4_reservation=192.168.0.98 siaddr=(no) sname=(empty) file=(empty) key=(empty) ipv6_reservations=(none) 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_ADDRESS4_COUNT using address 192.168.0.98, found 1 host(s) 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4_HOST using subnet id 1 and address 192.168.0.98, found host: hwaddr=B8CA3A7D69AD ipv4_subnet_id=1 hostname=prometheus.voncorax.internal ipv4_reservation=192.168.0.98 siaddr=(no) sname=(empty) file=(empty) key=(empty) ipv6_reservations=(none) 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_MEMFILE_GET_ADDR4 obtaining IPv4 lease for address 192.168.0.98 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.alloc-engine/11509.0x1a25f9c15f00] ALLOC_ENGINE_V4_REQUEST_EXTEND_LEASE [hwtype=1 b8:ca:3a:7d:6469:00]ad], cid=[01:b8:ca:3a:7d:6469:00]ad], tid=0x8e83a985tid=0xd3f53501: includingextending Hostnamelifetime optionof inthe lease for address 192.168.0.98 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_MEMFILE_UPDATE_ADDR4 updating IPv4 lease for address 192.168.0.98 2024-05-28 17:25:55.170 INFO [kea-dhcp4.leases/11509.0x1a25f9c15f00] DHCP4_LEASE_ALLOC [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: lease 192.168.0.98 has been allocated for 300 seconds 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.options/11509.0x1a25f9c15f00] DHCP4_PACKET_PACK [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: preparing on-wire format of the server'spacket responseto be sent 2024-05-28 17:25:55.170 proteusDEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_PACKET_SEND [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: trying to send packet DHCPACK (type 5) from 192.168.0.97:67 to 192.168.0.98:68 on interface em0 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_RESPONSE_DATA [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: responding with packet DHCPACK (type 5), packet details: local_address=192.168.0.97:67, remote_address=192.168.0.98:68, msg_type=DHCPACK (5), transid=0xd3f53501, options: type=001, len=004: 4294967040 (uint32) type=003, len=004: 192.168.0.1 type=006, len=008: 192.168.0.97 192.168.0.2 type=012, len=028: "prometheus.voncorax.internalinternal" (string) type=051, len=004: 300 (uint32) type=053, len=001: 5 (uint8) type=054, len=004: 192.168.0.97 type=061, len=007: 01:b8:ca:3a:7d:69:ad 

I won't post the entire log from kea-dhcp4 because it's huge, but it appears that dhcp4 is doing its thing correctly, just not talking to d2. The following is an excerpt from the output of grep ddns kea-dhcp4.log:

2024-05-28 14:39:06.403 DEBUG [kea-dhcp4.ddns/11509.0x1a25f9c16600] DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 b8:ca:3a:7d:64:00], cid=[01:b8:ca:3a:7d:64:00], tid=0x8e83a985: processing client's Hostname option 2024-05-28 14:39:06.403 DEBUG [kea-dhcp4.ddns/11509.0x1a25f9c16600] DHCP4_CLIENT_HOSTNAME_DATA [hwtype=1 b8:ca:3a:7d:64:00], cid=[01:b8:ca:3a:7d:64:00], tid=0x8e83a985: client sent Hostname option: proteus 2024-05-28 14:39:06.403 DEBUG [kea-dhcp4.ddns/11509.0x1a25f9c16600] DHCP4_CLIENT_HOSTNAME_DATA [hwtype=1 b8:ca:3a:7d:64:00], cid=[01:b8:ca:3a:7d:64:00], tid=0x8e83a985: client sent Hostname option: proteus 2024-05-28 14:39:06.403 DEBUG [kea-dhcp4.ddns/11509.0x1a25f9c16600] DHCP4_RESPONSE_HOSTNAME_DATA [hwtype=1 b8:ca:3a:7d:64:00], cid=[01:b8:ca:3a:7d:64:00], tid=0x8e83a985: including Hostname option in the server's response: proteus.voncorax.internal 

I won't post the entire log from kea-dhcp4 because it's huge, but it appears that dhcp4 is doing its thing correctly, just not talking to d2. The following is an excerpt from kea-dhcp4.log which appears (to my inexperienced eye) to be all of a piece:

2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c12000] DHCP4_BUFFER_RECEIVED received buffer from 192.168.0.98:68 to 192.168.0.97:67 over interface em0 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.options/11509.0x1a25f9c15f00] DHCP4_BUFFER_UNPACK parsing buffer received from 192.168.0.98 to 192.168.0.97 over interface em0 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_PACKET_RECEIVED [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: DHCPREQUEST (type 3) received from 192.168.0.98 to 192.168.0.97 on interface em0 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_QUERY_DATA [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501, packet details: local_address=192.168.0.97:67, remote_address=192.168.0.98:68, msg_type=DHCPREQUEST (3), transid=0xd3f53501, options: type=012, len=010: "prometheus" (string) type=053, len=001: 3 (uint8) type=055, len=010: 1(uint8) 28(uint8) 2(uint8) 121(uint8) 3(uint8) 15(uint8) 6(uint8) 12(uint8) 119(uint8) 26(uint8) type=061, len=007: 01:b8:ca:3a:7d:69:ad 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_SUBNET4_SELECT_NO_RAI_OPTIONS No RAI options found to use for subnet selection. 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_SUBNET4_SELECT_NO_RELAY_ADDRESS Relay address (giaddr) in client packet is empty. 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 192.168.0.0/24 for packet received by matching address 192.168.0.98 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_SUBNET_SELECTED [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: the subnet with ID 1 was selected for client assignments 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_SUBNET_DATA [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: the selected subnet details: 192.168.0.0/24 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation for subnet id 1, identified by hwaddr=B8CA3A7D69AD 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using identifier: hwaddr=B8CA3A7D69AD 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_IDENTIFIER_HOST using identifier: hwaddr=B8CA3A7D69AD, found host: hwaddr=B8CA3A7D69AD ipv4_subnet_id=1 hostname=prometheus.voncorax.internal ipv4_reservation=192.168.0.98 siaddr=(no) sname=(empty) file=(empty) key=(empty) ipv6_reservations=(none) 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=B8CA3A7D69AD, found 1 host(s) 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_HOST using subnet id 1 and identifier hwaddr=B8CA3A7D69AD, found host: hwaddr=B8CA3A7D69AD ipv4_subnet_id=1 hostname=prometheus.voncorax.internal ipv4_reservation=192.168.0.98 siaddr=(no) sname=(empty) file=(empty) key=(empty) ipv6_reservations=(none) 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.dhcp4/11509.0x1a25f9c15f00] DHCP4_CLASS_ASSIGNED [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: client packet has been assigned to the following class(es): KNOWN 2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.dhcp4/11509.0x1a25f9c15f00] DHCP4_CLASS_ASSIGNED [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: client packet has been assigned to the following class(es): ALL, KNOWN 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.ddns/11509.0x1a25f9c15f00] DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: processing client's Hostname option 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.ddns/11509.0x1a25f9c15f00] DHCP4_CLIENT_HOSTNAME_DATA [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: client sent Hostname option: prometheus 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.ddns/11509.0x1a25f9c15f00] DHCP4_RESERVED_HOSTNAME_ASSIGNED [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: server assigned reserved hostname prometheus.voncorax.internal 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_MEMFILE_GET_CLIENTID obtaining IPv4 leases for client ID 01:b8:ca:3a:7d:69:ad 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4 get one host with reservation for subnet id 1 and IPv4 address 192.168.0.98 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_ADDRESS4 get all hosts with reservations for IPv4 address 192.168.0.98 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_ADDRESS4_HOST using address 192.168.0.98 found host: hwaddr=B8CA3A7D69AD ipv4_subnet_id=1 hostname=prometheus.voncorax.internal ipv4_reservation=192.168.0.98 siaddr=(no) sname=(empty) file=(empty) key=(empty) ipv6_reservations=(none) 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_ADDRESS4_COUNT using address 192.168.0.98, found 1 host(s) 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4_HOST using subnet id 1 and address 192.168.0.98, found host: hwaddr=B8CA3A7D69AD ipv4_subnet_id=1 hostname=prometheus.voncorax.internal ipv4_reservation=192.168.0.98 siaddr=(no) sname=(empty) file=(empty) key=(empty) ipv6_reservations=(none) 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_MEMFILE_GET_ADDR4 obtaining IPv4 lease for address 192.168.0.98 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.alloc-engine/11509.0x1a25f9c15f00] ALLOC_ENGINE_V4_REQUEST_EXTEND_LEASE [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: extending lifetime of the lease for address 192.168.0.98 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_MEMFILE_UPDATE_ADDR4 updating IPv4 lease for address 192.168.0.98 2024-05-28 17:25:55.170 INFO [kea-dhcp4.leases/11509.0x1a25f9c15f00] DHCP4_LEASE_ALLOC [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: lease 192.168.0.98 has been allocated for 300 seconds 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.options/11509.0x1a25f9c15f00] DHCP4_PACKET_PACK [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: preparing on-wire format of the packet to be sent 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_PACKET_SEND [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: trying to send packet DHCPACK (type 5) from 192.168.0.97:67 to 192.168.0.98:68 on interface em0 2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_RESPONSE_DATA [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: responding with packet DHCPACK (type 5), packet details: local_address=192.168.0.97:67, remote_address=192.168.0.98:68, msg_type=DHCPACK (5), transid=0xd3f53501, options: type=001, len=004: 4294967040 (uint32) type=003, len=004: 192.168.0.1 type=006, len=008: 192.168.0.97 192.168.0.2 type=012, len=028: "prometheus.voncorax.internal" (string) type=051, len=004: 300 (uint32) type=053, len=001: 5 (uint8) type=054, len=004: 192.168.0.97 type=061, len=007: 01:b8:ca:3a:7d:69:ad 
Fix incorrect logfile name
Source Link

I won't post the entire log from kea-dhcp4 because it's huge, but it appears that dhcp4 is doing its thing correctly, just not talking to d2. The following is an excerpt from the output of grep ddns kea-ddnsdhcp4.log:

I won't post the entire log from kea-dhcp4 because it's huge, but it appears that dhcp4 is doing its thing correctly, just not talking to d2. The following is an excerpt from the output of grep ddns kea-ddns.log:

I won't post the entire log from kea-dhcp4 because it's huge, but it appears that dhcp4 is doing its thing correctly, just not talking to d2. The following is an excerpt from the output of grep ddns kea-dhcp4.log:

Add logfile excerpts
Source Link
Loading
added 4781 characters in body
Source Link
Loading
Source Link
Loading