[Kea-users] dhcp4 server stops responding to a device
Gavin Davenport
gavdav at gavdav.net
Sun Jan 21 22:15:15 UTC 2024
Hi
Managed to increase verbosity on logs and also alter tcpdump to see the inbound stuff and the responses of the dhcp server.
What seems to happen is that the client seems to get stuck in a loop of
Dicover->Offer->Discover->Offer
(so kea is responding correctly to the discover)
But the client doesn’t go onto perform the request for the address. It’ll do this every 5 seconds & I don’t understand why.
fc:fe:c2:05:3e:b7 is the dhcping client and I give it a reservation for 19.99.99.3.
10.99.99.119 is the dhcp server.
Logged:
2024-01-21 20:18:18.835 DEBUG [kea-dhcp4.packets/282727.140679905825152] DHCP4_BUFFER_RECEIVED received buffer from 0.0.0.0:68 to 255.255.255.255:67 over interface enp2s0
2024-01-21 20:18:18.835 DEBUG [kea-dhcp4.options/282727.140679872231104] DHCP4_BUFFER_UNPACK parsing buffer received from 0.0.0.0 to 255.255.255.255 over interface enp2s0
2024-01-21 20:18:18.836 DEBUG [kea-dhcp4.dhcpsrv/282727.140679872231104] DHCPSRV_SUBNET4_SELECT_NO_RAI_OPTIONS No RAI options found to use for subnet selection.
2024-01-21 20:18:18.836 DEBUG [kea-dhcp4.dhcpsrv/282727.140679872231104] DHCPSRV_SUBNET4_SELECT_NO_RELAY_ADDRESS Relay address (giaddr) in client packet is empty.
2024-01-21 20:18:18.836 DEBUG [kea-dhcp4.dhcpsrv/282727.140679872231104] DHCPSRV_SUBNET4_SELECT_BY_INTERFACE_NO_MATCH No subnet matches interface: enp2s0
2024-01-21 20:18:18.836 DEBUG [kea-dhcp4.dhcpsrv/282727.140679872231104] DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.99.99.0/24 for packet received by matching address 10.99.99.119
2024-01-21 20:18:18.836 DEBUG [kea-dhcp4.packets/282727.140679872231104] DHCP4_SUBNET_SELECTED [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x873cbbf1: the subnet with ID 1 was selected for client assignments
2024-01-21 20:18:18.836 DEBUG [kea-dhcp4.packets/282727.140679872231104] DHCP4_PACKET_RECEIVED [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x873cbbf1: DHCPDISCOVER (type 1) received from 0.0.0.0 to 255.255.255.255 on interface enp2s0
2024-01-21 20:18:18.836 DEBUG [kea-dhcp4.dhcpsrv/282727.140679872231104] DHCPSRV_SUBNET4_SELECT_NO_RAI_OPTIONS No RAI options found to use for subnet selection.
2024-01-21 20:18:18.836 DEBUG [kea-dhcp4.dhcpsrv/282727.140679872231104] DHCPSRV_SUBNET4_SELECT_NO_RELAY_ADDRESS Relay address (giaddr) in client packet is empty.
2024-01-21 20:18:18.836 DEBUG [kea-dhcp4.dhcpsrv/282727.140679872231104] DHCPSRV_SUBNET4_SELECT_BY_INTERFACE_NO_MATCH No subnet matches interface: enp2s0
2024-01-21 20:18:18.836 DEBUG [kea-dhcp4.dhcpsrv/282727.140679872231104] DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.99.99.0/24 for packet received by matching address 10.99.99.119
2024-01-21 20:18:18.836 DEBUG [kea-dhcp4.packets/282727.140679872231104] DHCP4_SUBNET_SELECTED [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x873cbbf1: the subnet with ID 1 was selected for client assignments
2024-01-21 20:18:18.836 DEBUG [kea-dhcp4.hosts/282727.140679872231104] HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation for subnet id 1, identified by hwaddr=FCFEC2053EB7
2024-01-21 20:18:18.836 DEBUG [kea-dhcp4.hosts/282727.140679872231104] HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using identifier: hwaddr=FCFEC2053EB7
2024-01-21 20:18:18.836 DEBUG [kea-dhcp4.hosts/282727.140679872231104] HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=FCFEC2053EB7, found 1 host(s)
2024-01-21 20:18:18.837 DEBUG [kea-dhcp4.hosts/282727.140679872231104] HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_HOST using subnet id 1 and identifier hwaddr=FCFEC2053EB7, found host: hwaddr=FCFEC2053EB7 ipv4_subnet_id=1 hostname=(empty) ipv4_reservation=10.99.99.3 siaddr=(no) sname=(empty) file=(empty) key=(empty) ipv6_reservations=(none)
2024-01-21 20:18:18.837 DEBUG [kea-dhcp4.dhcp4/282727.140679872231104] DHCP4_CLASS_ASSIGNED [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x873cbbf1: client packet has been assigned to the following class(es): KNOWN
2024-01-21 20:18:18.837 DEBUG [kea-dhcp4.dhcp4/282727.140679872231104] DHCP4_CLASS_ASSIGNED [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x873cbbf1: client packet has been assigned to the following class(es): ALL, KNOWN
2024-01-21 20:18:18.837 DEBUG [kea-dhcp4.ddns/282727.140679872231104] DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x873cbbf1: processing client's Hostname option
2024-01-21 20:18:18.837 DEBUG [kea-dhcp4.dhcpsrv/282727.140679872231104] DHCPSRV_MEMFILE_GET_HWADDR obtaining IPv4 leases for hardware address hwtype=1 fc:fe:c2:05:3e:b7
2024-01-21 20:18:18.837 DEBUG [kea-dhcp4.alloc-engine/282727.140679872231104] ALLOC_ENGINE_V4_DISCOVER_HR client [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x873cbbf1 sending DHCPDISCOVER has reservation for the address 10.99.99.3
2024-01-21 20:18:18.837 INFO [kea-dhcp4.leases/282727.140679872231104] DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x873cbbf1: lease 10.99.99.3 will be advertised
2024-01-21 20:18:18.837 DEBUG [kea-dhcp4.options/282727.140679872231104] DHCP4_PACKET_PACK [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x873cbbf1: preparing on-wire format of the packet to be sent
2024-01-21 20:18:18.837 DEBUG [kea-dhcp4.packets/282727.140679872231104] DHCP4_PACKET_SEND [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x873cbbf1: trying to send packet DHCPOFFER (type 2) from 10.99.99.119:67 to 255.255.255.255:68 on interface enp2s0
2024-01-21 20:18:22.726 DEBUG [kea-dhcp4.packets/282727.140679905825152] DHCP4_BUFFER_RECEIVED received buffer from 0.0.0.0:68 to 255.255.255.255:67 over interface enp2s0
2024-01-21 20:18:22.726 DEBUG [kea-dhcp4.dhcpsrv/282727.140679905825152] DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer: reclaim-expired-leases
2024-01-21 20:18:22.726 DEBUG [kea-dhcp4.alloc-engine/282727.140679905825152] ALLOC_ENGINE_V4_LEASES_RECLAMATION_START starting reclamation of expired leases (limit = 100 leases or 250 milliseconds)
2024-01-21 20:18:22.726 DEBUG [kea-dhcp4.dhcpsrv/282727.140679905825152] DHCPSRV_MEMFILE_GET_EXPIRED4 obtaining maximum 101 of expired IPv4 leases
2024-01-21 20:18:22.726 DEBUG [kea-dhcp4.options/282727.140679863838400] DHCP4_BUFFER_UNPACK parsing buffer received from 0.0.0.0 to 255.255.255.255 over interface enp2s0
2024-01-21 20:18:22.726 DEBUG [kea-dhcp4.alloc-engine/282727.140679905825152] ALLOC_ENGINE_V4_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.081 ms
2024-01-21 20:18:22.726 DEBUG [kea-dhcp4.alloc-engine/282727.140679905825152] ALLOC_ENGINE_V4_NO_MORE_EXPIRED_LEASES all expired leases have been reclaimed
2024-01-21 20:18:22.726 DEBUG [kea-dhcp4.dhcpsrv/282727.140679863838400] DHCPSRV_SUBNET4_SELECT_NO_RAI_OPTIONS No RAI options found to use for subnet selection.
2024-01-21 20:18:22.726 DEBUG [kea-dhcp4.dhcpsrv/282727.140679905825152] DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.dhcpsrv/282727.140679863838400] DHCPSRV_SUBNET4_SELECT_NO_RELAY_ADDRESS Relay address (giaddr) in client packet is empty.
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.dhcpsrv/282727.140679863838400] DHCPSRV_SUBNET4_SELECT_BY_INTERFACE_NO_MATCH No subnet matches interface: enp2s0
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.dhcpsrv/282727.140679863838400] DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.99.99.0/24 for packet received by matching address 10.99.99.119
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.packets/282727.140679863838400] DHCP4_SUBNET_SELECTED [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: the subnet with ID 1 was selected for client assignments
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.packets/282727.140679863838400] DHCP4_PACKET_RECEIVED [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: DHCPDISCOVER (type 1) received from 0.0.0.0 to 255.255.255.255 on interface enp2s0
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.dhcpsrv/282727.140679863838400] DHCPSRV_SUBNET4_SELECT_NO_RAI_OPTIONS No RAI options found to use for subnet selection.
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.dhcpsrv/282727.140679863838400] DHCPSRV_SUBNET4_SELECT_NO_RELAY_ADDRESS Relay address (giaddr) in client packet is empty.
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.dhcpsrv/282727.140679863838400] DHCPSRV_SUBNET4_SELECT_BY_INTERFACE_NO_MATCH No subnet matches interface: enp2s0
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.dhcpsrv/282727.140679863838400] DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.99.99.0/24 for packet received by matching address 10.99.99.119
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.packets/282727.140679863838400] DHCP4_SUBNET_SELECTED [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: the subnet with ID 1 was selected for client assignments
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.hosts/282727.140679863838400] HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation for subnet id 1, identified by hwaddr=FCFEC2053EB7
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.hosts/282727.140679863838400] HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using identifier: hwaddr=FCFEC2053EB7
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.hosts/282727.140679863838400] HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=FCFEC2053EB7, found 1 host(s)
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.hosts/282727.140679863838400] HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_HOST using subnet id 1 and identifier hwaddr=FCFEC2053EB7, found host: hwaddr=FCFEC2053EB7 ipv4_subnet_id=1 hostname=(empty) ipv4_reservation=10.99.99.3 siaddr=(no) sname=(empty) file=(empty) key=(empty) ipv6_reservations=(none)
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.dhcp4/282727.140679863838400] DHCP4_CLASS_ASSIGNED [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: client packet has been assigned to the following class(es): KNOWN
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.dhcp4/282727.140679863838400] DHCP4_CLASS_ASSIGNED [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: client packet has been assigned to the following class(es): ALL, KNOWN
2024-01-21 20:18:22.727 DEBUG [kea-dhcp4.ddns/282727.140679863838400] DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: processing client's Hostname option
2024-01-21 20:18:22.728 DEBUG [kea-dhcp4.dhcpsrv/282727.140679863838400] DHCPSRV_MEMFILE_GET_HWADDR obtaining IPv4 leases for hardware address hwtype=1 fc:fe:c2:05:3e:b7
2024-01-21 20:18:22.728 DEBUG [kea-dhcp4.alloc-engine/282727.140679863838400] ALLOC_ENGINE_V4_DISCOVER_HR client [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475 sending DHCPDISCOVER has reservation for the address 10.99.99.3
2024-01-21 20:18:22.728 INFO [kea-dhcp4.leases/282727.140679863838400] DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: lease 10.99.99.3 will be advertised
2024-01-21 20:18:22.728 DEBUG [kea-dhcp4.options/282727.140679863838400] DHCP4_PACKET_PACK [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: preparing on-wire format of the packet to be sent
2024-01-21 20:18:22.728 DEBUG [kea-dhcp4.packets/282727.140679863838400] DHCP4_PACKET_SEND [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: trying to send packet DHCPOFFER (type 2) from 10.99.99.119:67 to 255.255.255.255:68 on interface enp2s0
2024-01-21 20:18:27.170 DEBUG [kea-dhcp4.packets/282727.140679905825152] DHCP4_BUFFER_RECEIVED received buffer from 0.0.0.0:68 to 255.255.255.255:67 over interface enp2s0
2024-01-21 20:18:27.170 DEBUG [kea-dhcp4.options/282727.140679847052992] DHCP4_BUFFER_UNPACK parsing buffer received from 0.0.0.0 to 255.255.255.255 over interface enp2s0
2024-01-21 20:18:27.170 DEBUG [kea-dhcp4.dhcpsrv/282727.140679847052992] DHCPSRV_SUBNET4_SELECT_NO_RAI_OPTIONS No RAI options found to use for subnet selection.
2024-01-21 20:18:27.170 DEBUG [kea-dhcp4.dhcpsrv/282727.140679847052992] DHCPSRV_SUBNET4_SELECT_NO_RELAY_ADDRESS Relay address (giaddr) in client packet is empty.
2024-01-21 20:18:27.170 DEBUG [kea-dhcp4.dhcpsrv/282727.140679847052992] DHCPSRV_SUBNET4_SELECT_BY_INTERFACE_NO_MATCH No subnet matches interface: enp2s0
2024-01-21 20:18:27.170 DEBUG [kea-dhcp4.dhcpsrv/282727.140679847052992] DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.99.99.0/24 for packet received by matching address 10.99.99.119
2024-01-21 20:18:27.170 DEBUG [kea-dhcp4.packets/282727.140679847052992] DHCP4_SUBNET_SELECTED [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: the subnet with ID 1 was selected for client assignments
2024-01-21 20:18:27.170 DEBUG [kea-dhcp4.packets/282727.140679847052992] DHCP4_PACKET_RECEIVED [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: DHCPDISCOVER (type 1) received from 0.0.0.0 to 255.255.255.255 on interface enp2s0
2024-01-21 20:18:27.171 DEBUG [kea-dhcp4.dhcpsrv/282727.140679847052992] DHCPSRV_SUBNET4_SELECT_NO_RAI_OPTIONS No RAI options found to use for subnet selection.
2024-01-21 20:18:27.171 DEBUG [kea-dhcp4.dhcpsrv/282727.140679847052992] DHCPSRV_SUBNET4_SELECT_NO_RELAY_ADDRESS Relay address (giaddr) in client packet is empty.
2024-01-21 20:18:27.171 DEBUG [kea-dhcp4.dhcpsrv/282727.140679847052992] DHCPSRV_SUBNET4_SELECT_BY_INTERFACE_NO_MATCH No subnet matches interface: enp2s0
2024-01-21 20:18:27.171 DEBUG [kea-dhcp4.dhcpsrv/282727.140679847052992] DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.99.99.0/24 for packet received by matching address 10.99.99.119
2024-01-21 20:18:27.171 DEBUG [kea-dhcp4.packets/282727.140679847052992] DHCP4_SUBNET_SELECTED [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: the subnet with ID 1 was selected for client assignments
2024-01-21 20:18:27.171 DEBUG [kea-dhcp4.hosts/282727.140679847052992] HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation for subnet id 1, identified by hwaddr=FCFEC2053EB7
2024-01-21 20:18:27.171 DEBUG [kea-dhcp4.hosts/282727.140679847052992] HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using identifier: hwaddr=FCFEC2053EB7
2024-01-21 20:18:27.171 DEBUG [kea-dhcp4.hosts/282727.140679847052992] HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=FCFEC2053EB7, found 1 host(s)
2024-01-21 20:18:27.171 DEBUG [kea-dhcp4.hosts/282727.140679847052992] HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_HOST using subnet id 1 and identifier hwaddr=FCFEC2053EB7, found host: hwaddr=FCFEC2053EB7 ipv4_subnet_id=1 hostname=(empty) ipv4_reservation=10.99.99.3 siaddr=(no) sname=(empty) file=(empty) key=(empty) ipv6_reservations=(none)
2024-01-21 20:18:27.171 DEBUG [kea-dhcp4.dhcp4/282727.140679847052992] DHCP4_CLASS_ASSIGNED [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: client packet has been assigned to the following class(es): KNOWN
2024-01-21 20:18:27.171 DEBUG [kea-dhcp4.dhcp4/282727.140679847052992] DHCP4_CLASS_ASSIGNED [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: client packet has been assigned to the following class(es): ALL, KNOWN
2024-01-21 20:18:27.171 DEBUG [kea-dhcp4.ddns/282727.140679847052992] DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: processing client's Hostname option
2024-01-21 20:18:27.171 DEBUG [kea-dhcp4.dhcpsrv/282727.140679847052992] DHCPSRV_MEMFILE_GET_HWADDR obtaining IPv4 leases for hardware address hwtype=1 fc:fe:c2:05:3e:b7
2024-01-21 20:18:27.171 DEBUG [kea-dhcp4.alloc-engine/282727.140679847052992] ALLOC_ENGINE_V4_DISCOVER_HR client [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475 sending DHCPDISCOVER has reservation for the address 10.99.99.3
2024-01-21 20:18:27.171 INFO [kea-dhcp4.leases/282727.140679847052992] DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: lease 10.99.99.3 will be advertised
2024-01-21 20:18:27.172 DEBUG [kea-dhcp4.options/282727.140679847052992] DHCP4_PACKET_PACK [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: preparing on-wire format of the packet to be sent
2024-01-21 20:18:27.172 DEBUG [kea-dhcp4.packets/282727.140679847052992] DHCP4_PACKET_SEND [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf12fb475: trying to send packet DHCPOFFER (type 2) from 10.99.99.119:67 to 255.255.255.255:68 on interface enp2s0
Corresponding packets from tcpdump:
20:18:18.835591 fc:fe:c2:05:3e:b7 > Broadcast, ethertype IPv4 (0x0800), length 342: (tos 0x0, ttl 64, id 14, offset 0, flags [none], proto UDP (17), length 328)
0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fc:fe:c2:05:3e:b7, length 300, xid 0x873cbbf1, secs 172, Flags [Broadcast]
Client-Ethernet-Address fc:fe:c2:05:3e:b7
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message (53), length 1: Discover
Hostname (12), length 15: "WiserHeat053EB7"
20:18:18.838005 90:2b:34:5f:ff:10 > Broadcast, ethertype IPv4 (0x0800), length 366: (tos 0x10, ttl 128, id 0, offset 0, flags [DF], proto UDP (17), length 352)
10.99.99.119.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 324, xid 0x873cbbf1, Flags [Broadcast]
Your-IP 10.99.99.3
Client-Ethernet-Address fc:fe:c2:05:3e:b7
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message (53), length 1: Offer
Subnet-Mask (1), length 4: 255.255.255.0
Default-Gateway (3), length 4: 10.99.99.1
Domain-Name-Server (6), length 8: 10.99.99.119,10.99.99.111
Hostname (12), length 15: "wiserheat053eb7"
Domain-Name (15), length 15: "ad.domain.net"
Lease-Time (51), length 4: 43200
Server-ID (54), length 4: 10.99.99.119
RN (58), length 4: 900
RB (59), length 4: 1800
20:18:22.726283 fc:fe:c2:05:3e:b7 > Broadcast, ethertype IPv4 (0x0800), length 342: (tos 0x0, ttl 64, id 1, offset 0, flags [none], proto UDP (17), length 328)
0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fc:fe:c2:05:3e:b7, length 300, xid 0xf12fb475, Flags [Broadcast]
Client-Ethernet-Address fc:fe:c2:05:3e:b7
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message (53), length 1: Discover
Hostname (12), length 15: "WiserHeat053EB7"
20:18:22.728499 90:2b:34:5f:ff:10 > Broadcast, ethertype IPv4 (0x0800), length 366: (tos 0x10, ttl 128, id 0, offset 0, flags [DF], proto UDP (17), length 352)
10.99.99.119.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 324, xid 0xf12fb475, Flags [Broadcast]
Your-IP 10.99.99.3
Client-Ethernet-Address fc:fe:c2:05:3e:b7
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message (53), length 1: Offer
Subnet-Mask (1), length 4: 255.255.255.0
Default-Gateway (3), length 4: 10.99.99.1
Domain-Name-Server (6), length 8: 10.99.99.119,10.99.99.111
Hostname (12), length 15: "wiserheat053eb7"
Domain-Name (15), length 15: "ad.domain.net"
Lease-Time (51), length 4: 43200
Server-ID (54), length 4: 10.99.99.119
RN (58), length 4: 900
RB (59), length 4: 1800
20:18:27.170230 fc:fe:c2:05:3e:b7 > Broadcast, ethertype IPv4 (0x0800), length 342: (tos 0x0, ttl 64, id 2, offset 0, flags [none], proto UDP (17), length 328)
0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fc:fe:c2:05:3e:b7, length 300, xid 0xf12fb475, secs 5, Flags [Broadcast]
Client-Ethernet-Address fc:fe:c2:05:3e:b7
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message (53), length 1: Discover
Hostname (12), length 15: "WiserHeat053EB7"
20:18:27.172248 90:2b:34:5f:ff:10 > Broadcast, ethertype IPv4 (0x0800), length 366: (tos 0x10, ttl 128, id 0, offset 0, flags [DF], proto UDP (17), length 352)
10.99.99.119.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 324, xid 0xf12fb475, Flags [Broadcast]
Your-IP 10.99.99.3
Client-Ethernet-Address fc:fe:c2:05:3e:b7
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message (53), length 1: Offer
Subnet-Mask (1), length 4: 255.255.255.0
Default-Gateway (3), length 4: 10.99.99.1
Domain-Name-Server (6), length 8: 10.99.99.119,10.99.99.111
Hostname (12), length 15: "wiserheat053eb7"
Domain-Name (15), length 15: "ad.domain.net"
Lease-Time (51), length 4: 43200
Server-ID (54), length 4: 10.99.99.119
RN (58), length 4: 900
RB (59), length 4: 1800
It’s very sporadic. Sometimes it refuses to get an address (having rebooted the router, restarted, dhcp, restarted the wireless access point), sometimes it’ll request and renew it’s address for hours and work fine.
I have splunk tracking the RSSI of the client, it’s not getting amazing signal but it should be sufficient. (-68 to -72 over last 2 hours)
Considering replacing the AP but there’s nothing wrong with the AP except distance to the Wiser device
From: Kea-users <kea-users-bounces at lists.isc.org> On Behalf Of Rick Frey
Sent: 21 January 2024 16:42
To: Kea user's list <kea-users at lists.isc.org>
Subject: Re: [Kea-users] dhcp4 server stops responding to a device
The listed Kea logs for DHCP_LEASE_ADVERT would indicate that Kea is sending an OFFER to the DISCOVER request. It would seem unlikely that Kea logs the ADVERT without attempting to send the offer packet on the network (such a bug would likely affect more than your client). You also mention that you had similar issue with the legacy ISC dhcpd server. You also mention recent issue began after distro upgrade. Assuming there were not changes to Kea with the upgrade.
Not enough info in thread to determine, but seems more probable that the OFFER is being dropped/blocked by your OS/network layer. Generally, if offer packet is blocked by something such as NFTables/IPTables, Kea would also log something along the lines of "failed to send DHCPv4 packet: pkt4 send failed: sendmsg() returned with an error: Operation not permitted”. Apparmor/SELinux or similar security controls could also be in play.
You may want to try packet capture without filters (or just limit to port 67/68) in case there are some breadcrumbs there. If you have not already, recommend checking OS logs as well in case response packet dropped by your host. You can also turn up Kea loglevel (severity DEBUG and increased debuglevel) but since Kea is logging ADVERT, not sure you’ll learn more there. See https://kea.readthedocs.io/en/kea-2.4.1/arm/logging.html#logging-levels
On Jan 19, 2024, at 07:37, Gavin Davenport <gavdav at gavdav.net<mailto:gavdav at gavdav.net>> wrote:
Does anyone have any idea why dhcp would not actually emit the dhcp response following logging
2024-01-19 13:35:02.390 INFO [kea-dhcp4.leases/855.139674733151936] DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf3db5a1f: lease 10.99.99.3 will be advertised
2024-01-19 13:35:17.539 INFO [kea-dhcp4.leases/855.139674758330048] DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf3db5a1f: lease 10.99.99.3 will be advertised
2024-01-19 13:35:32.689 INFO [kea-dhcp4.leases/855.139674749937344] DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xf3db5a1f: lease 10.99.99.3 will be advertised
It's received the discover (visible in tcpdump) but why would it get jammed and refuse to respond to this ?
is there anything I have misconfigured in the scope ? Are there any improved debugging options I might use ?
-----Original Message-----
From: Kea-users <kea-users-bounces at lists.isc.org<mailto:kea-users-bounces at lists.isc.org>> On Behalf Of Gavin Davenport
Sent: 16 January 2024 20:46
To: Kea user's list <kea-users at lists.isc.org<mailto:kea-users at lists.isc.org>>
Subject: Re: [Kea-users] dhcp4 server stops responding to a device
I was using isc-dhcp and had this behaviour too:
https://gitlab.isc.org/isc-projects/dhcp/-/issues/177
I switched to kea-dhcp4 and it fixed it.
I've since done a distro upgrade and it's gone flaky again.
I've no idea how to diagnose signal quality from the data I can get from the wiser (there's a rest endpoint) but this isn't available when it gets unaddressed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20240121/a90bf126/attachment-0001.htm>
More information about the Kea-users
mailing list