[Kea-users] Question about Stork subnet address counting and high-usage warning

[Oliver]

Hi everyone,

I’m running Kea DHCP4 together with Stork, and I’ve encountered something I
don’t fully understand regarding how Stork calculates the total number of
addresses in a subnet.

I have a *1XX.9.3.0/24* subnet configured, with only a very small dynamic
pool:

pools:
  - pool: 1XX.9.3.250-1XX.9.3.254

All other addresses in the /24 are used exclusively as *static host
reservations*.

However, Stork reports the following:

   -

   *Total addresses:* 62
   -

   *Assigned:* 51
   -

   *Free:* 11
   -

   *Usage:* 82.3% (yellow warning shown)

My question is:
*Why does Stork calculate only 62 total usable addresses for this subnet,
when the subnet is actually a full /24?*

I understand that my dynamic pool only contains 5 addresses, but I expected
Stork to consider the rest of the /24 as part of the subnet, since I use
those addresses for reservations.

Is this the expected behavior?
Does Stork count only “usable” addresses as those inside dynamic pools plus
explicitly configured reservations?
Is there a recommended way to have Stork recognize the entire /24 range so
it doesn’t trigger a high-usage warning?

Operationally everything works fine — I can continue creating reservations
without any issue — but I’d like to confirm whether this behavior is normal
or whether I might be missing something in the configuration.

Thanks in advance,
Oliver
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20251205/4dc93208/attachment.htm>