Messages

Make sure that your device supports DHCPv6. For example, Google devices currently only support slacc, which will not appear on KEA IPv6 leases.

Hello team,

No, I am not using any "tracking interface" settings.

My configuration is:
* WAN: Uses DHCPv6 for IPv6.
* LAN: Uses a static IPv6 configuration.

Additionally, I tested using the KEA version from 25.7.4, and the same problem persists. This suggests the issue might not be related to the KEA version itself?

Thank you!

Are you using LAN tracking WAN via DHCPv6? Maybe there is an instability in your uplink.

I wouldn't suspect core changes at a first glance either, but maybe a newer Kea version could also be the culprit?

[seems]

> OPNsense team seems to have made some changes from 25.7.5

Can you be more precise please?


Cheers,
Franco

Hello team,

I cannot pinpoint the exact change that caused this, but I can confirm that all my ULA (Unique Local Address) configurations were working perfectly before version 25.7.5. They stopped functioning immediately after that update.

Recently, I've observed some new behavior. When I disable the "WAN-DHCPv6 Gateway" setting (which I did for monitoring purposes), the following happens:

Existing Devices: Devices configured for DHCP that already had a static lease defined in the KEA DHCPv6 Server can successfully renew their lease.

New Devices: New devices (with no prior lease) are unable to obtain a new ULA address from the KEA DHCPv6 Server.

I also received a similar warning message as follows

WARN [kea-dhcp6.alloc-engine.0x32c76de6b808] ALLOC_ENGINE_V6_ALLOC_FAIL_CLASSES duid=[], [no hwaddr info], tid=0xb03321: Failed to allocate an IPv6 address for client with classes: ALL, KNOWN

WARN [kea-dhcp6.alloc-engine.0x32c76de6b808] ALLOC_ENGINE_V6_ALLOC_FAIL_NO_POOLS duid=[], [no hwaddr info], tid=0xb03321: no pools were available for the lease allocation

Warningkea-dhcp6WARN [kea-dhcp6.alloc-engine.0x32c76de6b808] ALLOC_ENGINE_V6_ALLOC_FAIL_SUBNET duid=[], [no hwaddr info], tid=0xb03321: failed to allocate an IPv6 lease in the subnet abcd:efgh:abcd::/64, subnet-id 1, shared network (none)

I hope this information helps narrow down the potential cause.

Thank you!

In my case, the OPNsense team seems to have made some changes from 25.7.5, resulting in the use of ULA in KEA DHCPv6 Server, the inability to update the lease, and the no ULA IPv6 addresses was assigned for new devices. But it is all normal if in slacc mode.