- 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>
- A disabled reservation is kept but ignored: the client gets a pool
address like any other (steward reservation disable|enable, buttons and
a checkbox in the web UI). Schema migration 3.
- Subnets get Disable/Enable buttons on their page and in the list.
- A rule left without its selector in style.css broke the page heading's
layout, so the New ... buttons sat cramped under the description.
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>