Elektrine lite

← Feed

@swhobbit@hachyderm.io

2026-07-24 16:48 UTC

@laird@hachyderm.io not everybody over specifies the Kea configuration. I do it all with flat files. I think my Raspberry Pi shipped with a "lease-database": of type "memfile". On my server, the leases go in an included flat file: (I mailed the Kea configuration file to you.) My DNS/DHCP post-edit-update Makefile (which generates the include file) also does a: systemctl restart kea-dhcp4-server.service Of course, this means that my DNS/DHCP Makefile, the generated include file, and the DHCP server all run on the same machine. I am not showing all work. For example the Makefile invokes a 642 Python line script that takes the simple flat file that I edit and generates the DNS zones files, IBM host files, UNIX host files, ssh config files and DHCP include files, but you're a bright guy.

Replies (1)

  • @laird@hachyderm.io 2026-07-24 17:14

    @swhobbit@hachyderm.io sounds reasonable. I'm up to 917 IP addresses and 175 IP prefixes in netbox right now, counting 482 DHCP pool addresses and a zillion PTP links. Not particularly big by any sort of enterprise standard, but way too big to want to manage without tooling. "Find an unassigned IP on network X" is a common operation and mostly-trivial now. Generating the kea config happens automatically. Generating DNS is automated but doesn't run from cron; I like to look at diffs. For example, I just noticed that Netbox 4.x has a "DHCP" address status, so I moved all of my DHCP entries from status "Active" to "DHCP", and discovered that my DNS updater wants to delete all of my DHCP DNS entries, presumably because it depends on "Active". Oops. Reverted for now. On the showing work front, https://github.com/scottlaird?tab=repositories&q=netbox2&type=&language=&sort=, although it's unlikely that it's actually useful for anyone else.

    Open ##4316309