Commit 673861c2 authored by Marcin Siodelski's avatar Marcin Siodelski
Browse files

[5376] Documented how to override dhcp-server-identifier option.

parent 62f0e9a5
......@@ -1328,9 +1328,11 @@ This rather belong to the DDNS configuration
<!-- Message Type, Server Identifier and Parameter Request List should not be configured by a user.
<!-- Message Type should not be configured by a user.
<!-- Parameter Request List should not be configured by a user.
......@@ -3847,11 +3849,39 @@ i.e. it will assign increasing integer values starting from 1.</para>
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": "",
"option-data": [
"name": "dhcp-server-identifier",
"data": ""
<section id="dhcp4-subnet-selection">
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment