[FEAT] [DHCP] iVentoy Support

[djarbz]

I want to deploy iVentoy while keeping T-DNS as my DHCP server.

It looks like T-DNS just needs to add some logic for the boot file as documented.

That is to say, in this mode, the third-part DHCP server must dynamically provides different bootfile options according to the information in the client's DHCP request packet.
For example, if the client is Legacy BIOS mode, then the bootfile option value should be iventoy_loader_16000_bios, if the client is UEFI mode, then the bootfile option value should be iventoy_loader_16000_uefi

dhcpd.conf example

subnet 10.0.0.0 netmask 255.255.255.0 {
    option routers 10.0.0.254;
    range 10.0.0.2 10.0.0.253;

    class "pxeclients" {
        match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
        next-server 10.0.0.1;

        if option architecture-type = 00:07 {
            filename "iventoy_loader_16000_uefi";
        } else {
            filename "iventoy_loader_16000_bios";
        }
    }
}

[ShreyasZare]

Thanks for the feature request. Will get this implemented soon.