From: Tomek Mrugalski Date: Tue, 12 Jun 2018 14:54:30 +0000 (+0200) Subject: [5549a] Doc changes after review X-Git-Tag: 136-add-global-host-reservation-examples_base~4^2~2^2~1 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=bf0d433cf5900afa56fb9f513d60c7e4ce57862f;p=thirdparty%2Fkea.git [5549a] Doc changes after review --- diff --git a/doc/guide/classify.xml b/doc/guide/classify.xml index e61229deb6..7ce2cbe94f 100644 --- a/doc/guide/classify.xml +++ b/doc/guide/classify.xml @@ -101,9 +101,9 @@ Host reservations are looked for. If an identifier from the incoming packet matches a host reservation in the subnet or - shared network, the packet is associated with either the KNOWN - or the UNKNOWN builtin classes and all classes of the host - reservation. + shared network, the packet is associated with the KNOWN class + and all classes of the host reservation. If a reservation is not + found, the packet is assigned to UNKNOWN class. Classes with matching expressions using directly or indirectly @@ -111,7 +111,10 @@ request") evaluation are processed in the order they are defined in the configuration: the boolean expression is evaluated and when it returns true ("match") the incoming packet is associated - to the class. + to the class. The determination whether there is a reservation + for a given client is made after a subnet is selected. As such, it + is not possible to use KNOWN/UNKNOWN classes to select a shared + network or a subnet. If needed, addresses and prefixes from pools are assigned, diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml index c680e95861..5b48a92a20 100644 --- a/doc/guide/dhcp4-srv.xml +++ b/doc/guide/dhcp4-srv.xml @@ -2239,12 +2239,15 @@ It is merely echoed by the server - In a similar way a pool can be constrained to serve only known clients, - i.e. clients which have a reservation, using the build-n "KNOWN" or - "UNKNOWN" classes. - One can assign addresses to registered clients without giving a - different address per reservations, for instance when there is - not enough available addresses. + In a similar way a pool can be constrained to serve only known + clients, i.e. clients which have a reservation, using the + build-n "KNOWN" or "UNKNOWN" classes. One can assign addresses + to registered clients without giving a different address per + reservations, for instance when there is not enough available + addresses. The determination whether there is a reservation + for a given client is made after a subnet is selected. As such, it + is not possible to use KNOWN/UNKNOWN classes to select a shared + network or a subnet. diff --git a/doc/guide/dhcp6-srv.xml b/doc/guide/dhcp6-srv.xml index 731d48dd6c..9279e76e33 100644 --- a/doc/guide/dhcp6-srv.xml +++ b/doc/guide/dhcp6-srv.xml @@ -2237,12 +2237,15 @@ should include options from the isc option space: - In a similar way a pool can be constrained to serve only known clients, - i.e. clients which have a reservation, using the build-n "KNOWN" or - "UNKNOWN" classes. - One can assign addresses to registered clients without giving a - different address per reservations, for instance when there is - not enough available addresses. + In a similar way a pool can be constrained to serve only known + clients, i.e. clients which have a reservation, using the + build-n "KNOWN" or "UNKNOWN" classes. One can assign addresses + to registered clients without giving a different address per + reservations, for instance when there is not enough available + addresses. The determination whether there is a reservation + for a given client is made after a subnet is selected. As such, it + is not possible to use KNOWN/UNKNOWN classes to select a shared + network or a subnet.