<listitem><para>
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.
</para></listitem>
<listitem><para>
Classes with matching expressions using directly or indirectly
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.
</para></listitem>
<listitem><para>
If needed, addresses and prefixes from pools are assigned,
</para>
<para>
- 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.
</para>
<para>
</para>
<para>
- 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.
</para>
<para>