25.1.6_2 and 25.1.6_4 problem with Kea DHCPv4/DHCPv6 dual operation

Started by trdeal, May 11, 2025, 05:15:24 PM

Previous topic - Next topic
I have have two VLANs configured to seperate work traffic (myself and daughter) from home traffic. Currently I did have ISC DHCPv4 and DHCPv6 configured to supply both IPv4 and IPv6 traffic to work devices. After upgrading to 25.1.6_2 I performed a backup and then disabled ISC DHCPv4 and DHCPv6 and configured the same networks onto Kea DHCPv4 and DHCPv6. Initially with 25.1.6_2 I did managed to get an IPv4 and IPv6 address on my laptop but the lease did not appear. However after a power cycle the my laptop obtained an IPv4 and IPv6 address with both the IPv4 and IPv6 lease appearing; my daughter's laptop never obtained an IP address.
After upgrading to 25.1.6_4 I am able to obtain an IPv6 address but unable to obtain an IPv4 address, reverting to using ISC DHCP by restoring a backup IP addresses are always obtained.
If I power cycle 25.1.6_4 using the Kea backup, then my laptop does get IPv6 address immediately and then will get an IPv4 address, however only the IPv6 lease appears in Leases DHCPv6, nothing appears in Leases DHCPv4. If I restart the Kea DHCP service then I stop getting an IPv4 address and only obtain an IPv6 address

After checking the KEA Logs (informational) with 25.1.6_4, after a power cycle the logs show my laptop communicating with KEA and obtaining an IPv6 address then after a brief period it shows the laptop going through the DORA process and obtaining IPv4 address. After restarting the KEA Service and power cycling the laptop, the logs show an IPv6 address SARR process, however the IPv4 only completes DO or DORA, an DHCPOFFER is sent but there is never any response.
In respect of my daughter's connection, I connected a laptop to her network connection and could not get an IPv6 or IPv4 address checking the logs it shows that for IPv6 it completes SA of SARR and DO or DORA. In both cases I am using automated firewall rules, checking them manually they appear to be correct.
Both VLANs are connected to LAG interface connecting the 25.1.6_4 to my switch.
Restoring the ISC DHCP backup and with the attendant reboot, everything works as normal. So it is not a network issue, it appears to be directly related to ISC Kea.

Tried 25.1.7_2 with Kea DHCPv6 and DHCPv4 and now even from a reboot while my laptop does get an IPv6 address it fails to get an IPv4 address, looking at the Kea DHCPv4 information logs only the DO portion of the DORA process completes. Like before my daughter's laptop did not obtain an IP address (IPv4 or IPv6).

Upgraded to 25.1.7_4 and checked out Kea DHCP operation, my laptop can obtain an IPv6 address however if fails to get an IPv4 address.
Checking KEA's information logs 

2025-05-24T13:02:39 Informational kea-dhcp4 INFO [kea-dhcp4.packets.0x2b0007816d00] DHCP4_PACKET_SEND [hwtype=1 ab:ab:ab:ab:ab:ab], cid=[01:ab:ab:ab:ab:ab:ab], tid=0x4ae8d6a: trying to send packet DHCPOFFER (type 2) from 192.168.1.1:67 to 192.168.1.10:68 on interface lagg0_vlan2
2025-05-24T13:02:39 Informational kea-dhcp4 INFO [kea-dhcp4.leases.0x2b0007816d00] DHCP4_LEASE_OFFER [hwtype=1 ab:ab:ab:ab:ab:ab], cid=[01:ab:ab:ab:ab:ab:ab], tid=0x4ae8d6a: lease 192.168.1.10 will be offered
2025-05-24T13:02:39 Informational kea-dhcp4 INFO [kea-dhcp4.packets.0x2b0007816d00] DHCP4_PACKET_RECEIVED [hwtype=1 ab:ab:ab:ab:ab:ab], cid=[01:ab:ab:ab:ab:ab:ab], tid=0x4ae8d6a: DHCPDISCOVER (type 1) received from 0.0.0.0 to 255.255.255.255 on interface lagg0_vlan2
2025-05-24T13:02:39 Informational kea-dhcp4 INFO [kea-dhcp4.dhcp4.0x2b0007816d00] DHCP4_QUERY_LABEL received query: [hwtype=1 ab:ab:ab:ab:ab:ab], cid=[01:ab:ab:ab:ab:ab:ab], tid=0x4ae8d6a

So the logs are indicating its trying to send an DHCPOFFER and my laptop does not receive the offer, given that ISC DHCP works and the network has not changed. Would there be an issue with the automated Firewall rules.

The other thing I have noticed with Kea, is that DHCPv6 leases which have exceeded their expiry date are still being displayed.