Send kea-dev mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."


Today's Topics:

   1.  Draft Matrix of Kea Significant features (Victoria Risk)
   2.  Allow subnet/pool to reservations only (Mauser F)


----------------------------------------------------------------------

Message: 1
Date: Wed, 23 May 2018 11:54:09 -0700
From: Victoria Risk <[email protected]>
To: [email protected]
Subject: [kea-dev] Draft Matrix of Kea Significant features
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"

I have started a list of significant features added by release # for Kea.  We 
have something like this for BIND and it is very helpful if you are trying to 
find out when a feature was first introduced.
I put it into a Google sheets document so other people can contribute.

- are these the most significant features?
- is it clear enough?
there are a couple of things I am not entirely clear about, where there are ? 
in the document

https://docs.google.com/spreadsheets/d/1OThuXdNcpL5wQdY3EDyGrl_gKDzHUnJrvrrn46JuxVM/edit?usp=sharing
 
<https://docs.google.com/spreadsheets/d/1OThuXdNcpL5wQdY3EDyGrl_gKDzHUnJrvrrn46JuxVM/edit?usp=sharing>

Comments and edits are welcome. Once I have gotten a few reviews and I think it 
is ok, I will put it into the kb.isc.org <http://kb.isc.org/>
thank you!

Victoria Risk
Product Manager
Internet Systems Consortium
[email protected]





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

------------------------------

Message: 2
Date: Wed, 23 May 2018 19:45:25 +0000
From: Mauser F <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [kea-dev] Allow subnet/pool to reservations only
Message-ID:
        
<he1pr0801mb143577e8eca2774573e3db26c9...@he1pr0801mb1435.eurprd08.prod.outlook.com>
        
Content-Type: text/plain; charset="iso-8859-1"

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.html>

------------------------------

Subject: Digest Footer

_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev


------------------------------

End of kea-dev Digest, Vol 50, Issue 5
**************************************

Reply via email to