busybox VS dhcproto

Also known as Dash in Debian (it's satandard POSIX shell) and sh in Busybox that sadly tainted the original BSD source file with GPL2.

https://github.com/mirror/busybox/blob/master/shell/ash.c

More Good projects to learn from:

  - Busybox (https://github.com/mirror/busybox)

Also, it's barebones POSIX, and not the Linux extensions you commonly think of. But, that means the processes are a lot simpler, and the code is often less complex. So it's a good place for a beginner to dip into to see how .e.g mv works, compared to GNU mv.

Sure... There are symlinks in the installation, and there's a small main() function that dispatches execution to the appropriate function based on argv[0], but that doesn't significantly impact the C implementation of each individual tool. Those seem pretty straightforward, to me. A developer reading.. e.g. chmod.c isn't going to see any evidence of symlinks, and minimal impact from the external main() function.

BusyBox: https://github.com/mirror/busybox/blob/master/coreutils/ls.c

true false

Ok here is my followup. I didn't go into detail about kea hooks [0] because I didn't write any kea hook before, but from what I can tell it should cover all your needs. You have to write c code which I find absurd tbh, but if it has the functionality you are looking for it could be a solution.

I already posted my dnsmasq "solution" so I will skip this. If you want a code example I could whip you one up.

Then there is coredhcp [1] and you can write plugins written in go for it.

From time to time some hobby dhcp server pop up, but most fade away since (I guess) the existing solutions are "good enough". I for instance implement a automatic provisioning and configurating dhcp setup with tftp and pxe boot using dnsmasq. It automatically creates pxe configs based on the mac address and some other stuff (tm). Kea seemed overkill for this usecase and I'm quite happy with what I got.

Your use case of automatically fixing hostnames through ISC seems a bit overkill to me as well to be frank. My home network has a few VLANs and every device in it is managed manually. It's a one time setup and most automation is unnecessary (and some devices in my network flatout ignore some dhcp options....). Aaaaanyway I still think that most dhcp servers out there support some form of scripting (heck even udhcpcd has a lease notify script that could be hacked to offer some of that functionality even though this gets only executed after the fact so a bit useless [2]).

> oh wait, I wonder how much ISC was paid … to do exactly this EOL … by these major ISPs?

I don't know. Nothing?

> Plausible future: I can envision a special DHCP vendor-specific OPTION to use time-based blockchain hash to further solidify their hold.

Reading your cynic banter I'm quite happy of not having your DHCP problems. Looking through your github repositories I can find a bunch of configuration files for dhclient, but not much in form of ISC configs (only the nintendo fix you posted in your first post). Would be really interested in your setup.

[0] https://kea.readthedocs.io/en/latest/arm/hooks.html

[1] https://github.com/coredhcp/coredhcp

[2] https://github.com/mirror/busybox/blob/master/examples/udhcp...

https://github.com/mirror/busybox/blob/121b02d6b6c9f276e7f8da560e5996d3e389cd63/networking/ntpd.c#L175

I'll probably write a longer form blog post about it at some point, but there was such good feedback and PRs after we open-sourced dhcproto that we thought we would share this project also. If you're interested, check it out!

At BlueCat we're looking at offering a DHCP replacement, here is the GitHub of where we're at:

https://github.com/bluecatengineering/dhcproto

Disclaimer: I work there. My own opinions.

I work at a DDI (DNS, DHCP, IPAM) company and I'm always excited to see others contributing to the space.

We've done some rust contributions but on the DHCP side of things: https://github.com/bluecatengineering/dhcproto