"hw-address": "1a:1b:1c:1d:1e:1f",
"client-classes": [ "VoIP" ]
} ],
- "interface": "ethX"
+ "interface": "ethX",
+ "require-client-classes": [ "second_subnet" ]
},
// The following list defines a subnet with pools. For some pools
-// This is an example configuration file for the DHCPv4 server in Kea.
+// This is an example configuration file for the DHCPv6 server in Kea.
// The purpose of this example is to showcase how clients can be classified.
{ "Dhcp6":
-// This is an example configuration file for the DHCPv4 server in Kea.
+// This is an example configuration file for the DHCPv6 server in Kea.
// The purpose of this example is to showcase how clients can be classified.
{ "Dhcp6":
"duid": "01:02:03:04:05:0A:0B:0C:0D:0E",
"client-classes": [ "cable-modems" ]
} ],
- "interface": "ethX"
+ "interface": "ethX",
+ "require-client-classes": [ "second_subnet" ]
},
// The following subnet contains a pool with a class constraint: only
// clients which belong to the class are allowed to use this pool.
</para></listitem>
<listitem><para>
Classes with matching expressions and not marked for later ("on
- 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.
+ request" or depending on the KNOWN builtin class) 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.
</para></listitem>
<listitem><para>
If a private or code 43 DHCPv4 option is received, decoding it
of the host reservation.
</para></listitem>
<listitem><para>
- Classes with matching expressions using directly or indirectly on
- the KNOWN builtin class and not marked for only when required
+ Classes with matching expressions using directly or indirectly
+ the KNOWN builtin class and not marked for later ("on 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.
</para></listitem>
<listitem><para>
- If needed, resources from pools are assigned, possibly based on the
- class information when some pools are reserved to class members.
+ If needed, addresses and prefixes from pools are assigned,
+ possibly based on the class information when some pools are
+ reserved to class members.
</para></listitem>
<listitem><para>
Evaluate classes marked as "required" in the order in which they
precedence: if you set an option-data in a subnet it takes
precedence over an option-data in a class. When you move the
option-data to a required class and require it in
- the subnet, a class evaluted earlier may take precedence.
+ the subnet, a class evaluated earlier may take precedence.
</para>
<para>
<para>Static class assignments, as shown above, can be used in conjunction
with classification using expressions. The "KNOWN" builtin class is
added to the packet and any class depending on it directly or indirectly
- and not only-if-required is evaluted.
+ and not only-if-required is evaluated.
</para>
<note>
precedence: if you set an option-data in a subnet it takes
precedence over an option-data in a class. When you move the
option-data to a required class and require it in
- the subnet, a class evaluted earlier may take precedence.
+ the subnet, a class evaluated earlier may take precedence.
</para>
<para>
<para>Static class assignments, as shown above, can be used in conjunction
with classification using expressions. The "KNOWN" builtin class is
added to the packet and any class depending on it directly or indirectly
- and not only-if-required is evaluted.
+ and not only-if-required is evaluated.
</para>
<note>