dhcp6-srv.xml 168 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12 13
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY mdash  "&#x2014;" >

  <chapter id="dhcp6">
    <title>The DHCPv6 Server</title>

    <section id="dhcp6-start-stop">
      <title>Starting and Stopping the DHCPv6 Server</title>

Tomek Mrugalski's avatar
Tomek Mrugalski committed
14 15 16 17
        It is recommended that the Kea DHCPv6 server be started and stopped
        using <command>keactrl</command> (described in <xref linkend="keactrl"/>).
        However, it is also possible to run the server directly: it accepts
        the following command-line switches:
18 19

20 21
22 23 24 25
            <command>-c <replaceable>file</replaceable></command> -
            specifies the configuration file. This is the only mandatory
26 27
            <command>-d</command> - specifies whether the server
            logging should be switched to verbose mode. In verbose mode,
            the logging severity and debuglevel specified in the configuration
32 33 34 35
            file are ignored and "debug" severity and the maximum debuglevel
            (99) are assumed. The flag is convenient, for temporarily
            switching the server into maximum verbosity, e.g. when
36 37
38 39
            <command>-p <replaceable>port</replaceable></command> -
40 41
            specifies UDP port on which the server will listen. This is only
            useful during testing, as a DHCPv6 server listening on
            ports other than the standard ones will not be able to
            handle regular DHCPv6 queries.</simpara>
Tomek Mrugalski's avatar
Tomek Mrugalski committed
45 46
              <command>-v</command> - prints out the Kea version and exits.
Tomek Mrugalski's avatar
Tomek Mrugalski committed
48 49 50 51
52 53 54
              <command>-V</command> - prints out the Kea extended version with
              additional parameters and exits. The listing includes the versions
              of the libraries dynamically linked to Kea.
Tomek Mrugalski's avatar
Tomek Mrugalski committed
55 56
57 58
59 60 61 62 63
              <command>-W</command> - prints out the Kea configuration report
              and exits. The report is a copy of the
              <filename>config.report</filename> file produced by
              <userinput>./configure</userinput>: it is embedded in the
              executable binary.
64 65
66 67

Francis Dupont's avatar
Francis Dupont committed
Tomek Mrugalski's avatar
Tomek Mrugalski committed
69 70 71 72 73 74
        The <filename>config.report</filename> may also be accessed more
        directly.  The following command may be used to extract this
        information.  The binary <userinput>path</userinput> may be found
        in the install directory or in the <filename>.libs</filename>
        subdirectory in the source tree. For example

76 77 78 79 80
strings <userinput>path</userinput>/kea-dhcp6 | sed -n 's/;;;; //p'

        On start-up, the server will detect available network interfaces
83 84
        and will attempt to open UDP sockets on all interfaces
        mentioned in the configuration file.
85 86
        Since the DHCPv6 server opens privileged ports, it requires root
        access. Make sure you run this daemon as root.
87 88

89 90
        During startup the server will attempt to create a PID file of the
        form: localstatedir]/[conf name].kea-dhcp6.pid where:
92 93 94
            <simpara><command>localstatedir</command>: The value as passed into the
Jeremy C. Reed's avatar
Jeremy C. Reed committed
            build configure script. It defaults to "/usr/local/var".  Note
96 97 98 99 100
            that this value may be overridden at run time by setting the environment
            variable KEA_PIDFILE_DIR.  This is intended primarily for testing purposes.
            <simpara><command>conf name</command>: The configuration file name
102 103 104 105 106 107 108 109 110
            used to start the server, minus all preceding path and file extension.
            For example, given a pathname of "/usr/local/etc/kea/myconf.txt", the
            portion used would be "myconf".
        If the file already exists and contains the PID of a live process,
        the server will issue a DHCP6_ALREADY_RUNNING log message and exit. It
        is possible, though unlikely, that the file is a remnant of a system crash
        and the process to which the PID belongs is unrelated to Kea.  In such a
112 113
        case it would be necessary to manually delete the PID file.
114 115 116 117 118 119 120

        The server can be stopped using the <command>kill</command> command.
        When running in a console, the server can be shut down by
        pressing ctrl-c. It detects the key combination and shuts
        down gracefully.
121 122 123 124

    <section id="dhcp6-configuration">
      <title>DHCPv6 Server Configuration</title>
125 126
        This section explains how to configure the DHCPv6 server using the
129 130
        Kea configuration backend. (Kea configuration using any other
        backends is outside of scope of this document.) Before DHCPv6
        is started, its configuration file has to be created. The
        basic configuration is as follows:
# DHCPv6 configuration starts on the next line
136 137 138
"Dhcp6": {

# First we set up global values
    "valid-lifetime": 4000,
140 141 142 143
    "renew-timer": 1000,
    "rebind-timer": 2000,
    "preferred-lifetime": 3000,

144 145 146 147 148
# Next we setup the interfaces to be used by the server.
    "interfaces-config": {
        "interfaces": [ "eth0" ]

# And we specify the type of lease database
150 151
    "lease-database": {
        "type": "memfile",
        "persist": true,
153 154 155 156 157 158 159 160 161 162 163 164 165 166
        "name": "/var/kea/dhcp6.leases"

# Finally, we list the subnets from which we will be leasing addresses.
    "subnet6": [
            "subnet": "2001:db8:1::/64",
            "pools": [
                     "pool": "2001:db8:1::1-2001:db8:1::ffff"
# DHCPv6 configuration ends with the next line
168 169 170 171 172 173

} </screen>

<para>The following paragraphs provide a brief overview of the parameters in
the above example together with
175 176 177 178 179 180 181 182 183 184
their format. Subsequent sections of this chapter go into much greater detail
for these and other parameters.</para>

<para>The lines starting with a hash (#) are comments and are ignored by
the server; they do not impact its
operation in any way.</para>

<para>The configuration starts in the first line with the initial
opening curly bracket (or brace). Each configuration consists of
one or more objects. In this specific example, we have only one
object, called Dhcp6. This is a simplified configuration, as usually
186 187
there will be additional objects, like <command>Logging</command> or
<command>DhcpDns</command>, but we omit them now for clarity. The Dhcp6
configuration starts with the <command>"Dhcp6": {</command> line
189 190 191 192
and ends with the corresponding closing brace (in the above example,
the brace after the last comment).  Everything defined between those
lines is considered to be the Dhcp6 configuration.</para>

<para>In the general case, the order in which those parameters appear does not
matter. There are two caveats here though. The first one is to remember that
195 196 197
the configuration file must be well formed JSON. That means that parameters
for any given scope must be separated by a comma and there must not be a comma
after the last parameter. When reordering a configuration file, keep in mind that
198 199
moving a parameter to or from the last position in a given scope may also require
moving the comma. The second caveat is that it is uncommon &mdash; although
legal JSON &mdash; to
201 202 203 204 205 206
repeat the same parameter multiple times. If that happens, the last occurrence of a
given parameter in a given scope is used while all previous instances are
ignored. This is unlikely to cause any confusion as there are no real life
reasons to keep multiple copies of the same parameter in your configuration

207 208
<para>Moving onto the DHCPv6 configuration elements, the very first few elements
define some global parameters. <command>valid-lifetime</command>
defines for how long the addresses (leases) given out by the server are valid. If
nothing changes, a client that got an address is allowed to use it for 4000
211 212 213
seconds. (Note that integer numbers are specified as is, without any quotes
around them.) The address will become deprecated in 3000 seconds (clients are
allowed to keep old connections, but can't use this address for creating new
214 215 216
connections). <command>renew-timer</command> and
<command> rebind-timer</command> are values that define T1 and T2 timers that
govern when the client will begin the renewal and rebind procedures.</para>

218 219 220 221 222 223 224 225 226 227 228 229 230 231
<para>The <command>interfaces-config</command> map specifies the server
configuration concerning the network interfaces, on which the server should
listen to the DHCP messages. The <command>interfaces</command> parameter
specifies a list of network interfaces on which the server should listen.
Lists are opened and closed with square brackets, with elements separated
by commas. Had we wanted to listen on two interfaces, the
<command>interfaces-config</command> would look like this:
"interfaces-config": {
    "interfaces": [ "eth0", "eth1" ]

<para>The next couple of lines define the lease database, the place where the server
233 234
stores its lease information. This particular example tells the server to use
<command>memfile</command>, which is the simplest (and fastest) database
backend. It uses an in-memory database and stores leases on disk in a CSV
file. This is a very simple configuration. Usually the lease database configuration
237 238 239
is more extensive and contains additional parameters.  Note that
is an object and opens up a new scope, using an opening brace.
Its parameters (just one in this example - <command>type</command>)
follow. Had there been more than one, they would be separated by commas. This
242 243
scope is closed with a closing brace. As more parameters for the Dhcp6 definition
follow, a trailing comma is present.</para>
244 245 246

<para>Finally, we need to define a list of IPv6 subnets. This is the
most important DHCPv6 configuration structure as the server uses that
247 248
information to process clients' requests. It defines all subnets from
which the server is expected to receive DHCP requests. The subnets are
249 250
specified with the <command>subnet6</command> parameter.  It is a list,
so it starts and ends with square brackets.  Each subnet definition in
the list has several attributes associated with it, so it is a structure
252 253
and is opened and closed with braces. At minimum, a subnet definition
has to have at least two parameters: <command>subnet</command> (that
defines the whole subnet) and <command>pools</command> (which is a list of
255 256 257 258 259 260 261
dynamically allocated pools that are governed by the DHCP server).</para>

<para>The example contains a single subnet. Had more than one been defined,
additional elements
in the <command>subnet6</command> parameter would be specified and
separated by commas. For example, to define two subnets, the following
syntax would be used:
263 264
"subnet6": [
        "pools": [ { "pool": "2001:db8:1::/112" } ],
266 267 268
        "subnet": "2001:db8:1::/64"
        "pools": [ { "pool": "2001:db8:2::1-2001:db8:2::ffff" } ],
        "subnet": "2001:db8:2::/64"
271 272
Note that indentation is optional and is used for aesthetic purposes only.
In some cases in may be preferable to use more compact notation.

278 279
<para>After all parameters are specified, we have two contexts open:
global and Dhcp6, hence we need two closing curly brackets to close them.
280 281
In a real life configuration file there most likely would be additional
components defined such as Logging or DhcpDdns, so the closing brace would
282 283 284 285 286 287
be followed by a comma and another object definition.</para>

  <title>Lease Storage</title>
  <para>All leases issued by the server are stored in the lease database.
  Currently there are four database backends available:  memfile (which is the
  default backend), MySQL, PostgreSQL and Cassandra.</para>
  <title>Memfile - Basic Storage for Leases</title>
292 293 294

  <para>The server is able to store lease data in different repositories. Larger
  deployments may elect to store leases in a database. <xref
  linkend="database-configuration6"/> describes this option. In typical
296 297
  smaller deployments though, the server will store lease information in a CSV file rather
  than a database. As well as requiring less administration, an
298 299 300 301
  advantage of using a file for storage is that it
  eliminates a dependency on third-party database software.</para>

  <para>The configuration of the file backend (Memfile) is controlled through
302 303 304
  the Dhcp6/lease-database parameters. The <command>type</command> parameter
  is mandatory and it specifies which storage for leases the server should use.
  The value of <userinput>"memfile"</userinput> indicates that the file should
305 306
  be used as the storage. The following list gives additional, optional,
  parameters that can be used to configure the Memfile backend.
307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333

      <simpara><command>persist</command>: controls whether the new leases and
      updates to existing leases are written to the file. It is strongly
      recommended that the value of this parameter is set to
      <userinput>true</userinput> at all times, during the server's normal
      operation. Not writing leases to disk will mean that if a server is restarted
      (e.g. after a power failure), it will not know what addresses have been
      assigned.  As a result, it may hand out addresses to new clients that are
      already in use. The value of <userinput>false</userinput> is mostly useful
      for performance testing purposes. The default value of the
      <command>persist</command> parameter is <userinput>true</userinput>,
      which enables writing lease updates
      to the lease file.

      <simpara><command>name</command>: specifies an absolute location of the lease
      file in which new leases and lease updates will be recorded. The default value
      for this parameter is <userinput>"[kea-install-dir]/var/kea/kea-leases6.csv"

      <simpara><command>lfc-interval</command>: specifies the interval in seconds, at
334 335
      which the server will perform a lease file cleanup (LFC).  This
      removes redundant (historical) information from the lease file
336 337 338 339 340 341 342 343 344
      and effectively reduces the lease file size. The cleanup process is described
      in more detailed fashion further in this section. The default value of the
      <command>lfc-interval</command> is <userinput>0</userinput>, which disables
      the LFC.</simpara>


  <para>An example configuration of the Memfile backend is presented below:
Jeremy C. Reed's avatar
Jeremy C. Reed committed

"Dhcp6": {
349 350
    "lease-database": {
        <userinput>"type": "memfile"</userinput>,
        <userinput>"persist": true</userinput>,
352 353
        <userinput>"name": "/tmp/kea-leases6.csv"</userinput>,
        <userinput>"lfc-interval": 1800</userinput>
354 355 356
357 358 359 360 361

    This configuration selects the <filename>/tmp/kea-leases6.csv</filename> as
    the storage for lease information and enables persistence (writing lease updates
    to this file). It also configures the backend perform the periodic cleanup
    of the lease files, executed every 30 minutes.
362 363

  <para>It is important to know how the lease file contents are organized
  to understand why the periodic lease file cleanup is needed. Every time
366 367
  the server updates a lease or creates a new lease for the client, the new
  lease information must be recorded in the lease file. For performance reasons,
368 369 370
  the server does not update the existing client's lease in the file, as it would
  potentially require rewriting the entire file. Instead, it simply appends the new lease
  information to the end of the file: the previous lease entries for the
371 372 373 374 375 376
  client are not removed. When the server loads leases from the lease file, e.g.
  at the server startup, it assumes that the latest lease entry for the client
  is the valid one. The previous entries are discarded. This means that the
  server can re-construct the accurate information about the leases even though
  there may be many lease entries for each client. However, storing many entries
  for each client results in bloated lease file and impairs the performance of
  the server's startup and reconfiguration as it needs to process a larger number
378 379 380
  of lease entries.

  <para>Lease file cleanup (LFC) removes all previous entries for each client and
382 383
  leaves only the latest ones. The interval at which the cleanup is performed
  is configurable, and it should be selected according to the frequency of lease
384 385
  renewals initiated by the clients. The more frequent the renewals, the smaller
  the value of <command>lfc-interval</command> should be. Note however, that the
386 387 388 389
  LFC takes time and thus it is possible (although unlikely) that new cleanup
  is started while the previous cleanup instance is still running, if the
  <command>lfc-interval</command> is too short. The server would recover from
  this by skipping the new cleanup when it detects that the previous cleanup
  is still in progress. But it implies that the actual cleanups will be
  triggered more rarely than configured. Moreover, triggering a new cleanup
  adds an overhead to the server which will not be able to respond to new
393 394
  requests for a short period of time when the new cleanup process is spawned.
  Therefore, it is recommended that the <command>lfc-interval</command> value
  is selected in a way that would allow for the LFC to complete the cleanup before a
396 397 398
  new cleanup is triggered.

399 400 401
  <para>Lease file cleanup is performed by a separate process (in background) to avoid
  a performance impact on the server process. In order to avoid the conflicts
  between two processes both using the same lease files, the LFC process
402 403 404 405 406 407
  operates on the copy of the original lease file, rather than on the lease
  file used by the server to record lease updates. There are also other files
  being created as a side effect of the lease file cleanup. The detailed
  description of the LFC is located on the Kea wiki:
  <ulink url="http://kea.isc.org/wiki/LFCDesign"/>.

409 410 411

<section id="database-configuration6">
  <title>Lease Database Configuration</title>
413 414

    <para>Lease database access information must be configured for the DHCPv6 server,
416 417 418 419 420
    even if it has already been configured for the DHCPv4 server.  The servers
    store their information independently, so each server can use a separate
    database or both servers can use the same database.</para>

421 422
  <para>Lease database configuration is controlled through the
  Dhcp6/lease-database parameters. The type of the database must be set to
  "memfile", "mysql", "postgresql" or "cql", e.g.
"Dhcp6": { "lease-database": { <userinput>"type": "mysql"</userinput>, ... }, ... }
  Next, the name of the database is to hold the leases must be set: this is the
  name used when the database was created
429 430 431
  (see <xref linkend="mysql-database-create"/>,
  <xref linkend="pgsql-database-create"/>
  or <xref linkend="cql-database-create"/>).
"Dhcp6": { "lease-database": { <userinput>"name": "<replaceable>database-name</replaceable>" </userinput>, ... }, ... }
435 436 437
  If the database is located on a different system to the DHCPv6 server, the
  database host name must also be specified. (It should be noted that this
  configuration may have a severe impact on server performance.):
"Dhcp6": { "lease-database": { <userinput>"host": <replaceable>remote-host-name</replaceable></userinput>, ... }, ... }
441 442
  The usual state of affairs will be to have the database on the same machine as
  the DHCPv6 server.  In this case, set the value to the empty string:
"Dhcp6": { "lease-database": { <userinput>"host" : ""</userinput>, ... }, ... }
446 447 448
  Should the database be located on a different system, you may need to specify a longer interval
  for the connection timeout:
"Dhcp6": { "lease-database": { <userinput>"connect-timeout" : <replaceable>timeout-in-seconds</replaceable></userinput>, ... }, ... }
450 451
The default value of five seconds should be more than adequate for local connections.
If a timeout is given though, it should be an integer greater than zero.
453 454 455
  <para>Finally, the credentials of the account under which the server will
  access the database should be set:
"Dhcp6": { "lease-database": { <userinput>"user": "<replaceable>user-name</replaceable>"</userinput>,
                               <userinput>"password": "<replaceable>password</replaceable>"</userinput>,
459 460
                              ... },
           ... }
462 463 464 465
  If there is no password to the account, set the password to the empty string
  "". (This is also the default.)</para>

<section id="hosts6-storage">
468 469
  <title>Hosts Storage</title>
    <para>Kea is also able to store information about host reservations in the
470 471
    database. The hosts database configuration uses the same syntax as the lease
    database. In fact, a Kea server opens independent connections for each
    purpose, be it lease or hosts information. This arrangement gives the most
    flexibility. Kea can be used to keep leases and host reservations
    separately, but can also point to the same database. Currently the
    supported hosts database types are MySQL and PostgreSQL. The Cassandra
    backend does not support host reservations yet.</para>

    <para>Please note that usage of hosts storage is optional. A user can define
    all host reservations in the configuration file. That is the recommended way
480 481 482
    if the number of reservations is small. However, when the number of
    reservations grows it's more convenient to use host storage. Please note
    that both storage methods (configuration file and one of the supported databases)
    can be used together. If hosts are defined in both places, the definitions
    from the configuration file are checked first and external storage is checked
    later, if necessary.</para>
486 487

<section id="hosts-database-configuration6">
  <title>DHCPv6 Hosts Database Configuration</title>
489 490

  <para>Hosts database configuration is controlled through the Dhcp6/hosts-database
  parameters. If enabled, the type of the database must be set to "mysql" or
  "postgresql". Other hosts backends may be added in later version of Kea.
493 494 495
"Dhcp6": { "hosts-database": { <userinput>"type": "mysql"</userinput>, ... }, ... }
496 497 498
  Next, the name of the database to hold the reservations must be set: this is the
  name used when the database was created  (see <xref linkend="supported-databases"/>
  for instructions how to setup desired database type).
499 500 501
"Dhcp6": { "hosts-database": { <userinput>"name": "<replaceable>database-name</replaceable>" </userinput>, ... }, ... }
  If the database is located on a different system than the DHCPv6 server, the
  database host name must also be specified. (Again it should be noted that this
504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524
  configuration may have a severe impact on server performance):
"Dhcp6": { "hosts-database": { <userinput>"host": <replaceable>remote-host-name</replaceable></userinput>, ... }, ... }
  The usual state of affairs will be to have the database on the same machine as
  the DHCPv6 server.  In this case, set the value to the empty string:
"Dhcp6": { "hosts-database": { <userinput>"host" : ""</userinput>, ... }, ... }
  <para>Finally, the credentials of the account under which the server will
  access the database should be set:
"Dhcp6": { "hosts-database": { <userinput>"user": "<replaceable>user-name</replaceable>"</userinput>,
                               <userinput>"password": "<replaceable>password</replaceable>"</userinput>,
                              ... },
           ... }
  If there is no password to the account, set the password to the empty string
  "". (This is also the default.)</para>
525 526

<section id="read-only-database-configuration6">
<title>Using Read-Only Databases for Host Reservations</title>
529 530
In some deployments the database user whose name is specified in the database backend
configuration may not have write privileges to the database. This is often
531 532 533
required by the policy within a given network to secure the data from being
unintentionally modified. In many cases administrators have inventory databases
deployed, which contain substantially more information about the hosts than
static reservations assigned to them. The inventory database can be used to create
535 536 537
a view of a Kea hosts database and such view is often read only.
538 539 540 541 542 543 544
Kea host database backends operate with an implicit configuration to both
read from and write to the database. If the database user does not have
write access to the host database, the backend will fail to start and the
server will refuse to start (or reconfigure). However, if access to a read
only host database is required for retrieving reservations for clients
and/or assign specific addresses and options, it is possible to explicitly
configure Kea to start in "read-only" mode. This is controlled by the
545 546
<command>readonly</command> boolean parameter as follows:
"Dhcp6": { "hosts-database": { <userinput>"readonly": true</userinput>, ... }, ... }
548 549 550 551 552 553 554 555 556
Setting this parameter to <userinput>false</userinput> would configure the
database backend to operate in "read-write" mode, which is also a default
configuration if the parameter is not specified.
<note><para>The <command>readonly</command> parameter is currently only supported
for MySQL and PostgreSQL databases.</para></note>



<section id="dhcp6-interface-selection">
  <title>Interface Selection</title>
  <para>The DHCPv6 server has to be configured to listen on specific network
  interfaces.  The simplest network interface configuration instructs the server to
564 565
  listen on all available interfaces:
566 567 568 569 570 571 572
"Dhcp6": {
    "interfaces-config": {
        "interfaces": [ <userinput>"*"</userinput> ]
573 574 575
  The asterisk plays the role of a wildcard and means "listen on all interfaces".
  However, it is usually a good idea to explicitly specify interface names:
576 577 578 579 580 581 582 583
"Dhcp6": {
    "interfaces-config": {
        "interfaces": [ <userinput>"eth1", "eth3"</userinput> ]
  <para>It is possible to use wildcard interface name (asterisk) concurrently
  with the actual interface names:
587 588 589 590 591 592 593
"Dhcp6": {
    "interfaces-config": {
        "interfaces": [ <userinput>"eth1", "eth3", "*"</userinput> ]
594 595 596 597
It is anticipated that this will form of usage only be used where it is desired to
temporarily override a list of interface names and listen on all interfaces.
598 599 600 601

    <section id="ipv6-subnet-id">
      <title>IPv6 Subnet Identifier</title>
        The subnet identifier is a unique number associated with a particular subnet.
603 604
        In principle, it is used to associate clients' leases with their respective subnets.
        When a subnet identifier is not specified for a subnet being configured, it will
605 606 607 608 609
        be automatically assigned by the configuration mechanism. The identifiers
        are assigned from 1 and are monotonically increased for each subsequent
        subnet: 1, 2, 3 ....
610 611 612 613 614 615 616 617 618 619
        If there are multiple subnets configured with auto-generated identifiers and
        one of them is removed, the subnet identifiers may be renumbered. For example:
        if there are four subnets and the third is removed the last subnet will be assigned
        the identifier that the third subnet had before removal. As a result, the leases
        stored in the lease database for subnet 3 are now associated with
        subnet 4, something that may have unexpected consequences. It is planned
        to implement a mechanism to preserve auto-generated subnet ids in a
        future version of Kea.  However, the only remedy for this issue
        at present is to
        manually specify a unique identifier for each subnet.
620 621
622 623
        The following configuration will assign the specified subnet
        identifier to the newly configured subnet:

626 627
"Dhcp6": {
    "subnet6": [
628 629 630 631 632
            "subnet": "2001:db8:1::/64",
            <userinput>"id": 1024</userinput>,
633 634 635
636 637 638
        This identifier will not change for this subnet unless the "id" parameter is
        removed or set to 0. The value of 0 forces auto-generation of the subnet
640 641
      <!-- @todo: describe whether database needs to be updated after changing
      id -->
642 643 644

    <section id="dhcp6-unicast">
      <title>Unicast Traffic Support</title>
        When the DHCPv6 server starts, by default it listens to the DHCP traffic
648 649 650 651
        sent to multicast address ff02::1:2 on each interface that it is
        configured to listen on (see <xref linkend="dhcp6-interface-selection"/>).
        In some cases it is useful to configure a server to handle incoming
        traffic sent to the global unicast addresses as well. The most common
652 653 654
        reason for this is to have relays send their traffic to the server
        directly. To configure the server to listen on a specific unicast address,
        nn interface name can be
        optionally followed by a slash, followed by the global unicast address on which
656 657
        the server should listen. The server listens to this address in addition to normal
        link-local binding and listening on ff02::1:2 address. The sample configuration
        below shows how to listen on 2001:db8::1 (a global address)
659 660 661
        configured on the eth1 interface.
662 663
"Dhcp6": {
664 665 666
    "interfaces-config": {
        "interfaces": [ <userinput>"eth1/2001:db8::1"</userinput> ]
668 669 670
    "option-data": [
            "name": "unicast",
Francis Dupont's avatar
Francis Dupont committed
            "data": "2001:db8::1"
672 673
        } ],
674 675

        This configuration will cause the server to listen on
        eth1 on the link-local address, the multicast group (ff02::1:2) and 2001:db8::1.
680 681 682
        Usually unicast support is associated with a server unicast option
        which allows clients to send unicast messages to the server.
683 684
        The example above includes a server unicast option specification
        which will cause the client to send messages to the specified
Francis Dupont's avatar
Francis Dupont committed
        unicast address.
687 688
        It is possible to mix interface names, wildcards and interface name/addresses
        in the list of interfaces. It is not possible however to specify more than one
690 691 692 693
        unicast address on a given interface.
        Care should be taken to specify proper unicast addresses. The server will
694 695 696
        attempt to bind to the addresses specified without any additional checks.
        This approach has selected on purpose to allow the software to
        communicate over uncommon addresses if so desired.
697 698 699 700 701 702

    <section id="dhcp6-address-config">
      <title>Subnet and Address Pool</title>
        The main role of a DHCPv6 server is address assignment. For this,
704 705 706 707 708 709 710
        the server has to be configured with at least one subnet and one pool of dynamic
        addresses to be managed. For example, assume that the server
        is connected to a network segment that uses the 2001:db8:1::/64
        prefix. The Administrator of that network has decided that addresses from range
        2001:db8:1::1 to 2001:db8:1::ffff are going to be managed by the Dhcp6
        server. Such a configuration can be achieved in the following way:
711 712 713 714 715 716
"Dhcp6": {
    <userinput>"subnet6": [
           "subnet": "2001:db8:1::/64",
           "pools": [
                   "pool": "2001:db8:1::1-2001:db8:1::ffff"
718 719 720 721 722 723 724

725 726 727 728
        Note that <command>subnet</command> is defined as a simple string, but
        the <command>pools</command> parameter is actually a list of pools: for
        this reason, the pool definition is enclosed in square brackets, even
        though only one range of addresses is specified.</para>
729 730

        <para>Each <command>pool</command> is a structure that contains the
        parameters that describe a single pool. Currently there is only one
732 733 734 735
        parameter, <command>pool</command>, which gives the range of addresses
        in the pool. Additional parameters will be added in future releases of

736 737
        <para>It is possible to define more than one pool in a
        subnet: continuing the previous example, further assume that
        2001:db8:1:0:5::/80 should also be managed by the server. It could be written as
739 740 741 742 743
        2001:db8:1:0:5:: to 2001:db8:1::5:ffff:ffff:ffff, but typing so many 'f's
        is cumbersome. It can be expressed more simply as 2001:db8:1:0:5::/80. Both
        formats are supported by Dhcp6 and can be mixed in the pool list.
        For example, one could define the following pools:
744 745 746 747 748
"Dhcp6": {
    <userinput>"subnet6": [
        "subnet": "2001:db8:1::/64",
        "pools": [
749 750
            { "pool": "2001:db8:1::1-2001:db8:1::ffff" },
            { "pool": "2001:db8:1:05::/80" }
751 752 753 754 755
756 757 758 759
        White space in pool definitions is ignored, so spaces before and after the hyphen are optional.
        They can be used to improve readability.
760 761 762 763 764 765 766
        The number of pools is not limited, but for performance reasons it is recommended to
        use as few as possible.
         The server may be configured to serve more than one subnet. To add a second subnet,
         use a command similar to the following:
767 768 769 770 771
"Dhcp6": {
    <userinput>"subnet6": [
        "subnet": "2001:db8:1::/64",
        "pools": [
            { "pool": "2001:db8:1::1-2001:db8:1::ffff" }
773 774 775 776 777
        "subnet": "2001:db8:2::/64",
        "pools": [
            { "pool": "2001:db8:2::/64" }
779 780 781 782 783 784
        In this example, we allow the server to
        dynamically assign all addresses available in the whole subnet. Although
        rather wasteful, it is certainly a valid configuration to dedicate the
        whole /64 subnet for that purpose. Note that the Kea server does not preallocate
        the leases, so there is no danger in using gigantic address pools.
790 791 792
        When configuring a DHCPv6 server using prefix/length notation, please pay
793 794
        attention to the boundary values. When specifying that the server can use
        a given pool, it will also be able to allocate the first (typically network
        address) address from that pool. For example, for pool 2001:db8:2::/64 the
796 797
        2001:db8:2:: address may be assigned as well. If you want to avoid this,
        use the "min-max" notation.
798 799 800 801 802 803 804

<!-- @todo: add real meat to the prefix delegation config this is just place holder stuff -->
      <title>Subnet and Prefix Delegation Pools</title>
        Subnets may also be configured to delegate prefixes, as defined in
806 807 808 809 810 811 812 813 814 815
        <ulink url="http://tools.ietf.org/html/rfc3633">RFC 3633</ulink>.  A
        subnet may have one or more prefix delegation pools.  Each pool has a
        prefixed address, which is specified as a prefix
        (<command>prefix</command>) and a prefix length
        (<command>prefix-len</command>), as well as a delegated prefix length
        (<command>delegated-len</command>). The delegated length must not be
        shorter (that is it must be numerically greater or equal) than the
        prefix length.  If both the delegated and prefix lengths are equal, the
        server will be able to delegate only one prefix. The delegated prefix
        does not have to match the subnet prefix.
816 817 818
      <para> Below is a sample subnet configuration which enables prefix
      delegation for the subnet:
820 821 822 823 824 825
"Dhcp6": {
    "subnet6": [
            "subnet": "2001:d8b:1::/64",
            <userinput>"pd-pools": [
                    "prefix": "3000:1::",
827 828 829 830 831 832 833 834
                    "prefix-len": 64,
                    "delegated-len": 96
835 836 837 838

    <section id="dhcp6-std-options">
      <title>Standard DHCPv6 Options</title>
841 842
        One of the major features of a DHCPv6 server is to provide configuration
        options to clients.  Although there are several options that require
        special behavior, most options are sent by the server only if the client
        explicitly requests them.  The following example shows how to
845 846
        configure DNS servers, one of the most frequently used
        options.  Options specified in this way are considered
847 848 849
        global and apply to all configured subnets.

"Dhcp6": {
851 852 853 854 855
    "option-data": [
           <userinput>"name": "dns-servers",
           "code": 23,
           "space": "dhcp6",
           "csv-format": true,
857 858 859 860 861
           "data": "2001:db8::cafe, 2001:db8::babe"</userinput>
862 863

      The <command>option-data</command> line creates a new entry in
      the option-data table.  This table contains
      information on all global options that the server is supposed to configure
      in all subnets.  The <command>name</command> line specifies the option name.
      (For a complete list
      of currently supported names, see <xref
      linkend="dhcp6-std-options-list"/>.)  The next line specifies the option code,
873 874 875
      which must match one of the values from that list. The line beginning with
      <command>space</command> specifies the option space, which must always be set
      to "dhcp6" as these are standard DHCPv6 options.  For other name spaces,
      including custom option spaces, see <xref
      linkend="dhcp6-option-spaces"/>. The following line specifies the format in
      which the data will be entered: use of CSV (comma separated values) is
      recommended. Finally, the <command>data</command> line gives the actual value to be sent to
      clients.  Data is specified as normal text, with values separated by
      commas if more than one value is allowed.
882 883 884

      Options can also be configured as hexadecimal values.  If "csv-format" is
      set to false, the option data must be specified as a string of hexadecimal
      numbers.  The
888 889 890
      following commands configure the DNS-SERVERS option for all
      subnets with the following addresses: 2001:db8:1::cafe and
"Dhcp6": {
893 894 895 896 897
    "option-data": [
           <userinput>"name": "dns-servers",
           "code": 23,
           "space": "dhcp6",
           "csv-format": false,
899 900 901 902 903 904 905
           "data": "2001 0DB8 0001 0000 0000 0000 0000 CAFE
                    2001 0DB8 0001 0000 0000 0000 0000 BABE"</userinput>
906 907
       The value for the setting of the "data" element is split across two
909 910 911 912 913
       lines in this example for clarity: when entering the command, the
       whole string should be entered on the same line.
       Care should be taken
914 915
       to use proper encoding when using hexadecimal format as Kea's ability
       to validate data correctness in hexadecimal is limited.
916 917

918 919 920 921 922 923 924
        Most of the parameters in the "option-data" structure are optional and
        can be omitted in some circumstances as discussed in the
        <xref linkend="dhcp6-option-data-defaults"/>.

925 926 927 928 929 930 931 932 933 934 935 936 937 938
      It is possible to override options on a per-subnet basis.  If
      clients connected to most of your subnets are expected to get the
      same values of a given option, you should use global options: you
      can then override specific values for a small number of subnets.
      On the other hand, if you use different values in each subnet,
      it does not make sense to specify global option values
      (Dhcp6/option-data), rather you should set only subnet-specific values
      The following commands override the global
      DNS servers option for a particular subnet, setting a single DNS
      server with address 2001:db8:1::3.
939 940 941 942 943 944 945 946
"Dhcp6": {
    "subnet6": [
            <userinput>"option-data": [
                    "name": "dns-servers",
                    "code": 23,
Jeremy C. Reed's avatar
Jeremy C. Reed committed
                    "space": "dhcp6",
                    "csv-format": true,
949 950 951 952 953 954 955 956 957 958 959
                    "data": "2001:db8:1::3"
960 961 962 963 964 965 966 967 968 969

      The currently supported standard DHCPv6 options are
      listed in <xref linkend="dhcp6-std-options-list"/>.
      The "Name" and "Code"
      are the values that should be used as a name in the option-data
      structures. "Type" designates the format of the data: the meanings of
      the various types is given in <xref linkend="dhcp-types"/>.
970 971 972 973 974
      Experimental options (like standard options but with a code
      which was not assigned by IANA) are listed in
      <xref linkend="dhcp6-exp-options-list"/>.
975 976 977
      Some options are designated as arrays, which means that more than one
      value is allowed in such an option. For example the option dns-servers
      allows the specification of more than one IPv6 address, allowing
      clients to obtain the addresses of multiple DNS servers.
980 981 982 983 984 985 986 987 988 989

<!-- @todo: describe record types -->

        The <xref linkend="dhcp6-custom-options"/> describes the configuration
        syntax to create custom option definitions (formats). It is generally not
        allowed to create custom definitions for standard options, even if the
        definition being created matches the actual option format defined in the
        RFCs. There is an exception from this rule for standard options for which
        Kea does not yes provide a definition. In order to use such options,
991 992 993
        a server administrator must create a definition as described in
        <xref linkend="dhcp6-custom-options"/> in the 'dhcp6' option space. This
        definition should match the option format described in the relevant
994 995
        RFC but the configuration mechanism would allow any option format as it has
        no means to validate the format at the moment.
996 997 998 999 1000

      <table frame="all" id="dhcp6-std-options-list">
        <title>List of Standard DHCPv6 Options</title>
1002 1003
        <tgroup cols='4'>
        <colspec colname='name'/>
1004 1005 1006
        <colspec colname='code' align='center'/>
        <colspec colname='type' align='center'/>
        <colspec colname='array' align='center'/>
1007 1008 1009 1010 1011 1012