mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-09-04 07:55:18 +00:00
Code Issues Releases Wiki Activity

[#2892] document PD hints

Browse Source
This commit is contained in:
Andrei Pavel
2023-06-29 15:42:28 +03:00
parent 6fda004422
commit 7a375cf743
2 changed files with 17 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/sphinx/arm/dhcp4-srv.rst
View File

@@ -8040,7 +8040,9 @@ Address Allocation Strategies in DHCPv4
A DHCP server follows a complicated algorithm to select an IPv4 address for a client. A DHCP server follows a complicated algorithm to select an IPv4 address for a client.
It prefers assigning specific addresses requested by the client and the addresses for It prefers assigning specific addresses requested by the client and the addresses for
which the client has reservations. If the client requests no particular address and which the client has reservations.
If the client requests no particular address and
has no reservations, or other clients are already using any requested addresses, the server must has no reservations, or other clients are already using any requested addresses, the server must
find another available address within the configured pools. A server function called find another available address within the configured pools. A server function called
an "allocator" is responsible in Kea for finding an available address in such a case. an "allocator" is responsible in Kea for finding an available address in such a case.

17
doc/sphinx/arm/dhcp6-srv.rst
View File

@@ -7686,12 +7686,23 @@ MiNID.
.. _dhcp6_allocation_strategies: .. _dhcp6_allocation_strategies:
Address Allocation Strategies in DHCPv6 Allocation Strategies in DHCPv6
======================================= ===============================
A DHCP server follows a complicated algorithm to select a DHCPv6 lease for a client. A DHCP server follows a complicated algorithm to select a DHCPv6 lease for a client.
It prefers assigning specific addresses or delegated prefixes requested by the client It prefers assigning specific addresses or delegated prefixes requested by the client
and the ones for which the client has reservations. If the client requests no particular and the ones for which the client has reservations.
When the client requests a specific delegated prefix, there are a few steps that
:iscman:`kea-dhcp6` goes through to try to satisfy the request, in the following
order:
1. It searches for a lease that matches the requested prefix and prefix length.
2. It searches for a lease that matches the prefix length.
3. It searches for a lease with a larger address space (smaller prefix length).
4. It searches for a lease with a smaller address space (larger prefix length).
If the client requests no particular
lease and has no reservations, or other clients are already using any requested leases, the server must lease and has no reservations, or other clients are already using any requested leases, the server must
find another available lease within the configured pools. A server function called find another available lease within the configured pools. A server function called
an "allocator" is responsible in Kea for finding an available lease in such a case. an "allocator" is responsible in Kea for finding an available lease in such a case.