Hello,
I'm in the process of migrating an ISC DHCP server to Kea. I'm trying to 
re-create a feature that we use in the ISC DHCP config to set a boot file name 
if a specific vendor-class-identifier is met. The ISC DHCP share-network looks 
like:
shared-network FOOBAR {
    allow bootp;

    subnet 10.10.10.0 netmask 255.255.255.0 {

        # default PXE boot
        if substring(option vendor-class-identifier, 0, 20) = 
"PXEClient:Arch:00000" {
            filename "ipxe/netboot.xyz.kpxe";
        } else {
            filename "ipxe/netboot.xyz.efi";
        }

For Kea I can create the client class just fine, but how can I restrict these 
client classes to apply only to this subnet? I have other subnets that use a 
different boot file name. It doesn't seem like using "client-class" in the 
"subnet4" config would work as that would require a client to meet the 
classification, when that's not necessary.

"client-classes": [
    {
        "name": "ipxe_legacy_netbootxyz",
        "test": "substring(option[60].hex,0,20) == 'PXEClient:Arch:00000'",
        "next-server": "10.10.10.5",
        "boot-file-name": "ipxe/netboot.xyz.kpxe"
    },
    {
        "name": "ipxe_efi_netbootxyz",
        "test": "substring(option[60].hex,0,20) == 'PXEClient:Arch:00007'",
        "next-server": "10.10.10.5",
        "boot-file-name": "ipxe/netboot.xyz.efi"
    }
],

Thanks,

Isaac Brummel
System Administrator
Extreme Engineering Solutions
-- 
ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.

To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.

Kea-users mailing list
Kea-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/kea-users

Reply via email to