- 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>
- A reservation can have its own lease time (--lease-time, the
reservation dialog), over the subnet's. Schema migration 6.
- A reservation with a MAC address and a client ID matches either one
(a dual-boot machine sends two client IDs from one MAC); before, it
was found by MAC and then refused. A lease of the reserved address by
the client's other identity counts as its own.
- The Leases page shows a client's client ID; reserving a lease uses
both, or one with --by / the dialog's choice.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- interfaces.exclude in steward.yaml (names or shell patterns) leaves
interfaces out of GET /interfaces, the web UI's picker and
'steward interface list'. Subnets on them are still served.
- With the ping check on, active leases are pinged every minute; a
client that answers gets a last-seen time (leases.last_seen,
migration 4). Not answering never takes a client offline.
- The activity log filters by subnet (--subnet, the Activity page,
GET /events?subnet=).
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>
tls.acme names the certificate and jarl: the Jarl server and a token that
may only write the challenge record. Steward gets the certificate with
DNS-01 (lego), writing the record through Jarl's API into every view that
has the zone, renews it with a third of its lifetime left and swaps it
in without a restart. A check runs before every order: Jarl, the zone,
the token's permission, a test record, the zone's name servers, public
resolvers, clean-up; each step says what to fix. Staging by default.
With a certificate, each listener serves HTTPS and plain HTTP on one port
(redirecting plain HTTP, except from the server itself).
steward cert / cert check / cert renew, Server -> Certificate in the web
UI, GET /certificate, POST /certificate/check|renew. docs/certificates.md
and docs/jarl.md (the Jarl user and the token's grant).
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