From 4d388fbfea989872cb6f00a3b221813a76557c0c Mon Sep 17 00:00:00 2001 From: Francis Dupont Date: Wed, 5 Dec 2018 13:49:05 +0100 Subject: [PATCH] [297-old-text-about-multiple-classes-guards] Updated doc about one class vs classes (allow/deny old/not implemented idea) --- doc/guide/dhcp4-srv.xml | 8 ++++---- doc/guide/dhcp6-srv.xml | 6 +++--- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml index 7befc88735..1973f0a369 100644 --- a/doc/guide/dhcp4-srv.xml +++ b/doc/guide/dhcp4-srv.xml @@ -4455,11 +4455,11 @@ as long as it is valid IPv4 address. the clients when client classification is in use, to assure that the desired subnet is selected for a given client type. - If a subnet is associated with some classes, only the clients - belonging to any of these classes can use this subnet. If there are no + If a subnet is associated with a class, only the clients + belonging to this class can use this subnet. If there are no classes specified for a subnet, any client connected to a given shared network can use this subnet. A common mistake is to assume that the - subnet including client classes is preferred over subnets without + subnet including a client class is preferred over subnets without client classes. Consider the following example: @@ -4505,7 +4505,7 @@ as long as it is valid IPv4 address. where cable modems should use one subnet and other devices should use another subnet within the same shared network. In this case it is required to apply classification on all subnets. The following example defines two - classes of devices. The subnet selection is made based on option 93 values. + classes of devices. The subnet selection is made based on option 93 values. { "client-classes": [ diff --git a/doc/guide/dhcp6-srv.xml b/doc/guide/dhcp6-srv.xml index 968eee6006..33075797a8 100644 --- a/doc/guide/dhcp6-srv.xml +++ b/doc/guide/dhcp6-srv.xml @@ -4093,11 +4093,11 @@ as long as it is valid IPv6 address. the clients when client classification is in use, to assure that the desired subnet is selected for a given client type. - If a subnet is associated with some classes, only the clients - belonging to any of these classes can use this subnet. If there are no + If a subnet is associated with a class, only the clients + belonging to this class can use this subnet. If there are no classes specified for a subnet, any client connected to a given shared network can use this subnet. A common mistake is to assume that the - subnet including client classes is preferred over subnets without + subnet including a client class is preferred over subnets without client classes. Consider the following example: -- 2.47.2