- A subnet is a deny-list subnet (the default: everyone not denied) or
an allow-list subnet (only clients allowed or with a reservation);
the deny list counts in both. Entries are MAC addresses, prefixes
(aa:bb:cc:*) or client IDs. A refused client gets no answer (DENIED
in the activity log, with an Allow button) or a NAK on renewal.
steward access, the subnet's Access tab. Schema migration 7.
- The activity log keeps each message's header fields and options,
decoded into words (dhcp4.Describe): the parameter request list by
name, client IDs, lease times. ▸ on an Activity row, steward
activity show N / --details, GET /events/{id}.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Which never-used pool address a new client gets: sequential (the
lowest, as before), reverse or random, in the settings, a subnet or
a single pool (FIRST-LAST:ORDER). When no never-used address is left,
the one free the longest, whatever the order; returning clients keep
theirs.
- A subnet's pools are used in the order listed, or one at random
weighted by its never-used addresses. Pools now keep the order they
are given in (no more sorting by address).
- CLI --address-order and --pool-order; --add-pool of an existing range
changes its order in place. Web UI: per-pool order and a move-up
button, pool and address order on the subnet and settings pages.
- Kea's allocator: random is imported. Schema migration 5.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Subnets served per interface, pools, reservations, options at three
levels, leases in SQLite saved before the ACK, ping and decline conflict
checks, validated changes with history and undo, users and tokens, an
audit log, a Kea importer, a sandboxed systemd unit and Debian packages.
Tested with real udhcpc and dhcpcd clients in Docker (scripts/e2e.sh).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
abrown38andClaude Opus 5.5