mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-08-30 05:27:55 +00:00
Code Issues Releases Wiki Activity

[#805,!5-p] Updated the ARM

Browse Source 
Updated the ARM and added a ChangeLog entry.
This commit is contained in:
Thomas Markwalder 2019-08-09 15:59:40 -04:00
parent 13e1bb4398
commit 3d097f24cc
3 changed files with 34 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
ChangeLog
View File

@ -1,3 +1,11 @@
1653. [security] tmark
Added a new parameter, "max-row-errors", to Memfile lease database
configuration for kea-dhcp4 and kea-dhcp6. This parameter can be
used to limit the number of rows discarded due to error during
lease file loading after which the server will abandon the effort
and exit. The default value of 0 disables the limit.
(Gitlab #805,!5-p git TBD)
1652. [security] tmark 1652. [security] tmark
Prevent the DHCP servers from asserting when malformed Prevent the DHCP servers from asserting when malformed
hostname or FQDN options are received. Now the servers will hostname or FQDN options are received. Now the servers will

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

@ -321,7 +321,14 @@ can be used to configure the memfile backend.
value of the ``lfc-interval`` is ``3600``. A value of 0 disables the value of the ``lfc-interval`` is ``3600``. A value of 0 disables the
LFC. LFC.
An example configuration of the memfile backend is presented below: - ``max-row-errors``: when the server loads a lease file, it is processed
row by row, each row contaning a single lease. If a row is flawed and
cannot be processed correctly the server will log it, discard the row,
and go on to the next row. This parameter can be used to set a limit on
the number of such discards that may occur after which the server will
abandon the effort and exit. The default value of 0 disables the limit
and allows the server to process the entire file, regardless of how many
rows are discarded.
:: ::
@ -330,14 +337,16 @@ An example configuration of the memfile backend is presented below:
"type": "memfile", "type": "memfile",
"persist": true, "persist": true,
"name": "/tmp/kea-leases4.csv", "name": "/tmp/kea-leases4.csv",
"lfc-interval": 1800 "lfc-interval": 1800,
"max-row-errors": 100
} }
} }
This configuration selects the ``/tmp/kea-leases4.csv`` as the storage This configuration selects the ``/tmp/kea-leases4.csv`` as the storage
for lease information and enables persistence (writing lease updates to for lease information and enables persistence (writing lease updates to
this file). It also configures the backend to perform a periodic cleanup this file). It also configures the backend to perform a periodic cleanup
of the lease file every 30 minutes. of the lease file every 30 minutes and sets the maximum number of row
errors to 100.
It is important to know how the lease file contents are organized to It is important to know how the lease file contents are organized to
understand why the periodic lease file cleanup is needed. Every time the understand why the periodic lease file cleanup is needed. Every time the

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

@ -296,6 +296,15 @@ can be used to configure the memfile backend.
default value of the ``lfc-interval`` is ``3600``. A value of 0 default value of the ``lfc-interval`` is ``3600``. A value of 0
disables the LFC. disables the LFC.
- ``max-row-errors``: when the server loads a lease file, it is processed
row by row, each row contaning a single lease. If a row is flawed and
cannot be processed correctly the server will log it, discard the row,
and go on to the next row. This parameter can be used to set a limit on
the number of such discards that may occur after which the server will
abandon the effort and exit. The default value of 0 disables the limit
and allows the server to process the entire file, regardless of how many
rows are discarded.
An example configuration of the memfile backend is presented below: An example configuration of the memfile backend is presented below:
:: ::
@ -305,14 +314,17 @@ An example configuration of the memfile backend is presented below:
"type": "memfile", "type": "memfile",
"persist": true, "persist": true,
"name": "/tmp/kea-leases6.csv", "name": "/tmp/kea-leases6.csv",
"lfc-interval": 1800 "lfc-interval": 1800,
"max-row-errors": 100
} }
} }
This configuration selects the ``/tmp/kea-leases6.csv`` as the storage This configuration selects the ``/tmp/kea-leases6.csv`` as the storage
for lease information and enables persistence (writing lease updates to for lease information and enables persistence (writing lease updates to
this file). It also configures the backend to perform a periodic cleanup this file). It also configures the backend to perform a periodic cleanup
of the lease file every 30 minutes. of the lease file every 30 minutes and sets th maximum number of row
errors to 100.
It is important to know how the lease file contents are organized to It is important to know how the lease file contents are organized to
understand why the periodic lease file cleanup is needed. Every time the understand why the periodic lease file cleanup is needed. Every time the