Support for Windows/ Windows Server

[steskalja]

Are there any plans for Windows / Windows Server support?

[leshow]

No plans, there are some calls to linux specific syscalls that would need to be changed to support windows. The main ones probably being the call to ioctl for ARP injection & the main UDP socket that uses recvmsg/sendmsg. Not being familiar with windows, I can't say how much effort that would be. If someone wants to PR an implementation that supports windows behind a cfg(target_os = "windows"), we could consider merging it.

MacOS support would be nice too. I think the sockets crate already supports macos, so that might just be a matter of changing the ARP injection call? PRs for that welcome also.

[Jackbennett]

You have to licence windows for each client using it, I couldn't clarify if that's only an MS Service or Windows Server itself. But one reason Linux is used so often for DHCP is because technically you'd have to have a CAL for each lease given out. https://www.microsoft.com/en-us/licensing/product-licensing/client-access-license

So big-picture I wouldn't say there's a point to windows support, especially if it's a lot of effort. There's https://github.com/PJO2/tftpd64/ for toy deploys like network booting vm's or other bootstrapping jobs before just deploying the settings to windows server dhcp.

You can get docker and WSL on the host adapter and just use linux there for DHCP too for toying around with from windows. I don't mean to be negative but I hated to think of someone's OSS work going to waste because of licencing they cannot out-compete on merit.