[kea-dev] Allow subnet/pool to reservations only

Mauser F Mauser at live.se
Wed May 23 19:45:25 UTC 2018


Hi!

I'm working at an ISP and looking into the possibility of migrating from ISC to Kea.
At the moment I'm trying out Kea-1.4-beta.

I want to restrict a subnet or pool to "KNOWN" entries only, but I can't get that to work.
Does anyone know of a way of does this or is it a working progress?

It seems if I define a class and evalute it with "member('KNOWN') and put "only-if-required" to true, the host reservation will be assigned to that class but the subnet and pool are already decided and unkown users will be offered an IP too.


    "client-classes": [
        {
                "name": "test-class",
                "test": "member('KNOWN')",
                "only-if-required": true
        }
    ],
    "subnet4": [
        {
                "subnet": "192.168.100.0/29",
                "id": 10,
                "pools": [
                        {
                                "pool": "192.168.100.2 - 192.168.100.6",
                                "require-client-classes":  ["test-class"]
                        }
                ],

                "option-data": [
                         {
                                "name": "routers",
                                "data": "192.168.100.1"
                        }
                ]
               "reservations": [
                        {
                                "hw-address": "00:0f:21:e8:77:c3",
                                "client-classes": ["KNOWN"]
                        }
                ]
        }
    ],
....

I've also tried the following, but then the user is denied the pool before the class assignment.

   "client-classes": [
        {
                "name": "test-class",
                "test": "member('KNOWN')"
        }
    ],
    "subnet4": [
        {
                "subnet": "192.168.100.0/29",
                "id": 10,
                "pools": [
                        {
                                "pool": "192.168.100.2 - 192.168.100.6",
                                "client-class":  "test-class"
                        }
                ],

                "option-data": [
                         {
                                "name": "routers",
                                "data": "192.168.100.1"
                        }
                ]
               "reservations": [
                        {
                                "hw-address": "00:0f:21:e8:77:c3",
                                "client-classes": ["test-class"]
                        }
                ]
        }
    ],
...

I'm I doing it wrong? Is it a bug? Will the feature be added later?

Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-dev/attachments/20180523/bb4b85b2/attachment-0001.html>


More information about the kea-dev mailing list