From: Tomek Mrugalski Date: Fri, 19 Jul 2019 11:44:44 +0000 (+0200) Subject: [#644,!370] Manual apply of 330065ad5f60a3b9c2a0aa15bccdcb91e9341f4a to rst X-Git-Tag: Kea-1.6.1~10^2~45 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=618d26ae2aa8e9511825d835615507ff7fbfd57f;p=thirdparty%2Fkea.git [#644,!370] Manual apply of 330065ad5f60a3b9c2a0aa15bccdcb91e9341f4a to rst --- diff --git a/doc/sphinx/arm/classify.rst b/doc/sphinx/arm/classify.rst index 7427e332c6..8b8bae4f57 100644 --- a/doc/sphinx/arm/classify.rst +++ b/doc/sphinx/arm/classify.rst @@ -59,7 +59,7 @@ The classification process is conducted in several steps: following its client class or global (or, for option 43, last resort) definition. -5. When the incoming packet belongs the special DROP class it is +5. When the incoming packet belongs the special class, `DROP`, it is dropped and an informational message is logged with the packet information. diff --git a/doc/sphinx/arm/dhcp4-srv.rst b/doc/sphinx/arm/dhcp4-srv.rst index 6ae8b9cf86..13d51e5e4b 100644 --- a/doc/sphinx/arm/dhcp4-srv.rst +++ b/doc/sphinx/arm/dhcp4-srv.rst @@ -2564,8 +2564,8 @@ shared network or a subnet. The process of classification is conducted in five steps. The first step is to assess an incoming packet and assign it to zero or more classes. The second step is to choose a subnet, possibly based on the class -information. When the incoming packet is in the "DROP" -special class it is dropped and an information message logged. +information. When the incoming packet is in the special class, "DROP", +it is dropped and an information message logged. The next step is to evaluate class expressions depending on the built-in "KNOWN"/"UNKNOWN" classes after host reservation lookup, using them for pool selection and assigning classes from host diff --git a/doc/sphinx/arm/dhcp6-srv.rst b/doc/sphinx/arm/dhcp6-srv.rst index ae2471f5db..8b6cd50b12 100644 --- a/doc/sphinx/arm/dhcp6-srv.rst +++ b/doc/sphinx/arm/dhcp6-srv.rst @@ -2366,8 +2366,8 @@ shared network or a subnet. The process of classification is conducted in five steps. The first step is to assess an incoming packet and assign it to zero or more classes. The second step is to choose a subnet, possibly based on the class -information. When the incoming packet is in the "DROP" -special class it is dropped and an information message logged. +information. When the incoming packet is in the special class, "DROP, +it is dropped and an information message logged. The next step is to evaluate class expressions depending on the built-in "KNOWN"/"UNKNOWN" classes after host reservation lookup, using them for pool/pd-pool selection and assigning classes from host reservations. The