dhcp4-srv.xml 110 KB
Newer Older
1
2
3
4
5
6
7
8
9
10
11
12
<?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="dhcp4">
    <title>The DHCPv4 Server</title>

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

13
14
      <!-- @todo Rewrite this section once #3422 is done -->

15
      <para>
16
      It is recommended that the Kea DHCPv4 server be started and stopped
Jeremy C. Reed's avatar
Jeremy C. Reed committed
17
      using <command>keactrl</command> (described in <xref linkend="keactrl"/>).
18
19
      However, it is also possible to run the server directly: it accepts
      the following command-line switches:
20
      </para>
21
22
23

      <itemizedlist>
          <listitem>
24
25
26
27
            <simpara>
            <command>-c <replaceable>file</replaceable></command> -
            specifies the configuration file. This is the only mandatory
            switch.</simpara>
28
29
          </listitem>
          <listitem>
30
            <simpara>
Tomek Mrugalski's avatar
Tomek Mrugalski committed
31
32
            <command>-d</command> - specifies whether the server
            logging should be switched to debug/verbose mode. In verbose mode,
33
            the logging severity and debuglevel specified in the configuration
34
35
36
37
            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
            debugging.</simpara>
38
39
          </listitem>
          <listitem>
40
41
42
43
44
45
            <simpara>
            <command>-p <replaceable>port</replaceable></command> -
            specifies UDP port the server will listen on. This is only
            useful during testing, as the DHCPv4 server listening on
            ports other than default DHCPv4 ports will not be able to
            handle regular DHCPv4 queries.</simpara>
46
          </listitem>
Tomek Mrugalski's avatar
Tomek Mrugalski committed
47
48
          <listitem>
            <simpara>
Tomek Mrugalski's avatar
Tomek Mrugalski committed
49
              <command>-v</command> - prints out Kea version and exits.
Tomek Mrugalski's avatar
Tomek Mrugalski committed
50
51
52
53
54
            </simpara>
          </listitem>
          <listitem>
            <simpara>
              <command>-V</command> - prints out Kea extended version with
Tomek Mrugalski's avatar
Tomek Mrugalski committed
55
              additional parameters and exits.
Tomek Mrugalski's avatar
Tomek Mrugalski committed
56
57
            </simpara>
          </listitem>
58
59
      </itemizedlist>

60
      <para>
61
62
63
	    When running in a console, the server can be shut down by
	    pressing ctrl-c. It detects the key combination and shuts
	    down gracefully.
64
65
66
67
      </para>

      <para>
        On start-up, the server will detect available network interfaces
68
69
        and will attempt to open UDP sockets on all interfaces
        mentioned in the configuration file.
70
      </para>
71

72
      <para>
73
74
75
76
77
78
79
        Since the DHCPv4 server opens privileged ports, it requires root
        access. Make sure you run this daemon as root.
      </para>

    </section>

    <section id="dhcp4-configuration">
80
      <title>DHCPv4 Server Configuration</title>
81
82
<section>
  <title>Introduction</title>
83
      <para>
84
        This section explains how to configure the DHCPv4 server using the
85
86
        Kea configuration backend. (Kea configuration using any other
        backends is outside of scope of this document.) Before DHCPv4
87
        is started, its configuration file has to be created. The
88
        basic configuration is as follows:
89
<screen>
90
91
92
93
94
95
96
97
98
{
# DHCPv4 configuration starts in this line
"Dhcp4": {

# First we set up global values
    "valid-lifetime": 4000,
    "renew-timer": 1000,
    "rebind-timer": 2000,

99
100
101
102
103
104
# Next we setup the interfaces to be used by the server.
    "interfaces-config": {
        "interfaces": [ "eth0" ]
    },

# And we specify the type of lease database
105
    "lease-database": {
Tomek Mrugalski's avatar
Tomek Mrugalski committed
106
        "type": "memfile",
107
        "persist": true,
Tomek Mrugalski's avatar
Tomek Mrugalski committed
108
        "name": "/var/kea/dhcp4.leases"
109
110
111
112
113
114
    },

# Finally, we list the subnets from which we will be leasing addresses.
    "subnet4": [
        {
            "subnet": "192.0.2.0/24",
115
116
117
            "pools": [
                { "pool": "192.0.2.1 - 192.0.2.200" }
            ]
118
119
120
121
122
123
124
        }
    ]

# DHCPv4 configuration ends with this line
}

} </screen>
125
</para>
126

127
128
129
130
<para>The following paragraphs provide a brief overview of the parameters in
the above example and
their format. Subsequent sections of this chapter go into much greater detail
for these and other parameters.</para>
131

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

136
137
138
139
140
141
<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 Dhcp4. This is a simplified configuration, as usually
there will be additional objects, like <command>Logging</command> or
<command>DhcpDns</command>, but we omit them now for clarity. The Dhcp4
142
configuration starts with the <command>"Dhcp4": {</command> line
143
144
145
146
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 Dhcp4 configuration.</para>

147
<para>In the general case, the order in which those parameters appear does not
148
matter. There are two caveats here though. The first one is to remember that
149
150
151
152
153
the configuration file must be well formed JSON. That means that the 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
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
154
legal JSON &mdash; to
155
repeat the same parameter multiple times. If that happens, the last occurrence of a
156
given parameter in a given scope is used while all previous instances are
157
ignored. This is unlikely to cause any confusion as there are no real life
158
159
160
reasons to keep multiple copies of the same parameter in your configuration
file.</para>

161
162
<para>Moving onto the DHCPv4 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
163
server are valid. If nothing changes, a client that got an address is allowed to
164
165
166
use it for 4000 seconds. (Note that integer numbers are specified as is,
without any quotes around them.) <command>renew-timer</command> and
<command>rebind-timer</command> are values that
167
define T1 and T2 timers that govern when the client will begin the renewal and
168
169
170
171
rebind procedures. Note that <command>renew-timer</command> and
<command>rebind-timer</command> are optional. If they are not specified the
client will select values for T1 and T2 timers according to the
<ulink url="http://tools.ietf.org/html/rfc2131">RFC 2131</ulink>.</para>
172

173
174
175
176
177
178
179
180
181
182
183
184
185
186
<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:
<screen>
"interfaces-config": {
    "interfaces": [ "eth0", "eth1" ]
},
</screen>
</para>

187
<para>The next couple of lines define the lease database, the place where the server
188
stores its lease information. This particular example tells the server to use
189
<command>memfile</command>, which is the simplest (and fastest) database
190
backend. It uses an in-memory database and stores leases on disk in a CSV
191
file. This is a very simple configuration. Usually, lease database configuration
192
193
194
195
196
197
198
199
200
201
is more extensive and contains additional parameters.  Note that
<command>lease-database</command>
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
scope is closed with a closing brace. As more parameters follow, a trailing
comma is present.</para>

<para>Finally, we need to define a list of IPv4 subnets. This is the
most important DHCPv4 configuration structure as the server uses that
202
203
information to process clients' requests. It defines all subnets from
which the server is expected to receive DHCP requests. The subnets are
204
205
specified with the <command>subnet4</command> parameter.  It is a list,
so it starts and ends with square brackets.  Each subnet definition in
206
207
the list has several attributes associated with it, so it is a structure
and is opened and closed with braces. At a minimum, a subnet definition
208
has to have at least two parameters: <command>subnet</command> (that
209
defines the whole subnet) and <command>pools</command> (which is a list of
210
dynamically allocated pools that are governed by the DHCP server).</para>
211
212
213
214
215
216

<para>The example contains a single subnet. Had more than one been defined,
additional elements
in the <command>subnet4</command> parameter would be specified and
separated by commas. For example, to define three subnets, the following
syntax would be used:
217
<screen>
218
219
"subnet4": [
    {
220
        "pools": [ { "pool":  "192.0.2.1 - 192.0.2.200" } ],
221
222
223
        "subnet": "192.0.2.0/24"
    },
    {
224
        "pools": [ { "pool": "192.0.3.100 - 192.0.3.200" } ],
225
226
227
        "subnet": "192.0.3.0/24"
    },
    {
Adam Osuchowski's avatar
Adam Osuchowski committed
228
        "pools": [ { "pool": "192.0.4.1 - 192.0.4.254" } ],
229
230
231
        "subnet": "192.0.4.0/24"
    }
]
232
233
234
</screen>
</para>

235
236
<para>After all parameters are specified, we have two contexts open:
global and Dhcp4, hence we need two closing curly brackets to close them.
237
238
In a real life configuration file there most likely would be additional
components defined such as Logging or DhcpDdns, so the closing brace would
239
be followed by a comma and another object definition.</para>
240

241
</section>
242

243
<section>
244
245
246
247
248
  <title>Lease Storage</title>
  <para>All leases issued by the server are stored in the lease database.
  Currently there are three database backends available:
  memfile (which is the default backend), MySQL and PostgreSQL.</para>
<section>
249
  <title>Memfile, Basic Storage for Leases</title>
250
251
252

  <para>The server is able to store lease data in different repositories. Larger
  deployments may elect to store leases in a database. <xref
253
254
255
256
257
  linkend="database-configuration4"/> describes this option. In typical
  smaller deployments though, the server will use a CSV file rather than a database to
  store lease information. As well as requiring less administration, an
  advantage of using a file for storage is that it
  eliminates a dependency on third-party database software.</para>
258
259

  <para>The configuration of the file backend (Memfile) is controlled through
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
  the Dhcp4/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
  be used as the storage. The following list presents the remaining, not mandatory
  parameters, which can be used to configure the Memfile backend.

  <itemizedlist>
    <listitem>
      <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>
    </listitem>

    <listitem>
      <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-leases4.csv"
      </userinput>.</simpara>
    </listitem>

    <listitem>
      <simpara><command>lfc-interval</command>: specifies the interval in seconds, at
      which the server (Memfile backend) will perform a lease file cleanup (LFC),
      which removes the redundant (historical) information from the lease file
      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>
    </listitem>

  </itemizedlist>
  </para>

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

305
<screen>
306
307
308
"Dhcp4": {
    "lease-database": {
        <userinput>"type": "memfile"</userinput>,
309
        <userinput>"persist": true</userinput>,
310
311
        <userinput>"name": "/tmp/kea-leases4.csv",</userinput>
        <userinput>"lfc-interval": 1800</userinput>
312
313
    }
}
314
</screen>
315
316

    This configuration selects the <filename>/tmp/kea-leases4.csv</filename> as
317
    the storage for lease information and enables persistence (writing lease updates
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
    to this file). It also configures the backend perform the periodic cleanup
    of the lease files, executed every 30 minutes.
  </para>

  <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 when
  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,
  the server does not supersede the existing client's lease, as it would require
  the lookup of the specific lease entry, but simply appends the new lease
  information at the end of the lease file. The previous lease entries for the
  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 larger number
  of lease entries.
  </para>

  <para>The lease file cleanup removes all previous entries for each client and
  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
  renewals initiated by the clients. The more frequent renewals are, the lesser
  value of the <command>lfc-interval</command> should be. Note however, that the
  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, this 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
  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 completing the cleanup before the
  new cleanup is triggered.
  </para>

  <para>The LFC is performed by a separate process (in background) to avoid
  performance impact on the server process. In order to avoid the conflicts
  between the two processes both using the same lease files, the LFC process
  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"/>.
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
  </para>

</section>

<section id="database-configuration4">
  <title>Database Configuration</title>

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

  <para>Database configuration is controlled through the Dhcp4/lease-database
380
381
  parameters. The type of the database must be set to "mysql" or "postgresql",
  e.g.
382
<screen>
383
"Dhcp4": { "lease-database": { <userinput>"type": "mysql"</userinput>, ... }, ... }
384
</screen>
385
  Next, the name of the database to hold the leases must be set: this is the
386
387
  name used when the lease database was created (see <xref linkend="mysql-database-create"/>
  or <xref linkend="pgsql-database-create"/>).
388
<screen>
389
"Dhcp4": { "lease-database": { <userinput>"name": "<replaceable>database-name</replaceable>" </userinput>, ... }, ... }
390
</screen>
391
  If the database is located on a different system to the DHCPv4 server, the
392
  database host name must also be specified (although it should be noted that this
393
  configuration may have a severe impact on server performance):
394
<screen>
395
"Dhcp4": { "lease-database": { <userinput>"host": <replaceable>remote-host-name</replaceable></userinput>, ... }, ... }
396
</screen>
397
398
  The usual state of affairs will be to have the database on the same machine as
  the DHCPv4 server.  In this case, set the value to the empty string:
399
<screen>
400
"Dhcp4": { "lease-database": { <userinput>"host" : ""</userinput>, ... }, ... }
401
</screen>
402
403
404
  </para>
  <para>Finally, the credentials of the account under which the server will
  access the database should be set:
405
<screen>
406
"Dhcp4": { "lease-database": { <userinput>"user": "<replaceable>user-name</replaceable>"</userinput>,
407
                               <userinput>"password": "<replaceable>password</replaceable>"</userinput>,
408
409
                              ... },
           ... }
410
</screen>
411
412
413
  If there is no password to the account, set the password to the empty string
  "". (This is also the default.)</para>
</section>
414
</section>
415

416
417
<section id="dhcp4-interface-configuration">
  <title>Interface configuration</title>
418
  <para>The DHCPv4 server has to be configured to listen on specific network
419
420
421
  interfaces.  The simplest network interface configuration tells the server to
  listen on all available interfaces:
  <screen>
422
423
424
425
426
427
428
"Dhcp4": {
    "interfaces-config": {
        "interfaces": [ <userinput>"*"</userinput> ]
    }
    ...
},
  </screen>
429
430
  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:
431
  <screen>
432
433
434
435
436
437
438
"Dhcp4": {
    "interfaces-config": {
        "interfaces": [ <userinput>"eth1", "eth3"</userinput> ]
    },
    ...
}
  </screen>
439
440
441
442
  </para>
  <para>It is possible to use wildcard interface name (asterisk) concurrently
  with explicit interface names:
  <screen>
443
444
445
446
447
448
449
"Dhcp4": {
    "interfaces-config": {
        "interfaces": [ <userinput>"eth1", "eth3", "*"</userinput> ]
    },
    ...
}
  </screen>
450
It is anticipated that this form of usage will only be used when it is desired to
451
temporarily override a list of interface names and listen on all interfaces.
452
  </para>
453
  <para>Some deployments of the DHCP servers require that the servers listen
454
455
456
  on the interfaces with multiple IPv4 addresses configured. In these situations,
  the address to use can be selected by appending an IPv4 address to the interface
  name in the following manner:
457
458
459
460
461
462
463
464
  <screen>
"Dhcp4": {
    "interfaces-config": {
        "interfaces": [ <userinput>"eth1/10.0.0.1", "eth3/192.0.2.3"</userinput> ]
    },
    ...
}
  </screen>
465
  </para>
466

467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
  <para>If it is desired that the server listens on multiple IPv4 addresses assigned
  to the same interface, multiple addresses can be specified for this interface
  as in the example below:
  <screen>
"Dhcp4": {
    "interfaces-config": {
        "interfaces": [ <userinput>"eth1/10.0.0.1", "eth1/10.0.0.2"</userinput> ]
    },
    ...
}
  </screen>
  </para>

  <para>Alternatively, if the server should listen on all addresses for the particular
  interface, an interface name without any address should be specified.</para>

483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
  <para>Kea supports responding to directly connected clients which don't have
  an address configured on the interface yet. This requires that the server
  injects the hardware address of the destination into the data link layer
  of the packet being sent to the client. The DHCPv4 server utilizes the
  raw sockets to achieve this, and builds the entire IP/UDP stack for the
  outgoing packets. The down side of raw socket use, however, is that incoming
  and outgoing packets bypass the firewalls (e.g. iptables). It is also
  troublesome to handle traffic on multiple IPv4 addresses assigned to the
  same interface, as raw sockets are bound to the interface and advanced
  packet filtering techniques (e.g. using the BPF) have to be used to
  receive unicast traffic on the desired addresses assigned to the interface,
  rather than capturing whole traffic reaching the interface to which the raw
  socket is bound. Therefore, in the deployments where the server doesn't
  have to provision the directly connected clients and only receives the
  unicast packets from the relay agents, it is desired to configure the
  DHCP server to utilize the IP/UDP datagram sockets, instead of raw sockets.
  The following configuration demonstrates how this can be achieved:

  <screen>
"Dhcp4": {
    "interfaces-config": {
        "interfaces": [ <userinput>"eth1", "eth3"</userinput> ],
505
        "dhcp-socket-type": "udp"
506
507
508
509
    },
    ...
}
  </screen>
510
  The <command>dhcp-socket-type</command> specifies that the IP/UDP sockets will
511
  be opened on all interfaces on which the server listens, i.e. "eth1" and
512
  "eth3" in our case. If the <command>dhcp-socket-type</command> is set to
513
  <userinput>raw</userinput>, it configures the server to use raw sockets
514
  instead. If the <command>dhcp-socket-type</command> value is not specified, the
515
516
517
  default value <userinput>raw</userinput> is used.
  </para>

518
519
520
521
522
523
524
525
526
527
528
529
530
531
  <para>Using UDP sockets automatically disables the reception of brodcast
  packets from directly connected clients. This effectively means that the
  UDP sockets can be used for relayed traffic only. When using the raw sockets,
  both the traffic from the directly connected clients and the relayed traffic
  will be handled. Caution should be taken when configuring the server to open
  multiple raw sockets on the interface with several IPv4 addresses assigned.
  If the directly connected client sends the message to the brodcast address
  all sockets on this link will receive this message and multiple responses
  will be sent to the client. Hence, the configuration with multiple IPv4
  addresses assigned to the interface should not be used when the directly
  connected clients are operating on that link. To use a single address on
  such interface, the "interface-name/address" notation should be used.
  </para>

532
533
534
535
536
537
  <note>
    <para>Specifying the value <userinput>raw</userinput> as the socket type,
    doesn't guarantee that the raw sockets will be used! The use of raw sockets
    to handle the traffic from the directly connected clients is currently
    supported on Linux and BSD systems only. If the raw sockets are not
    supported on the particular OS, the server will issue a warning and
538
    fall back to use the IP/UDP sockets.</para>
539
  </note>
540
541
542
543
544
</section>

<section id="ipv4-subnet-id">
  <title>IPv4 Subnet Identifier</title>
  <para>
545
    The subnet identifier is a unique number associated with a particular subnet.
546
    In principle, it is used to associate clients' leases with their respective subnets.
547
    When a subnet identifier is not specified for a subnet being configured, it will
548
549
550
551
552
553
554
    be automatically assigned by the configuration mechanism. The identifiers
    are assigned from 1 and are monotonically increased for each subsequent
    subnet: 1, 2, 3 ....
  </para>
  <para>
    If there are multiple subnets configured with auto-generated identifiers and
    one of them is removed, the subnet identifiers may be renumbered. For example:
555
556
    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
557
558
    stored in the lease database for subnet 3 are now associated with
    subnet 4, something that may have unexpected consequences. It is planned
559
    to implement a mechanism to preserve auto-generated subnet ids in a
560
561
562
    future version of Kea.  However, the only remedy for this issue
    at present is to
    manually specify a unique identifier for each subnet.
563
  </para>
564
      <para>
565
	The following configuration will assign the specified subnet
566
567
	identifier to the newly configured subnet:

568
        <screen>
569
570
571
572
573
574
575
576
"Dhcp4": {
    "subnet4": [
        "subnet": "192.0.2.0/24",
        <userinput>"id": 1024</userinput>,
        ...
    ]
}
</screen>
577
578
    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
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
    identifier.
  </para>
    <!-- @todo: describe whether database needs to be updated after changing
      id -->
</section>

<section id="dhcp4-address-config">
  <title>Configuration of IPv4 Address Pools</title>
  <para>
    The essential role of DHCPv4 server is address assignment. 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 192.0.2.0/24 prefix. The Administrator of that network
    has decided that addresses from range 192.0.2.10 to 192.0.2.20 are going to
    be managed by the Dhcp4 server. Such a configuration can be achieved in the
    following way:
    <screen>
"Dhcp4": {
    <userinput>"subnet4": [
        "subnet": "192.0.2.0/24",
599
600
601
602
603
        "pools": [
	    {
	        "pool": "192.0.2.10 - 192.0.2.20"
            }
        ]</userinput>,
604
605
606
607
        ...
    ]
}</screen>

608
    Note that subnet is defined as a simple string, but the 'pools' parameter is
609
610
    actually a list of pools: for this reason, the pool definition is enclosed
    in square brackets, even though only one range of addresses is
611
    specified in this example.</para>
612

613
    <para>Each <command>pool</command> is a structure that contains the parameters
614
    that describe a single pool. Currently there is only one parameter,
615
616
617
618
    <command>pool</command>, which gives the range of addresses
    in the pool. Additional parameters will be added in future
    releases of Kea.</para>

619
620
621
622
623
624
625
626
627
    <para>It is possible to define more than one pool in a subnet: continuing
    the previous example, further assume that 192.0.2.64/26 should be also be
    managed by the server. It could be written as 192.0.2.64 to
    192.0.2.127. Alternatively, it can be expressed more simply as
    192.0.2.64/26. Both formats are supported by Dhcp4 and can be mixed in the
    pool list.  For example, one could define the following pools:
<screen>
"Dhcp4": {
    "subnet4": [
628
629
630
631
        <userinput>"pools": [
            { "pool": "192.0.2.10-192.0.2.20" },
            { "pool": "192.0.2.64/26" }
        ]</userinput>,
632
633
634
635
636
637
        ...
    ],
    ...
}
</screen>
    The number of pools is not limited, but for performance reasons it is recommended to
638
    use as few as possible. White space in pool definitions is ignored, so
639
    spaces before and after the hyphen are optional. They can be used to improve readability.
640
641
642
643
  </para>
  <para>
    The server may be configured to serve more than one subnet:
<screen>
644
645
646
647
"Dhcp4": {
    "subnet4": [
        {
            "subnet": "192.0.2.0/24",
648
            "pools": [ { "pool": "192.0.2.1 - 192.0.2.200" } ],
649
650
651
652
            ...
        },
        {
            "subnet": "192.0.3.0/24",
653
            "pools": [ { "pool": "192.0.3.100 - 192.0.3.200" } ],
654
655
656
657
            ...
        },
        {
            "subnet": "192.0.4.0/24",
658
            "pools": [ { "pool": "192.0.4.1 - 192.0.4.254" } ],
659
660
661
662
            ...
        }
    ]
}
663
664
665
666
</screen>
  </para>
  <para>
    When configuring a DHCPv4 server using prefix/length notation, please pay
667
668
    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
669
670
671
672
673
674
    address) and the last (typically broadcast address) address from that pool.
    In the aforementioned example of pool 192.0.3.0/24, both 192.0.3.0 and
    192.0.3.255 addresses may be assigned as well. This may be invalid in some
    network configurations. If you want to avoid this, please use the "min-max" notation.
  </para>
</section>
675
676
677
678

    <section id="dhcp4-std-options">
      <title>Standard DHCPv4 options</title>
      <para>
679
        One of the major features of the DHCPv4 server is to provide configuration
680
        options to clients.  Although there are several options that require
681
        special behavior, most options are sent by the server only if the client
682
        explicitly requests them.  The following example shows how to
683
        configure the addresses of DNS servers, which is one of the most frequently used
684
685
686
687
        options. Options specified in this way are considered global and apply
        to all configured subnets.

        <screen>
688
689
690
691
692
693
"Dhcp4": {
    "option-data": [
        {
           <userinput>"name": "domain-name-servers",
           "code": 6,
           "space": "dhcp4",
694
           "csv-format": true,
695
696
697
698
699
           "data": "192.0.2.1, 192.0.2.2"</userinput>
        },
        ...
    ]
}
700
701
702
</screen>
      </para>
    <para>
703
      The <command>name</command> parameter specifies the
704
705
      option name. For a complete list of currently supported names,
      see <xref linkend="dhcp4-std-options-list"/> below.
706
      The <command>code</command> parameter specifies the option code, which must match one of the
707
      values from that list. The next line specifies the option space, which must always
708
709
      be set to "dhcp4" as these are standard DHCPv4 options. For
      other option spaces, including custom option spaces, see <xref
710
      linkend="dhcp4-option-spaces"/>. The next line specifies the format in
711
712
      which the data will be entered: use of CSV (comma
      separated values) is recommended. The sixth line gives the actual value to
713
      be sent to clients. Data is specified as normal text, with
714
715
716
717
718
      values separated by commas if more than one value is
      allowed.
    </para>

    <para>
719
720
721
      Options can also be configured as hexadecimal values. If
      <command>csv-format</command> is
      set to false, option data must be specified as a hexadecimal string. The
722
723
      following commands configure the domain-name-servers option for all
      subnets with the following addresses: 192.0.3.1 and 192.0.3.2.
724
      Note that <command>csv-format</command> is set to false.
725
      <screen>
726
727
728
729
730
731
"Dhcp4": {
    "option-data": [
        {
            <userinput>"name": "domain-name-servers",
            "code": 6,
            "space": "dhcp4",
732
            "csv-format": false,
733
734
735
736
737
738
            "data": "C0 00 03 01 C0 00 03 02"</userinput>
        },
        ...
    ],
    ...
}</screen>
739
740
      </para>

741
742
743
744
745
746
      <para>
        Most of the parameters in the "option-data" structure are optional and
        can be omitted in some circumstances as discussed in the
        <xref linkend="dhcp4-option-data-defaults"/>.
      </para>

747
      <para>
748
        It is possible to specify or override options on a per-subnet basis.  If
749
750
751
752
753
754
755
756
757
758
759
760
        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
        (Dhcp4/option-data), rather you should set only subnet-specific values
        (Dhcp4/subnet[X]/option-data[Y]).
      </para>
      <para>
        The following commands override the global
        DNS servers option for a particular subnet, setting a single DNS
        server with address 192.0.2.3.
761
762
763
764
765
766
767
768
<screen>
"Dhcp4": {
    "subnet4": [
        {
            <userinput>"option-data": [
                {
                    "name": "domain-name-servers",
                    "code": 6,
Jeremy C. Reed's avatar
Jeremy C. Reed committed
769
                    "space": "dhcp4",
770
                    "csv-format": true,
771
772
773
774
775
776
777
778
779
780
781
                    "data": "192.0.2.3"
                },
                ...
            ]</userinput>,
            ...
        },
        ...
    ],
    ...
}
</screen>
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
      </para>

      <para>
        The currently supported standard DHCPv4 options are
        listed in <xref linkend="dhcp4-std-options-list"/>
        and <xref linkend="dhcp4-std-options-list-part2"/>.
        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"/>.
      </para>
      <para>
        Some options are designated as arrays, which means that more than one
        value is allowed in such an option. For example the option time-servers
        allows the specification of more than one IPv4 address, so allowing
797
        clients to obtain the addresses of multiple NTP servers.
798
799
800
801
802
803
804
805
806
807
808
809
810
      </para>
      <!-- @todo: describe record types -->

      <para>
        The <xref linkend="dhcp4-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 provide a definition yet. In order to use such options,
        a server administrator must create a definition as described in
        <xref linkend="dhcp4-custom-options"/> in the 'dhcp4' option space. This
        definition should match the option format described in the relevant
811
812
        RFC but the configuration mechanism will allow any option format as it has
        no means to validate the format at the moment.
813
814
815
816
817
818
819
      </para>

      <para>
        <table frame="all" id="dhcp4-std-options-list">
          <title>List of standard DHCPv4 options</title>
          <tgroup cols='4'>
          <colspec colname='name'/>
820
821
822
          <colspec colname='code' align='center'/>
          <colspec colname='type' align='center'/>
          <colspec colname='array' align='center'/>
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
          <thead>
            <row>
              <entry>Name</entry>
              <entry>Code</entry>
              <entry>Type</entry>
              <entry>Array?</entry>
            </row>
          </thead>
          <tbody>
<row><entry>subnet-mask</entry><entry>1</entry><entry>ipv4-address</entry><entry>false</entry></row>
<row><entry>time-offset</entry><entry>2</entry><entry>int32</entry><entry>false</entry></row>
<row><entry>routers</entry><entry>3</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>time-servers</entry><entry>4</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>name-servers</entry><entry>5</entry><entry>ipv4-address</entry><entry>false</entry></row>
<row><entry>domain-name-servers</entry><entry>6</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>log-servers</entry><entry>7</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>cookie-servers</entry><entry>8</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>lpr-servers</entry><entry>9</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>impress-servers</entry><entry>10</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>resource-location-servers</entry><entry>11</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>host-name</entry><entry>12</entry><entry>string</entry><entry>false</entry></row>
<row><entry>boot-size</entry><entry>13</entry><entry>uint16</entry><entry>false</entry></row>
<row><entry>merit-dump</entry><entry>14</entry><entry>string</entry><entry>false</entry></row>
<row><entry>domain-name</entry><entry>15</entry><entry>fqdn</entry><entry>false</entry></row>
<row><entry>swap-server</entry><entry>16</entry><entry>ipv4-address</entry><entry>false</entry></row>
<row><entry>root-path</entry><entry>17</entry><entry>string</entry><entry>false</entry></row>
<row><entry>extensions-path</entry><entry>18</entry><entry>string</entry><entry>false</entry></row>
<row><entry>ip-forwarding</entry><entry>19</entry><entry>boolean</entry><entry>false</entry></row>
<row><entry>non-local-source-routing</entry><entry>20</entry><entry>boolean</entry><entry>false</entry></row>
<row><entry>policy-filter</entry><entry>21</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>max-dgram-reassembly</entry><entry>22</entry><entry>uint16</entry><entry>false</entry></row>
<row><entry>default-ip-ttl</entry><entry>23</entry><entry>uint8</entry><entry>false</entry></row>
<row><entry>path-mtu-aging-timeout</entry><entry>24</entry><entry>uint32</entry><entry>false</entry></row>
<row><entry>path-mtu-plateau-table</entry><entry>25</entry><entry>uint16</entry><entry>true</entry></row>
<row><entry>interface-mtu</entry><entry>26</entry><entry>uint16</entry><entry>false</entry></row>
<row><entry>all-subnets-local</entry><entry>27</entry><entry>boolean</entry><entry>false</entry></row>
<row><entry>broadcast-address</entry><entry>28</entry><entry>ipv4-address</entry><entry>false</entry></row>
<row><entry>perform-mask-discovery</entry><entry>29</entry><entry>boolean</entry><entry>false</entry></row>
<row><entry>mask-supplier</entry><entry>30</entry><entry>boolean</entry><entry>false</entry></row>
<row><entry>router-discovery</entry><entry>31</entry><entry>boolean</entry><entry>false</entry></row>
<row><entry>router-solicitation-address</entry><entry>32</entry><entry>ipv4-address</entry><entry>false</entry></row>
<row><entry>static-routes</entry><entry>33</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>trailer-encapsulation</entry><entry>34</entry><entry>boolean</entry><entry>false</entry></row>
<row><entry>arp-cache-timeout</entry><entry>35</entry><entry>uint32</entry><entry>false</entry></row>
<row><entry>ieee802-3-encapsulation</entry><entry>36</entry><entry>boolean</entry><entry>false</entry></row>
<row><entry>default-tcp-ttl</entry><entry>37</entry><entry>uint8</entry><entry>false</entry></row>
869
<row><entry>tcp-keepalive-interval</entry><entry>38</entry><entry>uint32</entry><entry>false</entry></row>
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
<row><entry>tcp-keepalive-garbage</entry><entry>39</entry><entry>boolean</entry><entry>false</entry></row>

          </tbody>
          </tgroup>
        </table>
      </para>

      <para>
        <table frame="all" id="dhcp4-std-options-list-part2">
          <title>List of standard DHCPv4 options (continued)</title>
          <tgroup cols='4'>
          <colspec colname='name'/>
          <colspec colname='code'/>
          <colspec colname='type'/>
          <colspec colname='array'/>
          <thead>
            <row>
              <entry>Name</entry>
              <entry>Code</entry>
              <entry>Type</entry>
              <entry>Array?</entry>
            </row>
          </thead>
          <tbody>

<row><entry>nis-domain</entry><entry>40</entry><entry>string</entry><entry>false</entry></row>
<row><entry>nis-servers</entry><entry>41</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>ntp-servers</entry><entry>42</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>vendor-encapsulated-options</entry><entry>43</entry><entry>empty</entry><entry>false</entry></row>
<row><entry>netbios-name-servers</entry><entry>44</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>netbios-dd-server</entry><entry>45</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>netbios-node-type</entry><entry>46</entry><entry>uint8</entry><entry>false</entry></row>
<row><entry>netbios-scope</entry><entry>47</entry><entry>string</entry><entry>false</entry></row>
<row><entry>font-servers</entry><entry>48</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>x-display-manager</entry><entry>49</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>dhcp-requested-address</entry><entry>50</entry><entry>ipv4-address</entry><entry>false</entry></row>
<!-- Lease time should not be configured by a user.
<row><entry>dhcp-lease-time</entry><entry>51</entry><entry>uint32</entry><entry>false</entry></row>
-->
<row><entry>dhcp-option-overload</entry><entry>52</entry><entry>uint8</entry><entry>false</entry></row>
<!-- Message Type, Server Identifier and Parameter Request List should not be configured by a user.
<row><entry>dhcp-message-type</entry><entry>53</entry><entry>uint8</entry><entry>false</entry></row>
<row><entry>dhcp-server-identifier</entry><entry>54</entry><entry>ipv4-address</entry><entry>false</entry></row>
<row><entry>dhcp-parameter-request-list</entry><entry>55</entry><entry>uint8</entry><entry>true</entry></row>
-->
<row><entry>dhcp-message</entry><entry>56</entry><entry>string</entry><entry>false</entry></row>
<row><entry>dhcp-max-message-size</entry><entry>57</entry><entry>uint16</entry><entry>false</entry></row>
<!-- Renewal and rebinding time should not be configured by a user.
<row><entry>dhcp-renewal-time</entry><entry>58</entry><entry>uint32</entry><entry>false</entry></row>
<row><entry>dhcp-rebinding-time</entry><entry>59</entry><entry>uint32</entry><entry>false</entry></row>
-->
<row><entry>vendor-class-identifier</entry><entry>60</entry><entry>binary</entry><entry>false</entry></row>
<!-- Client identifier should not be configured by a user.
<row><entry>dhcp-client-identifier</entry><entry>61</entry><entry>binary</entry><entry>false</entry></row>
-->
<row><entry>nwip-domain-name</entry><entry>62</entry><entry>string</entry><entry>false</entry></row>
<row><entry>nwip-suboptions</entry><entry>63</entry><entry>binary</entry><entry>false</entry></row>
<row><entry>tftp-server-name</entry><entry>66</entry><entry>string</entry><entry>false</entry></row>
<row><entry>boot-file-name</entry><entry>67</entry><entry>string</entry><entry>false</entry></row>
<row><entry>user-class</entry><entry>77</entry><entry>binary</entry><entry>false</entry></row>
<row><entry>fqdn</entry><entry>81</entry><entry>record</entry><entry>false</entry></row>
<row><entry>dhcp-agent-options</entry><entry>82</entry><entry>empty</entry><entry>false</entry></row>
<row><entry>authenticate</entry><entry>90</entry><entry>binary</entry><entry>false</entry></row>
<row><entry>client-last-transaction-time</entry><entry>91</entry><entry>uint32</entry><entry>false</entry></row>
<row><entry>associated-ip</entry><entry>92</entry><entry>ipv4-address</entry><entry>true</entry></row>
<row><entry>subnet-selection</entry><entry>118</entry><entry>ipv4-address</entry><entry>false</entry></row>
<row><entry>domain-search</entry><entry>119</entry><entry>binary</entry><entry>false</entry></row>
<row><entry>vivco-suboptions</entry><entry>124</entry><entry>binary</entry><entry>false</entry></row>
<row><entry>vivso-suboptions</entry><entry>125</entry><entry>binary</entry><entry>false</entry></row>
          </tbody>
          </tgroup>
        </table>

      </para>
      <para>
        <table frame="all" id="dhcp-types">
          <title>List of standard DHCP option types</title>
          <tgroup cols='2'>
          <colspec colname='name'/>
          <colspec colname='meaning'/>
          <thead>
            <row><entry>Name</entry><entry>Meaning</entry></row>
          </thead>
          <tbody>
            <row><entry>binary</entry><entry>An arbitrary string of bytes, specified as a set of hexadecimal digits.</entry></row>
            <row><entry>boolean</entry><entry>Boolean value with allowed values true or false</entry></row>
            <row><entry>empty</entry><entry>No value, data is carried in suboptions</entry></row>
            <row><entry>fqdn</entry><entry>Fully qualified domain name (e.g. www.example.com)</entry></row>
            <row><entry>ipv4-address</entry><entry>IPv4 address in the usual dotted-decimal notation (e.g. 192.0.2.1)</entry></row>
            <row><entry>ipv6-address</entry><entry>IPv6 address in the usual colon notation (e.g. 2001:db8::1)</entry></row>
            <row><entry>record</entry><entry>Structured data that may comprise any types (except "record" and "empty")</entry></row>
            <row><entry>string</entry><entry>Any text</entry></row>
            <row><entry>uint8</entry><entry>8 bit unsigned integer with allowed values 0 to 255</entry></row>
963
            <row><entry>uint16</entry><entry>16 bit unsigned integer with allowed values 0 to 65535</entry></row>
964
965
966
967
968
969
970
971
972
            <row><entry>uint32</entry><entry>32 bit unsigned integer with allowed values 0 to 4294967295</entry></row>
          </tbody>
          </tgroup>
       </table>
      </para>
    </section>

    <section id="dhcp4-custom-options">
      <title>Custom DHCPv4 options</title>
973
974
975
976
      <para>Kea supports custom (non-standard) DHCPv4 options. Assume
      that we want to define a new DHCPv4 option called "foo" which
      will have code 222 and will convey a single unsigned 32 bit
      integer value. We can define such an option by using the
977
      following entry in the configuration file:
978
979
980
981
982
983
984
<screen>
"Dhcp4": {
    "option-def": [
        {
            <userinput>"name": "foo",
            "code": 222,
            "type": "uint32",
985
            "array": false,
986
987
988
989
990
991
992
993
            "record-types": "",
            "space": "dhcp4",
            "encapsulate": ""</userinput>
        }, ...
    ],
    ...
}
</screen>
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
      The <command>false</command> value of the <command>array</command>
      parameter determines that the option does NOT comprise an array of
      "uint32" values but rather a single value.  Two other parameters have been
      left blank: <command>record-types</command> and
      <command>encapsulate</command>.  The former specifies the comma separated
      list of option data fields if the option comprises a record of data
      fields. This should be non-empty if the <command>type</command> is set to
      "record". Otherwise it must be left blank. The latter parameter specifies
      the name of the option space being encapsulated by the particular
      option. If the particular option does not encapsulate any option space it
      should be left blank.  Note that the above set of comments define the
      format of the new option and do not set its values.
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
      </para>
      <note>
        <para>
          In the current release the default values are not propagated to the
          parser when the new configuration is being set. Therefore, all
          parameters must be specified at all times, even if their values are
          left blank.
        </para>
      </note>

      <para>Once the new option format is defined, its value is set
      in the same way as for a standard option. For example the following
      commands set a global value that applies to all subnets.
1019
1020
1021
1022
<screen>
"Dhcp4": {
    "option-data": [
        {
1023
            <userinput>"name": "foo",
1024
1025
            "code": 222,
            "space": "dhcp4",
1026
            "csv-format": true,
1027
1028
1029
1030
1031
1032
            "data": "12345"</userinput>
        }, ...
    ],
    ...
}
</screen>
1033
1034
1035
1036
1037
      </para>

      <para>New options can take more complex forms than simple use of
      primitives (uint8, string, ipv4-address etc): it is possible to
      define an option comprising a number of existing primitives.
1038
      Assume we want to define a new option that will consist of
1039
      an IPv4 address, followed by an unsigned 16 bit integer, followed by
1040
1041
1042
      a boolean value, followed by a text string. Such an option could
      be defined in the following way:
<screen>
1043
1044
1045
1046
1047
1048
1049
"Dhcp4": {
    "option-def": [
        {
            <userinput>"name": "bar",
            "code": 223,
            "space": "dhcp4",
            "type": "record",
1050
            "array": false,
1051
1052
1053
1054
1055
1056
            "record-types": "ipv4-address, uint16, boolean, string",
            "encapsulate": ""</userinput>
        }, ...
    ],
    ...
}
1057
</screen>
1058
      The <command>type</command> is set to "record" to indicate that the option contains
1059
      multiple values of different types.  These types are given as a comma-separated
1060
      list in the <command>record-types</command> field and should be those listed in <xref linkend="dhcp-types"/>.
1061
1062
1063
1064
      </para>
      <para>
      The values of the option are set as follows:
<screen>
1065
1066
1067
1068
1069
1070
"Dhcp4": {
    "option-data": [
        {
            <userinput>"name": "bar",
            "space": "dhcp4",
            "code": 223,
1071
            "csv-format": true,
1072
1073
1074
1075
1076
            "data": "192.0.2.100, 123, true, Hello World"</userinput>
        }
    ],
    ...
}</screen>
1077
      <command>csv-format</command> is set to <command>true</command> to indicate
1078
1079
1080
1081
      that the <command>data</command> field comprises a command-separated list
      of values.  The values in the <command>data</command> must correspond to
      the types set in the <command>record-types</command> field of the option
      definition.
1082
1083
     </para>
     <note>
1084
       <para>In the general case, boolean values are specified as <command>true</command> or
1085
1086
1087
1088
1089
       <command>false</command>, without quotes. Some specific boolean parameters may
       accept also <command>"true"</command>, <command>"false"</command>,
       <command>0</command>, <command>1</command>, <command>"0"</command> and
       <command>"1"</command>. Future Kea versions will accept all those values
       for all boolean parameters.</para>
1090
1091
1092
1093
     </note>
    </section>

    <section id="dhcp4-vendor-opts">
1094
      <title>DHCPv4 Vendor Specific Options</title>
1095
      <para>
1096
1097
1098
      Currently there are three option spaces defined: "dhcp4" (used by the DHCPv4 daemon)
      and "dhcp6" (for the DHCPv6 daemon); there is also "vendor-encapsulated-options-space",
      which is empty by default, but options
1099
1100
1101
1102
1103
1104
1105
1106
1107
      can be defined in it. Those options are called vendor-specific
      information options. The following examples show how to define
      an option "foo" with code 1 that consists of an IPv4 address, an
      unsigned 16 bit integer and a string. The "foo" option is conveyed
      in a vendor specific information option.
      </para>
      <para>
      The first step is to define the format of the option:
<screen>
1108
1109
1110
1111
1112
1113
1114
"Dhcp4": {
    "option-def": [
        {
            <userinput>"name": "foo",
            "code": 1,
            "space": "vendor-encapsulated-options-space",
            "type": "record",
1115
            "array": false,
1116
1117
1118
1119
1120
1121
            "record-types": "ipv4-address, uint16, string",
            "encapsulates": ""</userinput>
        }
    ],
    ...
}</screen>
1122
1123
1124
     (Note that the option space is set to "vendor-encapsulated-options-space".)
     Once the option format is defined, the next step is to define actual values
     for that option:
1125
1126
1127
1128
1129
1130
1131
<screen>
"Dhcp4": {
    "option-data": [
        {
            <userinput>"name": "foo"
            "space": "vendor-encapsulated-options-space",
            "code": 1,
1132
            "csv-format": true,
1133
1134
1135
1136
1137
            "data": "192.0.2.3, 123, Hello World"</userinput>
        }
    ],
    ...
}</screen>
1138
    We also set up a dummy value for "vendor-encapsulated-options", the option that conveys our sub-option "foo".
1139
    This is required else the option will not be included in messages sent to the client.
1140
1141
1142
1143
1144
1145
1146
<screen>
"Dhcp4": {
    "option-data": [
        {
            <userinput>"name": "vendor-encapsulated-options"
            "space": "dhcp4",
            "code": 43,
1147
            "csv-format": false,
1148
            "data": ""</userinput>
1149
1150
1151
1152
        }
    ],
    ...
}</screen>
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
      </para>

      <note>
        <para>
          With this version of Kea, the "vendor-encapsulated-options" option
          must be specified in the configuration although it has no configurable
          parameters. If it is not specified, the server will assume that it is
          not configured and will not send it to a client. In the future there
          will be no need to include this option in the configuration.
        </para>
      </note>

    </section>

    <section id="dhcp4-option-spaces">

1169
      <title>Nested DHCPv4 Options (Custom Option Spaces)</title>
1170
1171
1172
      <para>It is sometimes useful to define completely new option
      space. This is the case when user creates new option in the
      standard option space ("dhcp4 or "dhcp6") and wants this option
1173
      to convey sub-options. Since they are in a separate space,
1174
      sub-option codes will have a separate numbering scheme and may
1175
      overlap with the codes of standard options.
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
      </para>
      <para>Note that creation of a new option space when defining
      sub-options for a standard option is not required, because it is
      created by default if the standard option is meant to convey any
      sub-options (see <xref linkend="dhcp4-vendor-opts"/>).
      </para>
      <para>
      Assume that we want to have a DHCPv4 option called "container" with
      code 222 that conveys two sub-options with codes 1 and 2.
      First we need to define the new sub-options:
<screen>
1187
1188
1189
1190
1191
1192
1193
1194
"Dhcp4": {
    "option-def": [
        {
            <userinput>"name": "subopt1",
            "code": 1,
            "space": "isc",
            "type": "ipv4-address".
            "record-types": "",
1195
            "array": false,
1196
1197
1198
1199
1200
1201
1202
1203
            "encapsulate ""
        },
        {
            "name": "subopt2",
            "code": 2,
            "space": "isc",
            "type": "string",
            "record-types": "",
1204
            "array": false
1205
1206
1207
1208
1209
            "encapsulate": ""</userinput>
        }
    ],
    ...
}</screen>
1210
1211
1212
1213
1214
1215
1216
    Note that we have defined the options to belong to a new option space
    (in this case, "isc").
    </para>
    <para>
    The next step is to define a regular DHCPv4 option with our desired
    code and specify that it should include options from the new option space:
<screen>
1217
1218
1219
1220
1221
1222
1223
1224
"Dhcp4": {
    "option-def": [
        ...,
        {
            <userinput>"name": "container",
            "code": 222,
            "space": "dhcp4",
            "type": "empty",
1225
            "array": false,
1226
1227
1228
1229
1230
1231
            "record-types": "",
            "encapsulate": "isc"</userinput>
        }
    ],
    ...
}</screen>
1232
1233
1234
1235
1236
1237
1238
1239
    The name of the option space in which the sub-options are defined
    is set in the "encapsulate" field. The "type" field is set to "empty"
    to indicate that this option does not carry any data other than
    sub-options.
    </para>
    <para>
    Finally, we can set values for the new options:
<screen>
1240
1241
1242
1243
1244
1245
"Dhcp4": {
    "option-data": [
        {
            <userinput>"name": "subopt1",
            "space": "isc",
            "code": 1,
1246
            "csv-format": true,
1247
1248
1249
1250
1251
1252
            "data": "192.0.2.3"</userinput>
        },
        }
            <userinput>"name": "subopt2",
            "space": "isc",
            "code": 2,
1253
            "csv-format": true,
1254
1255
1256
1257
1258
1259
            "data": "Hello world"</userinput>
        },
        {
            <userinput>"name": "container",
            "space": "dhcp4",
            "code": 222,
1260
            "csv-format": true,
1261
1262
1263
1264
1265
            "data": ""</userinput>
        }
    ],
    ...
}
1266
1267
1268
</screen>
    Even though the "container" option does not carry any data except
    sub-options, the "data" field must be explicitly set to an empty value.
1269
    This is required because in the current version of Kea, the
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
    default configuration values are not propagated to the configuration parsers:
    if the "data" is not set the parser will assume that this
    parameter is not specified and an error will be reported.
    </para>
    <para>Note that it is possible to create an option which carries some data
    in addition to the sub-options defined in the encapsulated option space.  For example,
    if the "container" option from the previous example was required to carry an uint16
    value as well as the sub-options, the "type" value would have to be set to "uint16" in
    the option definition. (Such an option would then have the following
    data structure: DHCP header, uint16 value, sub-options.) The value specified
1280
1281
    with the "data" parameter &mdash; which should be a valid integer enclosed in quotes,
    e.g. "123" &mdash; would then be assigned to the uint16 field in the "container" option.
1282
1283
1284
    </para>
    </section>

1285
    <section id="dhcp4-option-data-defaults">
1286
      <title>Unspecified parameters for DHCPv4 option configuration</title>
1287
      <para>In many cases it is not required to specify all parameters for
1288
      an option configuration and the default values may be used. However, it is
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
      important to understand the implications of not specifing some of them
      as it may result in configuration errors. The list below explains
      the behavior of the server when a particular parameter is not explicitly
      specified:

      <itemizedlist>
        <listitem>
          <simpara><command>name</command> - the server requires an option name or
          option code to identify an option. If this parameter is unspecified, the
          option code must be specified.
          </simpara>
        </listitem>

        <listitem>
          <simpara><command>code</command> - the server requires an option name or
          option code to identify an option. This parameter may be left unspecified if
          the <command>name</command> parameter is specified. However, this also
          requires that the particular option has its definition (it is either a
          standard option or an administrator created a definition for the option
          using an 'option-def' structure), as the option definition associates an
          option with a particular name. It is possible to configure an option
          for which there is no definition (unspecified option format).
          Configuration of such options requires the use of option code.
          </simpara>
        </listitem>

        <listitem>
          <simpara><command>space</command> - if the option space is unspecified it
          will default to 'dhcp4' which is an option space holding DHCPv4 standard
          options.
          </simpara>
        </listitem>

        <listitem>
          <simpara><command>data</command> - if the option data is unspecified it
          defaults to an empty value. The empty value is mostly used for the
          options which have no payload (boolean options), but it is legal to specify
          empty values for some options which carry variable length data and which
          spec allows for the length of 0. For such options, the data parameter
          may be omitted in the configuration.</simpara>
        </listitem>

        <listitem>
          <simpara><command>csv-format</command> - if this value is not specified
          and the definition for the particular option exists, the server will assume
          that the option data is specified as a list of comma separated values to be
          assigned to individual fields of the DHCP option. If the definition
          does not exist for this option, the server will assume that the data
          parameter contains the option payload in the binary format (represented
          as a string of hexadecimal digits). Note that not specifying this
          parameter doesn't imply that it defaults to a fixed value, but
          the configuration data interpretation also depends on the presence
          of the option definition. An administrator must be aware if the
          definition for the particular option exists when this parameter
          is not specified. It is generally recommended to not specify this
          parameter only for the options for which the definition exists, e.g.
          standard options. Setting <command>csv-format</command> to an explicit
          value will cause the server to strictly check the format of the option
          data specified.
          </simpara>
        </listitem>
      </itemizedlist>
      </para>

    </section>

1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
    <section id="dhcp4-stateless-configuration">
      <title>Stateless Configuration of DHCPv4 clients</title>
      <para>The DHCPv4 server supports the stateless client configuration whereby the
      client has an IP address configured (e.g. using manual configuration) and only
      contacts the server to obtain other configuration parameters, e.g. DNS servers' addresses.
      In order to obtain the stateless configuration parameters the client sends the
      DHCPINFORM message to the server with the "ciaddr" set to the address that the
      client is currently using. The server unicasts the DHCPACK message to the
      client that includes the stateless configuration ("yiaddr" not set).
      </para>

      <para>The server will respond to the DHCPINFORM when the client is associated
      with the particular subnet defined in the server's configuration. The example
      subnet configuration will look like this:
        <screen>
"Dhcp4": {
    "subnet4": [
        {
            "subnet": "192.0.2.0/24"
1374
            "option-data": [ {
1375
1376
                "name": "domain-name-servers",
                "code": 6,
1377
                "data": "192.0.2.200,192.0.2.201",
1378
                "csv-format": true,
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
                "space": "dhcp4"
            } ]
        }
    ]
}</screen>
      </para>
      <para>This subnet specifies the single option which will be included in
      the DHCPACK message to the client in response to DHCPINFORM. Note that
      the subnet definition does not require the address pool configuration
      if it will be used solely for the stateless configuration.
      </para>

      <para>This server will associate the subnet with the client if one of
      the following conditions is met:
      <itemizedlist>
          <listitem>
            <simpara>The DHCPINFORM is relayed and the giaddr matches the
            configured subnet.</simpara>
          </listitem>
          <listitem>
            <simpara>The DHCPINFORM is unicast from the client and the ciaddr
            matches the configured subnet.</simpara>
          </listitem>
          <listitem>
            <simpara>The DHCPINFORM is unicast from the client, the ciaddr is
            not set but the source address of the IP packet matches the
            configured subnet.</simpara>
          </listitem>
          <listitem>
            <simpara>The DHCPINFORM is not relayed and the IP address on the
            interface on which the message is received matches the configured
            subnet.</simpara>
          </listitem>
      </itemizedlist>
      </para>
    </section>

1416
1417
1418
1419
    <section id="dhcp4-client-classifier">
      <title>Client Classification in DHCPv4</title>
      <note>
      <para>
1420
        The DHCPv4 server has been extended to support limited client classification.
1421
        Although the current capability is modest, it is expected to be expanded
1422
        in the future. However, it is envisaged that the majority of client classification
1423
1424
1425
1426
1427
        extensions will be using hooks extensions.
      </para>
      </note>
      <para>In certain cases it is useful to differentiate between different
      types of clients and treat them differently. The process of doing
1428
      classification is conducted in two steps. The first step is to assess an
1429
1430
      incoming packet and assign it to zero or more classes. This classification
      is currently simple, but is expected to grow in capability soon. Currently
1431
1432
1433
      the server checks whether an incoming packet includes the vendor class identifier
      option (60). If it does, the content of that option is prepended with
      &quot;VENDOR_CLASS_&quot; then it is interpreted as a class. For example,
1434
1435
1436
1437
      modern cable modems will send this option with value &quot;docsis3.0&quot;
      and as a result the packet will belong to class &quot;VENDOR_CLASS_docsis3.0&quot;.
      </para>

1438
      <para>It is envisaged that the client classification will be used for changing the
1439
      behavior of almost any part of the DHCP message processing, including assigning
1440
      leases from different pools, assigning different options (or different values of
1441
1442
1443
1444
1445
1446
1447
      the same options) etc. For now, there are only two mechanisms that are taking
      advantage of client classification: specific processing for cable modems and
      subnet selection.</para>

      <para>
        For clients that belong to the VENDOR_CLASS_docsis3.0 class, the siaddr
        field is set to the value of next-server (if specified in a subnet). If
1448
        there is a boot-file-name option specified, its value is also set in the
1449
1450
        file field in the DHCPv4 packet. For eRouter1.0 class, the siaddr is
        always set to 0.0.0.0. That capability is expected to be moved to
1451
        an external hook library that will be dedicated to cable modems.
1452
1453
1454
1455
1456
1457
1458
      </para>

      <para>
        Kea can be instructed to limit access to given subnets based on class information.
        This is particularly useful for cases where two types of devices share the
        same link and are expected to be served from two different subnets. The
        primary use case for such a scenario is cable networks. There are two
1459
        classes of devices: the cable modem itself, which should be handed a lease
1460
        from subnet A and all other devices behind the modem that should get a lease
1461
1462
1463
1464
1465
1466
1467
        from subnet B. That segregation is essential to prevent overly curious
        users from playing with their cable modems. For details on how to set up
        class restrictions on subnets, see <xref linkend="dhcp4-subnet-class"/>.
      </para>


    <section id="dhcp4-subnet-class">
1468
      <title>Limiting Access to IPv4 Subnet to Certain Classes</title>
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
      <para>
        In certain cases it beneficial to restrict access to certain subnets
        only to clients that belong to a given subnet. For details on client
        classes, see <xref linkend="dhcp4-client-classifier"/>. This is an
        extension of a previous example from <xref linkend="dhcp4-address-config"/>.
        Let's assume that the server is connected to a network segment that uses
        the 192.0.2.0/24 prefix. The Administrator of that network has decided
        that addresses from range 192.0.2.10 to 192.0.2.20 are going to be
        managed by the Dhcp4 server. Only clients belonging to client class
        VENDOR_CLASS_docsis3.0 are allowed to use this subnet. Such a
        configuration can be achieved in the following way:
        <screen>
1481
1482
1483
"Dhcp4": {
    "subnet4": [
        {
Jeremy C. Reed's avatar
Jeremy C. Reed committed
1484
            <userinput>"subnet": "192.0.2.0/24",
1485
            "pools": [ { "pool": "192.0.2.10 - 192.0.2.20" } ],
1486
1487
1488
1489
1490
            "client-class": "VENDOR_CLASS_docsis3.0"</userinput>
        }
    ],
    ...
}</screen>
1491
1492
1493
      </para>

      <para>
1494
        Care should be taken with client classification as it is easy for
1495
1496
1497
        clients that do not meet class criteria to be denied any service altogether.
      </para>
    </section>
1498
1499
    </section>

1500
1501
1502
    <section id="dhcp4-ddns-config">
      <title>Configuring DHCPv4 for DDNS</title>
      <para>
1503
      As mentioned earlier, kea-dhcp4 can be configured to generate requests to the
1504
      DHCP-DDNS server (referred to here as "D2" ) to update DNS entries.  These requests are known as
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
      NameChangeRequests or NCRs.  Each NCR contains the following information:
      <orderedlist>
      <listitem><para>
      Whether it is a request to add (update) or remove DNS entries
      </para></listitem>
      <listitem><para>
      Whether the change requests forward DNS updates (A records), reverse
      DNS updates (PTR records), or both.
      </para></listitem>
      <listitem><para>
      The FQDN, lease address, and DHCID
      </para></listitem>
      </orderedlist>
1518
      The parameters for controlling the generation of NCRs for submission to D2
1519
      are contained in the <command>dhcp-ddns</command> section of the kea-dhcp4 server
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
      configuration. The mandatory parameters for the DHCP DDNS configuration
      are <command>enable-updates</command> which is unconditionally
      required, and <command>qualifying-suffix</command> which has no
      default value and is required when <command>enable-updates</command>
      is set to <command>true</command>.

      The two (disabled and enabled) minimal DHCP DDNS configurations are:
<screen>
"Dhcp4": {
    "dhcp-ddns": {
        <userinput>"enable-updates": false</userinput>
    },
    ...
}
</screen>
      and for example: