Man skal passe på med at tilskrive til ondskab, hvad der kan forklares med inkompetence. Men det er pudsigt, at min egen router ikke kan få et DHCPv4 svar - og mine mesh punkter virker elendigt med Hipers egen router, netop som Hiper tilbyder at leje mesh punkter af dem for 20 kr/punkt/måned.
De vil som minimum ikke være særlig tilskyndet til at få mine til at virke.
#danmarkskifter #fritzbox #mesh #DHCPv4

Finally (2), I have some good enough DHCP server!  

Tried kea from ISC — it works but requires some additional actions to be launched under #NetBSD. It has very strange default paths for file with leases, PIDs and logs:
- /usr/pkg/var/lib/kea/
- /usr/pkg/var/lib/run/kea
- /usr/pkg/var/log/kea

BTW, it could be changed via playing with some environment variables.

Also, the default startup script uses keactrl to launch DHCP server and keactrl requires some configuration for it. So, to use "service kea start" there are two configuration files are necessary:
- /usr/pkg/etc/keactrl.conf — the main configuration file for server.
- /usr/pkg/etc/kea/keactrl.conf — the configuration file for keactrl.

Then, I tried the dhcpsd — the new promising successor of ISC dhcpd, which could be configured with configuration file in Lua and conforms Unix FHS — all necessary files lies in the right places: /var/run, /var/log, etc. Sadly, it doesn't work: server starts but there are no leases for clients and no any errors in the log :-(

Then, I found cmu-dhcpd in the repos — there is a dhcpd from Carnegie Mellon University with some patches from Princeton. And, finally it works! And it also conforms Unix FHS: main configuration in the /etc/dhcpd.conf, PID-file in the /var/run/dhcpd.pid and logs in the /var/log/messages  

#selfhosting #dhcp #DHCPv4 #dhcpd

Finally, I have some good enough DHCP server.

It is a kea from ISC – the successor of EOLed dhcpd.

The moment, when I switched re0 interface configuration from DHCP to static IP and rebooted the server — was the most touching. The second one — when I disabled DHCP server in the D-Link router, started kea and restarted the router  

Fortunately, the lines from connecting phone appeared in the kea log after some lenghty seconds  

#SelfHosting #dhcp #kea #DHCPv4

Kea DHCP: Modern, open source DHCPv4 and DHCPv6 server

https://www.isc.org/kea/

#HackerNews #Kea #DHCP #open #source #DHCPv4 #DHCPv6 #server #ISC

Kea DHCP

Modern, open source DHCPv4 & DHCPv6 server

#Kea 2.7.9 (dev) has been released (#DHCP / #DHCPv4 / #DHCPv6 / #DNS / #ISC / #InternetSystemsConsortium) https://www.isc.org/kea/
Kea DHCP

Modern, open source DHCPv4 & DHCPv6 server

#Kea 2.4.2 (old stable) has been released (#DHCP / #DHCPv4 / #DHCPv6 / #DNS / #ISC / #InternetSystemsConsortium) https://www.isc.org/kea/
Kea DHCP

Modern, open source DHCPv4 & DHCPv6 server

#Kea 2.6.3 (stable) has been released (#DHCP / #DHCPv4 / #DHCPv6 / #DNS / #ISC / #InternetSystemsConsortium) https://www.isc.org/kea/
Kea DHCP

Modern, open source DHCPv4 & DHCPv6 server

Dnsmasq - network services for small networks.

So … my ideal DDI solution consists of:
- #Kea #DHCPv4 #DHCPv6
- #PowerDNS Auth
- #ISC #Stork for Kea Management
- Custom application, that can
- Translate Kea Leases into a PowerDNS Remote backend
- Manipulate PowerDNS through its HTTP Api (i.e. an Admin interface)

Stork apparently got the ability to manage/configure Kea, so that's something I don't have to build.

Why not NSUpdate? Because it sucks.

#HomeLab #Network

#Kea 2.7.0 (dev) has been released (#DHCP / #DHCPv4 / #DHCPv6 / #DNS / #ISC / #InternetSystemsConsortium) https://www.isc.org/kea/
Kea DHCP

Modern, open source DHCPv4 & DHCPv6 server