[Kea-users] Multiple ipv6 addresses/prefix reservations

[Olivier Clavel]

On Thu, 23 Feb 2017 at 15:47 Tomek Mrugalski <tomasz at isc.org> wrote:

W dniu 23.02.2017 o 11:35, Olivier Clavel pisze:
> On http://kea.isc.org/wiki/KeaKnownIssues I see that  /"/Static
> reservation of multiple IPv6 addresses or multiple IPv6 prefixes is not
> supported." was specified for versions up to 1.0.0 but as been removed
> on 1.1.0. Does that mean I can reserve several IPv6 addresses on
> different network/pools for a single client ? Anything special to deal
> with in the configuration ?
Having a reservation for the same host in different subnets worked for a
long time, for both v4 and v6. That's the case when client moves to a
different location in your network.

Now, DHCPv6 allows for a client to get more than one address and/or
prefix and given location. To support that, the client should send more
than one IA_NA (for address) and/or IA_PD (for prefix). Kea supports
that for a long time.


Ok. This is what I'm trying to achieve. I have a ula network prefix. I'd
like clients to possibly get both addresses from the server. Here is the
config

 "Dhcp6": {
    "host-reservation-identifiers": [ "hw-address" ],
    "subnet6": [
         {
             "subnet": "fdc5:xxxx:xxxx::/64",
             "id": 1,
             "interface": "eth0",
             "pools": [
                 { "pool": "fdc5:xxxx:xxxx::1000-fdc5:xxxx:xxxx::1fff" }
             ],
             "reservation-mode": "out-of-pool",
             "reservations": [
                 {
                     "ip-addresses": [ "fdc5:xxxx:xxxx::cafe" ],
                     "hw-address": "d8:22:8a:33:d1:8f",
                     "hostname": "bob"
                 },
                 {
                     "ip-addresses": [ "fdc5:xxxx:xxxx::babe" ],
                     "hw-address": "f8:22:03:33:0c:40",
                     "hostname": "john"
                 }
             ]
         },
         {
             "subnet": "2a01:xxxx:xxxx:xxxx::/64",
             "id": 2,
             "interface": "eth0",
             "pools": [
                 { "pool":
"2a01:xxxx:xxxx:xxxx::1000-2a01:xxxx:xxxx:xxxx::1fff" }
             ],
             "reservation-mode": "out-of-pool",
             "reservations": [
                  {
                      "ip-addresses": [ "2a01:xxxx:xxxx:xxxx::cafe" ],
                      "hw-address": "d8:22:8a:33:d1:8f",
                      "hostname": "bob"
                  },
                  {
                      "ip-addresses": [ "2a01:xxxx:xxxx:xxxx::8" ],
                      "hw-address": "f8:22:03:33:0c:40",
                      "hostname": "john"
                  }
             ]
        }
    ]
}

Assigning for ULA network works as expected but I never catch an address
from the global network. No matter how many dhcp requests I send, I only
get subsequent adresses from the ULA network only. Is there something I
didn't get or should I change client to achieve this (currently using
dhclient) ?


What has recently been improved is the ability to reserve multiple
addresses or prefixes at one location. To take advantage of that, your
client needs to send multiple IA_NA and/or IA_PD.

I just noticed that there's a small bug in the documentation. Section
8.3 incorrectly states how to reserve multiples addresses:

INCORRECT TEXT:
{
   "hw-address": "00:01:02:03:04:05",
   "ip-addresses": [ "2001:db8:1::101, 2001:db8:1::102" ]
},

SHOULD BE:
{
   "hw-address": "00:01:02:03:04:05",
   "ip-addresses": [ "2001:db8:1::101", "2001:db8:1::102" ]
},

I just pushed this correction to master. The user's guide is being
regenerated daily, so this link should be correct tomorrow:
https://jenkins.isc.org/job/Kea_doc/guide/kea-guide.html#host-reservation-v6

Tomek

_______________________________________________
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/20170223/f11c79c2/attachment.htm>