Plan and leases
- Kea
- JSON + Stork (extra) + often a sheet
- Lattice
- One catalog
Replace
Replace Kea
Keep your DNS.
Replace Kea: kea-dhcp4.conf and Stork (extra) plus a sheet is still a split brain. One catalog. Why NAK is a named queue, not a log line. Discover on A and Ack on B is the happy path.
On-prem · Ubuntu tarball · Community: 1,000 managed IPs · No phone-home
Beta signup issues a lifetime perpetual Starter license so you can test three-node HA. Not a sale.
Today — two systems
Plan
- Spreadsheet
- dhcpd.conf
DHCP
- MMC scopes
- Lease file
Keep them in sync yourself.
Lattice — one catalog
The reservation you save is the next Offer.
- prefix
- subnet
- pool
- reservation
- assignment
- lease
dhcpd serves these rows. Console writes them. There is no second copy to sync. A/PTR follow the grant into the DNS you already run.
Cutover
Lattice does not ingest Kea JSON. subnet4, pools, and reservations map to prefix, subnet, pool, reservation. kea-admin lease-dump can seed reservations. It is not a live lease import. Kea HA config does not come with you.
Playbook: Migrate · HA is not Microsoft failover — three-node VIP.
A Tuesday after cutover
JSON plus Stork plus a sheet is still two systems. Lattice is one catalog, so Work can name the failure.
9:05
What IP does this MAC have?
Helpdesk pastes a suffix. Search lands on the lease. Neteng is not the lookup API.
11:20
Give the printer .10 forever
The reservation you save is the next Offer. No scope to edit, no sheet to sync.
2:40
Laptop will not get an address
Work names the queue. No capture first. There is no primary to restart.
4:10
Who had this IP last Tuesday?
Occupancy is every remaining lease row. As-of a day. CSV. Not Audit, not a ping.
Scale-out / failover
- Kea
- Kea HA pair
- Lattice
- Same pool on every node (Starter: extra dhcpd + three-node VIP). Beta signup includes lifetime Starter.
Find a MAC
- Kea
- Stork / logs
- Lattice
- Console search
Who held this IP
- Kea
- Stork / lease-dump
DNS
- Kea
- BYO / hooks
- Lattice
- A/PTR after Ack into DNS you keep
Cutover
- Kea
- Map subnet4/pools/reservations; lease-dump seeds reservations only
- Lattice
- Dump → map → API
What hurts in Kea
JSON is the plan, Stork is extra
You already operate Kea. Stork is another install to see it. The spreadsheet is still the used list. That is still two systems.
HA is still a pair
Kea HA is a relationship between servers. It is not identical dhcpd on a shared lease store. Discover on A and Ack on B is not the happy path.
lease-dump is not IPAM
kea-admin lease-dump is a seed for reservations if you want printers to keep an IP. It is not a catalog dhcpd must honour tomorrow.
What Lattice does
dhcpd reads the catalog
No per-node subnet JSON. A reservation is the next Offer on every node that shares the database.
One console
Search, Addresses, Work. Why NAK is a named queue, not a log line in Stork.
Who held this IP
Occupancy is every remaining lease row. As-of a day. CSV. Not a Stork lease-dump.
Keep your DNS
BIND TSIG or AD GSS-TSIG after Ack. Option 6 does not move unless you move it.
Same pool, any node
Community is one Ubuntu node. Same binaries. A Starter file adds dhcpd processes on the same database (Discover on one node, Ack on another, same pool) and three-node HA behind a VIP. Signup includes a lifetime perpetual Starter license so you can test HA.
FAQ
- Will Lattice ingest Kea JSON?
- No. Map subnet4, pools, and reservations, then POST /api/v1. kea-admin lease-dump can seed reservations. It is not a live lease import. Read the migrate playbook.
- Do I still need Stork?
- No. Search, Addresses, and Work are one console. Why NAK is a named queue, not a log line.
- Is Lattice Kea HA?
- No. Kea HA is a pair. Lattice is the same pool on every node — Discover on A, Ack on B. Paid HA is three Ubuntu VMs and a VIP. Read the HA docs.