From: Andrei Pavel Date: Thu, 29 Jun 2023 12:18:07 +0000 (+0300) Subject: [#2892] add a phrase about empty reservations for known clients X-Git-Tag: Kea-2.4.0~21 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6fda0044228a6fb247df76c5282e8ad333cefbe2;p=thirdparty%2Fkea.git [#2892] add a phrase about empty reservations for known clients --- diff --git a/doc/sphinx/arm/dhcp4-srv.rst b/doc/sphinx/arm/dhcp4-srv.rst index 47e4812681..afdafb7536 100644 --- a/doc/sphinx/arm/dhcp4-srv.rst +++ b/doc/sphinx/arm/dhcp4-srv.rst @@ -5921,7 +5921,9 @@ mechanism. The following example demonstrates this concept. It indicates a single IPv4 subnet and all clients will get an address from it. However, only known clients (those that -have reservations) will get their default router configured. +have reservations) will get their default router configured. Empty reservations +i.e. reservations that only have the identification criterion, can be +specifically useful in this regard of making the clients known. :: diff --git a/doc/sphinx/arm/dhcp6-srv.rst b/doc/sphinx/arm/dhcp6-srv.rst index 5b12ed49ff..86a5dfc0bb 100644 --- a/doc/sphinx/arm/dhcp6-srv.rst +++ b/doc/sphinx/arm/dhcp6-srv.rst @@ -5133,7 +5133,9 @@ mechanism. The following example demonstrates this concept. It indicates a single IPv6 subnet and all clients will get an address from it. However, only known clients (those that -have reservations) will get their default DNS server configured. +have reservations) will get their default DNS server configured. Empty reservations +i.e. reservations that only have the identification criterion, can be +specifically useful in this regard of making the clients known. ::