From: Marcin Siodelski Date: Tue, 23 Aug 2016 17:07:03 +0000 (+0200) Subject: [4552] Documented reservations for siaddr, sname and file. X-Git-Tag: trac4631_base~4^2~2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b59bb07d9c672eedd8f7af6703938c8174c7adf6;p=thirdparty%2Fkea.git [4552] Documented reservations for siaddr, sname and file. --- diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml index e3bbab5b91..61355e9bb0 100644 --- a/doc/guide/dhcp4-srv.xml +++ b/doc/guide/dhcp4-srv.xml @@ -2822,6 +2822,35 @@ It is merely echoed by the server +
+ Reserving Next Server, Server Hostname and Boot File Name + BOOTP/DHCPv4 messages include "siaddr", "sname" and "file" fields. + Even though, DHCPv4 includes corresponding options, such as option 66 and + option 67, some clients may not support these options. Thus, server + administrators often use "siaddr", "sname" and "file" fields instead. + + With Kea, it is possible to make static reservations for these DHCPv4 + message fields: + + +{ + "subnet4": [ { + "reservations": [ + { + "hw-address": "aa:bb:cc:dd:ee:ff", + "next-server": "10.1.1.2", + "server-hostname": "server-hostname.example.org", + "boot-file-name": "/tmp/bootfile.efi" + } ] + } ] +} + + Note that those parameters can be specified in combination with + other parameters for a reservation, e.g. reserved IPv4 address. These + parameters are optional, i.e. a subset of them can specified, or all of + them can be omitted. +
+
Storing host reservations in MySQL or PostgreSQL