mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-08-30 13:37:55 +00:00
Code Issues Releases Wiki Activity

[#1836] addressed comments

Browse Source
This commit is contained in:
Razvan Becheriu
2021-06-25 17:15:55 +03:00
parent 22cc625725
commit 0721a05021
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/sphinx/arm/dhcp4-srv.rst
View File

@@ -5807,12 +5807,13 @@ has been received. A single server instance will use multiple server
identifiers if it is receiving queries on multiple interfaces. identifiers if it is receiving queries on multiple interfaces.
It is possible to override the default server identifier values by specifying It is possible to override the default server identifier values by specifying
the "dhcp-server-identifier" option. This option configuration is only supported the "dhcp-server-identifier" option. This option configuration is only
at the subnet, shared network, client class and global levels; it must not be supported at the subnet, shared network, client class and global levels. It
specified at the host reservation levels. must not be specified at the host reservation level.
When configuring the "dhcp-server-identifier" option at client class level, the When configuring the "dhcp-server-identifier" option at client class level, the
option must not use ``only-if-required`` flag, because this would cause the class must not set the ``only-if-required`` flag, because this class would not
evaluation of the class to be done after subnet selection only when required. be evaluated before the server determines if the received DHCP message should
be accepted for processing. Such classes are evaluated after subnet selection.
See :ref:`dhcp4-required-class` for details. See :ref:`dhcp4-required-class` for details.
The following example demonstrates how to override the server identifier The following example demonstrates how to override the server identifier