Kea leases tab empty - 24.1.r_3

[ronin3510]

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

• I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
• I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug

The leases tab in Kea stays empty even though leases are distributed when requested.

To Reproduce

Steps to reproduce the behavior:

1. Go to ISC - DHCPv4 and disable it on LAN - Save changes
2. Click on Kea, enable service and select LAN interface
3. Set up a subnet 192.168.11.0/24 with a Pool 192.168.11.2 - 192.168.11.254 and a GW 192.168.11.1
4. Save changes - restart Kea
5. ipconfig /renew generates logs but the Leases tab stays empty

2024-01-13T06:24:01 Informational kea-dhcp4 INFO [kea-dhcp4.leases.0x8343c7000] DHCP4_LEASE_ALLOC [hwtype=1 1c:6f:65:81:c3:25], cid=[01:1c:6f:65:81:c3:25], tid=0xadce238f: lease 192.168.11.103 has been allocated for 4000 seconds 2024-01-13T06:22:54 Informational kea-dhcp4 INFO [kea-dhcp4.dhcp4.0x834268000] DHCP4_DYNAMIC_RECONFIGURATION_SUCCESS dynamic server reconfiguration succeeded with file: /usr/local/etc/kea/kea-dhcp4.conf 2024-01-13T06:22:54 Warning kea-dhcp4 WARN [kea-dhcp4.dhcp4.0x834268000] DHCP4_MULTI_THREADING_INFO enabled: yes, number of threads: 4, queue size: 64 2024-01-13T06:22:54 Informational kea-dhcp4 INFO [kea-dhcp4.dhcpsrv.0x834268000] DHCPSRV_CFGMGR_USE_ALLOCATOR using the iterative allocator for V4 leases in subnet 192.168.11.0/24 2024-01-13T06:22:54 Informational kea-dhcp4 INFO [kea-dhcp4.dhcpsrv.0x834268000] DHCPSRV_MEMFILE_LFC_SETUP setting up the Lease File Cleanup interval to 3600 sec 2024-01-13T06:22:54 Informational kea-dhcp4 INFO [kea-dhcp4.dhcpsrv.0x834268000] DHCPSRV_MEMFILE_EXTRACT_EXTENDED_INFO4 extracting extended info saw 4 leases, extended info sanity checks modified 0 / updated 0 leases and 0 leases have relay or remote id 2024-01-13T06:22:54 Informational kea-dhcp4 INFO [kea-dhcp4.dhcpsrv.0x834268000] DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file /var/db/kea/kea-leases4.csv 2024-01-13T06:22:54 Informational kea-dhcp4 INFO [kea-dhcp4.dhcpsrv.0x834268000] DHCPSRV_MEMFILE_DB opening memory file lease database: persist=true type=memfile universe=4 2024-01-13T06:22:54 Informational kea-dhcp4 INFO [kea-dhcp4.dhcp4.0x834268000] DHCP4_CONFIG_COMPLETE DHCPv4 server has completed configuration: added IPv4 subnets: 1; DDNS: disabled 2024-01-13T06:22:54 Informational kea-dhcp4 INFO [kea-dhcp4.dhcpsrv.0x834268000] DHCPSRV_CFGMGR_SOCKET_TYPE_DEFAULT "dhcp-socket-type" not specified , using default socket type raw 2024-01-13T06:22:54 Informational kea-dhcp4 INFO [kea-dhcp4.dhcpsrv.0x834268000] DHCPSRV_CFGMGR_ADD_IFACE listening on interface igc1 2024-01-13T06:22:54 Informational kea-dhcp4 INFO [kea-dhcp4.dhcpsrv.0x834268000] DHCPSRV_CFGMGR_SOCKET_TYPE_SELECT using socket type raw 2024-01-13T06:22:54 Informational kea-dhcp4 INFO [kea-dhcp4.dhcpsrv.0x834268000] DHCPSRV_CFGMGR_NEW_SUBNET4 a new subnet has been added to configuration: 192.168.11.0/24 with params: valid-lifetime=4000 2024-01-13T06:22:54 Warning kea-dhcp4 WARN [kea-dhcp4.dhcp4.0x834268000] DHCP4_RESERVATIONS_LOOKUP_FIRST_ENABLED Multi-threading is enabled and host reservations lookup is always performed first. 2024-01-13T06:22:54 Warning kea-dhcp4 WARN [kea-dhcp4.dhcpsrv.0x834268000] DHCPSRV_MT_DISABLED_QUEUE_CONTROL disabling dhcp queue control when multi-threading is enabled. 2024-01-13T06:22:54 Informational kea-dhcp4 INFO [kea-dhcp4.hosts.0x834268000] HOSTS_BACKENDS_REGISTERED the following host backend types are available: 2024-01-13T06:22:54 Warning kea-dhcp4 WARN [kea-dhcp4.dhcp4.0x834268000] DHCP4_CONFIG_SYNTAX_WARNING configuration syntax warning: /usr/local/etc/kea/kea-dhcp4.conf:50.10: Extraneous comma. A piece of configuration may have been omitted. 2024-01-13T06:22:54 Informational kea-dhcp4 INFO [kea-dhcp4.dhcp4.0x834268000] DHCP4_DYNAMIC_RECONFIGURATION initiate server reconfiguration using file: /usr/local/etc/kea/kea-dhcp4.conf, after receiving SIGHUP signal or config-reload command 2024-01-13T06:22:15 Informational kea-dhcp4 INFO [kea-dhcp4.leases.0x83426cd00] DHCP4_LEASE_ALLOC [hwtype=1 4a:85:c7:12:a9:d7], cid=[01:4a:85:c7:12:a9:d7], tid=0x16119f77: lease 192.168.11.2 has been allocate

Expected behavior

A clear and concise description of what you expected to happen.

Describe alternatives you considered

I first started using Kea when in landed 23.7 snapshot, went through the same steps and the leases were visible. Now both that VM and the 2 FWs I worked on today are affected by this issue.

Screenshots
n/a

Relevant log files
n/a
Additional context
The two physiical FWs are on R_3 and the vm set up a while ago on R_2 it is on -snapshot

Environment

Software version used and hardware type if relevant, e.g.:

OPNsense 24.1.r_3 (amd64).

[AdSchellevis]

probably this 415f53c , accidentally left some local test data in the last commit.

[ronin3510]

Thank you Ad, it looks good now with the patch.

One more oddity I noticed: If I disconnect a VM briefly to trigger dhcp client ( and no randomized MAC ) I end up with duplicate entries in the leases tab. The IP is preserved as expected but the lease is renewed instead of using the existing one - hence the duplication I think.

A trash button facility would also be helpful in cleaning up old leases whenever it can be added.

[AdSchellevis]

@ronin3510

A trash button facility would also be helpful in cleaning up old leases whenever it can be added.

no plans at the moment as you can not safely update the leases file (our old isc code offered this in quite a “hacky” way which we’re not going to replicate). Maybe when the control agent is used, although I haven’t tried that myself.