From: Marcin Siodelski Date: Tue, 17 Oct 2017 09:45:44 +0000 (+0200) Subject: [5376] Documented how to override dhcp-server-identifier option. X-Git-Tag: trac5266_base~3^2~3^2~1 X-Git-Url: http://git.ipfire.org/gitweb/gitweb.cgi?a=commitdiff_plain;h=673861c246c04d7ffdd88855c6e749c976d12d26;p=thirdparty%2Fkea.git [5376] Documented how to override dhcp-server-identifier option. --- diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml index 8b8db50dec..9996ae474d 100644 --- a/doc/guide/dhcp4-srv.xml +++ b/doc/guide/dhcp4-srv.xml @@ -1328,9 +1328,11 @@ This rather belong to the DDNS configuration dhcp-lease-time51uint32falsetrue --> dhcp-option-overload52uint8falsefalse - dhcp-server-identifier54ipv4-addressfalsetrue + dhcp-message56stringfalsefalse @@ -3847,11 +3849,39 @@ i.e. it will assign increasing integer values starting from 1. received. A single server instance will use multiple server identifiers if it is receiving queries on multiple interfaces. + - Currently there is no mechanism to override the default server identifiers - by an administrator. In the future, the configuration mechanism will be used - to specify the custom server identifier. + It is possible to override default server identifier values by specifying + "dhcp-server-identifier" option. This option can be specified at any + configuration level, but it is recommended to only specify this option on + global, shared network or subnet level. Specifying this option on a class + or host reservation level will work only in cases when the specified + server identifier is an IP address assigned to one of the interfaces on + which the server is listening to DHCP queries. Otherwise, the server + will drop the messages with these server identifiers. The server will + accept messages including server identifiers specified on the global, + shared network and subnet level, even if they point to IP addresses not + assigned to any interfaces, on which the server is listening to the + DHCP queries. + + + The following example demonstrates how to override server identifier for + a subnet: + +"subnet4": [ + { + "subnet": "192.0.2.0/24", + "option-data": [ + { + "name": "dhcp-server-identifier", + "data": "10.2.5.76" + } + ], + ... + } +] +