[Kea-users] Host reservations, bootfilename and client classes

Jorell F JorellF at outlook.com
Wed May 8 17:38:56 UTC 2019


Didn’t send to list.

________________________________
From: Jorell F
Sent: Wednesday, May 8, 2019 10:37:04 AM
To: mkangelo
Subject: RE: [Kea-users] Host reservations, bootfilename and client classes


Is this the answer you are looking for:



    "next-server": "<serverip>",

    "option-data":

    [

      {

        "name":  "no-pxedhcp",

        "data":  "1",

        "code":  176,

        "space": "ipxe"

      },

      {

        "name": "tftp-server-name",

        "data": "<serverip>"

      }

    ],

    "client-classes":

    [

      {

        "name": "Legacy ",

        "test": "substring(option[60].hex,0,20) == 'PXEClient:Arch:00000'",

        "boot-file-name": "ipxe/undionly.kpxe"

      },

      {

        "name": "UEFI-32-1",

        "test": "substring(option[60].hex,0,20) == 'PXEClient:Arch:00002'",

        "boot-file-name": "ipxe/i386/ipxe.efi"

      },

      {

        "name": "UEFI-32-2",

        "test": "substring(option[60].hex,0,20) == 'PXEClient:Arch:00006'",

        "boot-file-name": "ipxe/i386/ipxe.efi"

      },

      {

        "name": "UEFI-64-1",

        "test": "substring(option[60].hex,0,20) == 'PXEClient:Arch:00007'",

        "boot-file-name": "ipxe/x86_64/snponly.efi"

      },

      {

        "name": "UEFI-64-2",

        "test": "substring(option[60].hex,0,20) == 'PXEClient:Arch:00008'",

        "boot-file-name": "ipxe/x86_64/snponly.efi"

      },

      {

        "name": "UEFI-64-3",

        "test": "substring(option[60].hex,0,20) == 'PXEClient:Arch:00009'",

        "boot-file-name": "ipxe/x86_64/snponly.efi"

      },

      {

        "name": "EFI_HTTP",

        "test": "option[93].hex == 0x0010",

        "option-data": [ { "name": "vendor-class-identifier", "data": "HTTPClient" } ],

        "boot-file-name": "http://<serverip>:80/ipxe/x86_64/snponly.efi"

      },

      {

        "name": "XClient_iPXE",

        "test": "substring(option[77].hex,0,4) == 'iPXE'",

        "boot-file-name": "http://<serverip>:80/ipxe/boot.php"

      }

    ],



Clients that are PXE booting get the boot file, clients that already have the boot file get the config file.

(this config was working on kea v1.4)

I believe kea uses a last to match, if an option does not exist deeper in the config i.e. reservations, it will pull from subnet or global.





________________________________
From: Kea-users <kea-users-bounces at lists.isc.org> on behalf of mkangelo <angel.rushkov at gmail.com>
Sent: Tuesday, April 30, 2019 7:46:13 AM
To: kea-users at lists.isc.org
Subject: [Kea-users] Host reservations, bootfilename and client classes

Hi guys,

We are evaluating KEA (premium) as a potential replacement for our current
DHCP infra, and we have few concerns over the following:

1. Is it possible to have a custom bootFilename (option 67) set per host
reservation while it references to a single client class? (this should not
be part of the subnets).

2. Is it possible to prioritise bootFilename from a class (even if there is
already a bootFilename set in the reservation) based on the matching client
option (example 60, 77) ?

To clarify:

- We need clients that have option 77 to receive bootFilename from a
reservation and in case it doesn't have option 77 and matches just option 60
to receive bootFilename from that class.

- There will be multiple classes configured, and we'd like the host
reservations to be stored in a SQL database


I'd appreciate some feedback.


Example JSON config (classes and reservation - used for testing):





--
Sent from: http://kea-users.7364.n8.nabble.com/
_______________________________________________
Kea-users mailing list
Kea-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/kea-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20190508/28b6115d/attachment-0001.html>


More information about the Kea-users mailing list