mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-08-29 04:57:52 +00:00
Code Issues Releases Wiki Activity

[master] Merge branch 'trac3684'

Browse Source
This commit is contained in:
Marcin Siodelski 2016-09-14 18:02:39 +02:00
commit 71d21eac51
24 changed files with 555 additions and 167 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/Makefile.am
View File

@ -13,6 +13,8 @@ nobase_dist_doc_DATA += examples/kea4/classify.json
nobase_dist_doc_DATA += examples/kea4/hooks.json
nobase_dist_doc_DATA += examples/kea4/leases-expiration.json
nobase_dist_doc_DATA += examples/kea4/multiple-options.json
nobase_dist_doc_DATA += examples/kea4/mysql-reservations.json
nobase_dist_doc_DATA += examples/kea4/pgsql-reservations.json
nobase_dist_doc_DATA += examples/kea4/reservations.json
nobase_dist_doc_DATA += examples/kea4/several-subnets.json
nobase_dist_doc_DATA += examples/kea4/single-subnet.json
@ -22,6 +24,8 @@ nobase_dist_doc_DATA += examples/kea6/classify.json
nobase_dist_doc_DATA += examples/kea6/hooks.json
nobase_dist_doc_DATA += examples/kea6/leases-expiration.json
nobase_dist_doc_DATA += examples/kea6/multiple-options.json
nobase_dist_doc_DATA += examples/kea6/mysql-reservations.json
nobase_dist_doc_DATA += examples/kea6/pgsql-reservations.json
nobase_dist_doc_DATA += examples/kea6/reservations.json
nobase_dist_doc_DATA += examples/kea6/several-subnets.json
nobase_dist_doc_DATA += examples/kea6/simple.json

8
doc/examples/kea4/backends.json
View File

@ -68,11 +68,7 @@
# "contact_points": "192.0.2.1,192.0.2.2,192.0.2.3"
# },
# Addresses will be assigned with valid lifetimes being 4000. Client
# is told to start renewing after 1000 seconds. If the server does not respond
# after 2000 seconds since the lease was granted, client is supposed
# to start REBIND procedure (emergency renewal that allows switching
# to a different server).
# Addresses will be assigned with a lifetime of 4000 seconds.
"valid-lifetime": 4000,
# Renew and rebind timers are commented out. This implies that options
@ -94,7 +90,7 @@
},
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{

2
doc/examples/kea4/classify.json
View File

@ -90,7 +90,7 @@
},
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{

15
doc/examples/kea4/leases-expiration.json
View File

@ -10,9 +10,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
@ -34,11 +35,7 @@
"unwarned-reclaim-cycles": 10
},
# Addresses will be assigned with valid lifetimes being 4000. Client
# is told to start renewing after 1000 seconds. If the server does not respond
# after 2000 seconds since the lease was granted, client is supposed
# to start REBIND procedure (emergency renewal that allows switching
# to a different server).
# Addresses will be assigned with a lifetime of 4000 seconds.
"valid-lifetime": 4000,
# The following list defines subnets. We have only one subnet
@ -53,7 +50,7 @@
},
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{

15
doc/examples/kea4/multiple-options.json
View File

@ -9,18 +9,15 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
# Addresses will be assigned with valid lifetimes being 4000. Client
# is told to start renewing after 1000 seconds. If the server does not respond
# after 2000 seconds since the lease was granted, client is supposed
# to start REBIND procedure (emergency renewal that allows switching
# to a different server).
# Addresses will be assigned with a lifetime of 4000 seconds.
"valid-lifetime": 4000,
# Renew and rebind timers are commented out. This implies that options
@ -58,7 +55,7 @@
},
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{

94
doc/examples/kea4/mysql-reservations.json Normal file
View File

@ -0,0 +1,94 @@
# This is an example configuration file for the DHCPv4 server in Kea.
# It contains configuration of the MySQL host database backend, used
# to retrieve reserved addresses, host names, DHCPv4 message fields
# and DHCP options from MySQL database.
{ "Dhcp4":
{
# Kea is told to listen on ethX interface only.
"interfaces-config": {
"interfaces": [ "ethX" ]
},
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
# Addresses will be assigned with a lifetime of 4000 seconds.
"valid-lifetime": 4000,
# Renew and rebind timers are commented out. This implies that options
# 58 and 59 will not be sent to the client. In this case it is up to
# the client to pick the timer values according to RFC2131. Uncomment the
# timers to send these options to the client.
# "renew-timer": 1000,
# "rebind-timer": 2000,
# Kea supports reservations by several different types of identifiers:
# hw-address (hardware/MAC address of the client), duid (DUID inserted by the
# client), client-id (client identifier inserted by the client) and circuit-id
# (circuit identifier inserted by the relay agent). When told to do so, Kea can
# check for all of those identifier types, but it takes a costly database lookup
# to do so. It is therefore useful from a performance perspective to use only
# the reservation types that are actually used in a given network.
# The example below is not optimal from a performance perspective, but it
# nicely showcases the host reservation capabilities. Please use the minimum
# set of identifier types used in your network.
"host-reservation-identifiers": [ "circuit-id", "hw-address", "duid", "client-id" ],
# Specify connection to the database holding host reservations. The type
# specifies that the MySQL database is used. user and password are the
# credentials used to connect to the database. host and name specify
# location of the host where the database instance is running, and the
# name of the database to use. The server processing a packet will first
# check if there are any reservations specified for this client in the
# reservations list, within the subnet (configuration file). If there are
# no reservations there, the server will try to retrieve reservations
# from this database.
"hosts-database": {
"type": "mysql",
"name": "kea",
"user": "kea",
"password": "kea",
"host": "localhost"
},
# Define a subnet with a single pool of dynamic addresses. Addresses from
# this pool will be assigned to clients which don't have reservations in the
# database. Subnet identifier is equal to 1. If this subnet is selected for
# the client, this subnet id will be used to search for the reservations
# within the database.
"subnet4": [
{
"pools": [ { "pool": "192.0.2.10 - 192.0.2.200" } ],
"subnet": "192.0.2.0/24",
"interface": "ethX",
"id": 1
}
]
},
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp4",
"output_options": [
{
"output": "stdout"
}
],
"severity": "INFO"
}
]
}
}

94
doc/examples/kea4/pgsql-reservations.json Normal file
View File

@ -0,0 +1,94 @@
# This is an example configuration file for the DHCPv4 server in Kea.
# It contains configuration of the PostgreSQL host database backend, used
# to retrieve reserved addresses, host names, DHCPv4 message fields
# and DHCP options from PostgreSQL database.
{ "Dhcp4":
{
# Kea is told to listen on ethX interface only.
"interfaces-config": {
"interfaces": [ "ethX" ]
},
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
# Addresses will be assigned with a lifetime of 4000 seconds.
"valid-lifetime": 4000,
# Renew and rebind timers are commented out. This implies that options
# 58 and 59 will not be sent to the client. In this case it is up to
# the client to pick the timer values according to RFC2131. Uncomment the
# timers to send these options to the client.
# "renew-timer": 1000,
# "rebind-timer": 2000,
# Kea supports reservations by several different types of identifiers:
# hw-address (hardware/MAC address of the client), duid (DUID inserted by the
# client), client-id (client identifier inserted by the client) and circuit-id
# (circuit identifier inserted by the relay agent). When told to do so, Kea can
# check for all of those identifier types, but it takes a costly database lookup
# to do so. It is therefore useful from a performance perspective to use only
# the reservation types that are actually used in a given network.
# The example below is not optimal from a performance perspective, but it
# nicely showcases the host reservation capabilities. Please use the minimum
# set of identifier types used in your network.
"host-reservation-identifiers": [ "circuit-id", "hw-address", "duid", "client-id" ],
# Specify connection to the database holding host reservations. The type
# specifies that the PostgreSQL database is used. user and password are the
# credentials used to connect to the database. host and name specify
# location of the host where the database instance is running, and the
# name of the database to use. The server processing a packet will first
# check if there are any reservations specified for this client in the
# reservations list, within the subnet (configuration file). If there are
# no reservations there, the server will try to retrieve reservations
# from this database.
"hosts-database": {
"type": "postgresql",
"name": "kea",
"user": "kea",
"password": "kea",
"host": "localhost"
},
# Define a subnet with a single pool of dynamic addresses. Addresses from
# this pool will be assigned to clients which don't have reservations in the
# database. Subnet identifier is equal to 1. If this subnet is selected for
# the client, this subnet id will be used to search for the reservations
# within the database.
"subnet4": [
{
"pools": [ { "pool": "192.0.2.10 - 192.0.2.200" } ],
"subnet": "192.0.2.0/24",
"interface": "ethX",
"id": 1
}
]
},
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp4",
"output_options": [
{
"output": "stdout"
}
],
"severity": "INFO"
}
]
}
}

15
doc/examples/kea4/reservations.json
View File

@ -9,18 +9,15 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
# Addresses will be assigned with valid lifetimes being 4000. Client
# is told to start renewing after 1000 seconds. If the server does not respond
# after 2000 seconds since the lease was granted, client is supposed
# to start REBIND procedure (emergency renewal that allows switching
# to a different server).
# Addresses will be assigned with a lifetime of 4000 seconds.
"valid-lifetime": 4000,
# Renew and rebind timers are commented out. This implies that options
@ -116,7 +113,7 @@
},
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{

22
doc/examples/kea4/several-subnets.json
View File

@ -10,16 +10,17 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
# Addresses will be assigned with the valid lifetimes being 4000.
# Client is told to start renewing after 1000 seconds. If the server
# does not respond after 2000 seconds since the lease was granted, client
# Addresses will be assigned with a lifetime of 4000 seconds.
# The client is told to start renewing after 1000 seconds. If the server
# does not respond within 2000 seconds of the lease being granted, client
# is supposed to start REBIND procedure (emergency renewal that allows
# switching to a different server).
"valid-lifetime": 4000,
@ -37,19 +38,18 @@
"subnet": "192.0.4.0/24" } ]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp4",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 99,
"severity": "DEBUG"
"severity": "INFO"
}
]
}

15
doc/examples/kea4/single-subnet.json
View File

@ -10,18 +10,15 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
# Addresses will be assigned with valid lifetimes being 4000. Client
# is told to start renewing after 1000 seconds. If the server does not respond
# after 2000 seconds since the lease was granted, client is supposed
# to start REBIND procedure (emergency renewal that allows switching
# to a different server).
# Addresses will be assigned with a lifetime of 4000 seconds.
"valid-lifetime": 4000,
# Renew and rebind timers are commented out. This implies that options
@ -43,7 +40,7 @@
},
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{

17
doc/examples/kea6/advanced.json
View File

@ -15,9 +15,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
@ -71,19 +72,19 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 99,
"severity": "DEBUG"
"debuglevel": 0,
"severity": "INFO"
}
]
}

6
doc/examples/kea6/backends.json
View File

@ -90,15 +90,15 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 0,

12
doc/examples/kea6/classify.json
View File

@ -74,19 +74,19 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 99,
"severity": "DEBUG"
],
"debuglevel": 0,
"severity": "INFO"
}
]
}

17
doc/examples/kea6/duid.json
View File

@ -30,9 +30,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
@ -50,7 +51,7 @@
# The following list defines subnets. Each subnet consists of at
# least subnet and pool entries.
"subnet6": [
"subnet6": [
{
"pools": [ { "pool": "2001:db8:1::/80" } ],
"subnet": "2001:db8:1::/64",
@ -59,17 +60,17 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
],
"debuglevel": 0,
"severity": "INFO"
}

17
doc/examples/kea6/leases-expiration.json
View File

@ -10,9 +10,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
@ -56,19 +57,19 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 99,
"severity": "DEBUG"
"debuglevel": 0,
"severity": "INFO"
}
]
}

17
doc/examples/kea6/multiple-options.json
View File

@ -9,9 +9,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
@ -49,19 +50,19 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 99,
"severity": "DEBUG"
"debuglevel": 0,
"severity": "INFO"
}
]
}

92
doc/examples/kea6/mysql-reservations.json Normal file
View File

@ -0,0 +1,92 @@
# This is an example configuration file for the DHCPv6 server in Kea.
# It contains configuration of the MySQL host database backend, used
# to retrieve reserved addresses, host names, DHCPv4 message fields
# and DHCP options from MySQL database.
{ "Dhcp6":
{
# Kea is told to listen on ethX interface only.
"interfaces-config": {
"interfaces": [ "ethX" ]
},
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
# This is pretty basic stuff, it has nothing to do with reservations.
"preferred-lifetime": 3000,
"valid-lifetime": 4000,
"renew-timer": 1000,
"rebind-timer": 2000,
# Kea supports two types of identifiers in DHCPv6: hw-address (hardware/MAC address
# of the client) and duid (DUID inserted by the client). When told to do so, Kea can
# check for each of these identifier types, but it takes a costly database lookup
# to do so. It is therefore useful from a performance perspective to use only
# the reservation types that are actually used in a given network.
"host-reservation-identifiers": [ "duid", "hw-address" ],
# Specify connection to the database holding host reservations. The type
# specifies that the MySQL database is used. user and password are the
# credentials used to connect to the database. host and name specify
# location of the host where the database instance is running, and the
# name of the database to use. The server processing a packet will first
# check if there are any reservations specified for this client in the
# reservations list, within the subnet (configuration file). If there are
# no reservations there, the server will try to retrieve reservations
# from this database.
"hosts-database": {
"type": "mysql",
"name": "kea",
"user": "kea",
"password": "kea",
"host": "localhost"
},
# Define a subnet with a pool of dynamic addresses and a pool of dynamic
# prefixes. Addresses and prefixes from those pools will be assigned to
# clients which don't have reservations in the database. Subnet identifier
# is equal to 1. If this subnet is selected for the client, this subnet
# id will be used to search for the reservations within the database.
"subnet6": [
{
"subnet": "2001:db8:1::/48",
"pools": [ { "pool": "2001:db8:1::/80" } ],
"pd-pools": [
{
"prefix": "2001:db8:1:8000::",
"prefix-len": 56,
"delegated-len": 64
}
],
"interface": "ethX",
"id": 1
}
]
},
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "stdout"
}
],
"debuglevel": 0,
"severity": "INFO"
}
]
}
}

92
doc/examples/kea6/pgsql-reservations.json Normal file
View File

@ -0,0 +1,92 @@
# This is an example configuration file for the DHCPv6 server in Kea.
# It contains configuration of the PostgreSQL host database backend, used
# to retrieve reserved addresses, host names, DHCPv4 message fields
# and DHCP options from PostgreSQL database.
{ "Dhcp6":
{
# Kea is told to listen on ethX interface only.
"interfaces-config": {
"interfaces": [ "ethX" ]
},
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
# This is pretty basic stuff, it has nothing to do with reservations.
"preferred-lifetime": 3000,
"valid-lifetime": 4000,
"renew-timer": 1000,
"rebind-timer": 2000,
# Kea supports two types of identifiers in DHCPv6: hw-address (hardware/MAC address
# of the client) and duid (DUID inserted by the client). When told to do so, Kea can
# check for each of these identifier types, but it takes a costly database lookup
# to do so. It is therefore useful from a performance perspective to use only
# the reservation types that are actually used in a given network.
"host-reservation-identifiers": [ "duid", "hw-address" ],
# Specify connection to the database holding host reservations. The type
# specifies that the PostgreSQL database is used. user and password are the
# credentials used to connect to the database. host and name specify
# location of the host where the database instance is running, and the
# name of the database to use. The server processing a packet will first
# check if there are any reservations specified for this client in the
# reservations list, within the subnet (configuration file). If there are
# no reservations there, the server will try to retrieve reservations
# from this database.
"hosts-database": {
"type": "postgresql",
"name": "kea",
"user": "kea",
"password": "kea",
"host": "localhost"
},
# Define a subnet with a pool of dynamic addresses and a pool of dynamic
# prefixes. Addresses and prefixes from those pools will be assigned to
# clients which don't have reservations in the database. Subnet identifier
# is equal to 1. If this subnet is selected for the client, this subnet
# id will be used to search for the reservations within the database.
"subnet6": [
{
"subnet": "2001:db8:1::/48",
"pools": [ { "pool": "2001:db8:1::/80" } ],
"pd-pools": [
{
"prefix": "2001:db8:1:8000::",
"prefix-len": 56,
"delegated-len": 64
}
],
"interface": "ethX",
"id": 1
}
]
},
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "stdout"
}
],
"debuglevel": 0,
"severity": "INFO"
}
]
}
}

17
doc/examples/kea6/reservations.json
View File

@ -12,9 +12,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
@ -109,19 +110,19 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 99,
"severity": "DEBUG"
"debuglevel": 0,
"severity": "INFO"
}
]
}

18
doc/examples/kea6/several-subnets.json
View File

@ -10,9 +10,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
@ -30,19 +31,19 @@
# The following list defines subnets. Each subnet consists of at
# least subnet and pool entries.
"subnet6": [
"subnet6": [
{ "pools": [ { "pool": "2001:db8:1::/80" } ],
"subnet": "2001:db8:1::/64" },
{ "pools": [ { "pool": "2001:db8:2::/80" } ],
"subnet": "2001:db8:2::/64" },
"subnet": "2001:db8:2::/64" },
{ "pools": [ { "pool": "2001:db8:3::/80" } ],
"subnet": "2001:db8:3::/64" },
{ "pools": [ { "pool": "2001:db8:4::/80" } ],
"subnet": "2001:db8:4::/64" } ]
},
# The following configures logging. It assumes that warning messages
# will be logged to stdout.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{
@ -52,7 +53,8 @@
"output": "stdout"
}
],
"severity": "WARN"
"debuglevel": 0,
"severity": "INFO"
}
]
}

23
doc/examples/kea6/simple.json
View File

@ -5,15 +5,16 @@
{ "Dhcp6":
{
{
# Kea is told to listen on ethX interface only.
"interfaces-config": {
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
@ -31,7 +32,7 @@
# The following list defines subnets. Each subnet consists of at
# least subnet and pool entries.
"subnet6": [
"subnet6": [
{
"pools": [ { "pool": "2001:db8:1::/80" } ],
"subnet": "2001:db8:1::/64",
@ -40,19 +41,19 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error and fatal) should be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 99,
"severity": "DEBUG"
],
"debuglevel": 0,
"severity": "INFO"
}
]
}

4
doc/guide/admin.xml
View File

@ -203,7 +203,7 @@
<entry>Host Reservations</entry>
<entry>no</entry>
<entry>yes</entry>
<entry>no</entry>
<entry>yes</entry>
<entry>no</entry>
</row>
@ -211,7 +211,7 @@
<entry>Options defined on per host basis</entry>
<entry>no</entry>
<entry>yes</entry>
<entry>no</entry>
<entry>yes</entry>
<entry>no</entry>
</row>

38
doc/guide/dhcp4-srv.xml
View File

@ -479,7 +479,7 @@ If a timeout is given though, it should be an integer greater than zero.
</section>
<section>
<title id="hosts4-storage">Hosts Storage</title>
<title id="hosts-storage4">Hosts Storage</title>
<para>Kea is also able to store information about host reservations in the
database. The hosts database configuration uses the same syntax as the lease
@ -2580,7 +2580,7 @@ It is merely echoed by the server
<!-- Host reservation is a large topic. There will be many subsections,
so it should be a section on its own. -->
<section id="host-reservation-v4">
<title>Host reservation in DHCPv4</title>
<title>Host Reservation in DHCPv4</title>
<para>There are many cases where it is useful to provide a configuration on
a per host basis. The most obvious one is to reserve specific, static
@ -2595,9 +2595,7 @@ It is merely echoed by the server
<para>Another example when the host reservations are applicable is when a host
that has specific requirements, e.g. a printer that needs additional DHCP options.
Yet another possible use case is to define unique names for hosts. Although not all
of the presented use cases are implemented yet, Kea software will support them in the
near future.</para>
Yet another possible use case is to define unique names for hosts.</para>
<para>Hosts reservations are defined as parameters for each subnet. Each host
has to be identified by an identifier, for example hardware/MAC address. There is an optional
@ -2605,9 +2603,10 @@ It is merely echoed by the server
element. Each element in that array is a structure, that holds information
about reservations for a single host. In particular, such a structure has
to have an identifier that uniquely identifies a host. In DHCPv4 context, such an
identifier is a hardware or MAC address. In most cases an address
will be specified. It is also possible to specify a hostname or host
specific options. Additional capabilities are planned.</para>
identifier is usually a hardware or MAC address. In most cases an IP address
will be specified. It is also possible to specify a hostname, host
specific options or fields carried within DHCPv4 message such as siaddr,
sname or file.</para>
<para>In Kea 1.0.0 it was only possible to create host reservations
using client's hardware address. Host reservations by client
@ -2677,7 +2676,7 @@ It is merely echoed by the server
additional check incurs performance penalty.</para>
<section id="reservation4-types">
<title>Address reservation types</title>
<title>Address Reservation Types</title>
<para>In a typical scenario there is an IPv4 subnet defined,
e.g. 192.0.2.0/24, with certain part of it dedicated for dynamic allocation
@ -2696,7 +2695,7 @@ It is merely echoed by the server
</section>
<section id="reservation4-conflict">
<title>Conflicts in DHCPv4 reservations</title>
<title>Conflicts in DHCPv4 Reservations</title>
<para>As the reservations and lease information are stored separately,
conflicts may arise. Consider the following series of events. The server
has configured the dynamic pool of addresses from the range of 192.0.2.10 to
@ -2774,7 +2773,7 @@ It is merely echoed by the server
</section>
<section id="reservation4-hostname">
<title>Reserving a hostname</title>
<title>Reserving a Hostname</title>
<para>When the reservation for a client includes the <command>hostname
</command>, the server will return this hostname to the client in
the Client FQDN or Hostname option. The server responds with the Client
@ -2842,7 +2841,7 @@ It is merely echoed by the server
</section>
<section id="reservation4-options">
<title>Including specific DHCPv4 options in reservations</title>
<title>Including Specific DHCPv4 Options in Reservations</title>
<para>Kea 1.1.0 introduced the ability to specify options on a
per host basis. The options follow the same rules as any other
options. These can be standard options (see <xref
@ -2987,17 +2986,20 @@ It is merely echoed by the server
</section>
<section id="reservations4-mysql-pgsql">
<title>Storing host reservations in MySQL or PostgreSQL</title>
<title>Storing Host Reservations in MySQL or PostgreSQL</title>
<para>
It is possible to store host reservations in MySQL or PostgreSQL. See <xref
linkend="hosts4-storage" /> for information on how to configure Kea to use
It is possible to store host reservations in MySQL or PostgreSQL database. See
<xref linkend="hosts-storage4"/> for information on how to configure Kea to use
reservations stored in MySQL or PostgreSQL. Kea does not provide any dedicated
tools for managing reservations in a database. See Kea wiki <ulink
url="http://kea.isc.org/wiki/HostReservationsHowTo" /> for detailed
information and examples of how reservations can be inserted into the
database.
</para>
<note><simpara>In Kea 1.1.0 maximum length of an option specified per host is
arbitrarily set to 4096 bytes.</simpara></note>
</section>
<section id="reservations4-cql">
@ -3042,7 +3044,7 @@ It is merely echoed by the server
dynamic pool. Therefore it can skip the reservation checks when dealing
with in-pool addresses, thus improving performance. Do not use this mode
if any of your reservations use in-pool address. Caution is advised when
using this setting. Kea 0.9.1 does not sanity check the reservations against
using this setting. Kea 1.1.0 does not sanity check the reservations against
<command>reservation-mode</command>. Misconfiguration may cause problems.
</simpara></listitem>
@ -3072,7 +3074,7 @@ It is merely echoed by the server
</para>
<para>Another aspect of the host reservations are different types of
identifiers. Currently (June 2016) Kea supports four types of identifiers
identifiers. Kea 1.1.0 supports four types of identifiers
(hw-address, duid, client-id and circuit-id), but more identifier types
are likely to be added in the future. This is beneficial from a
usability perspective. However, there is a drawback. For each incoming
@ -3108,7 +3110,7 @@ It is merely echoed by the server
<para>If not specified, the default value is:
<screen>
<userinput>"host-reservation-identifiers": [ "hw-address", "duid", "circuit-id" ]</userinput>
<userinput>"host-reservation-identifiers": [ "hw-address", "duid", "circuit-id", "client-id" ]</userinput>
</screen>
<!-- see CfgHostOperations::createConfig4() in
src/lib/dhcpsrv/cfg_host_operations.cc -->

68
doc/guide/dhcp6-srv.xml
View File

@ -2304,7 +2304,7 @@ should include options from the isc option space:
<!-- Host reservation is a large topic. There will be many subsections,
so it should be a section on its own. -->
<section id="host-reservation-v6">
<title>Host reservation in DHCPv6</title>
<title>Host Reservation in DHCPv6</title>
<para>There are many cases where it is useful to provide a configuration on
a per host basis. The most obvious one is to reserve specific, static IPv6
@ -2320,9 +2320,7 @@ should include options from the isc option space:
<para>Another example when the host reservations are applicable is when a host
that has specific requirements, e.g. a printer that needs additional DHCP options
or a cable modem needs specific parameters. Yet another possible use case for
host reservation is to define unique names for hosts. Although not all of
the presented use cases are implemented yet, Kea software will support them
in the near future.</para>
host reservation is to define unique names for hosts.</para>
<para>Hosts reservations are defined as parameters for each subnet. Each host
can be identified by either DUID or its hardware/MAC address. See
@ -2332,9 +2330,9 @@ should include options from the isc option space:
is a structure, that holds information about a single host. In
particular, such a structure has to have an identifier that
uniquely identifies a host. In DHCPv6 context, such an identifier
is a hardware (MAC) address or a DUID. Also, either one or more
addresses or prefixes should be specified. It is possible to
specify a hostname. Additional capabilities are planned.</para>
is usually a DUID, but can also be a hardware or MAC address. Also,
either one or more addresses or prefixes may be specified. It is
possible to specify a hostname and DHCPv6 options for a given host.</para>
<para>The following example shows how to reserve addresses and prefixes
for specific hosts:
@ -2358,11 +2356,11 @@ should include options from the isc option space:
},
{
"hw-address": "00:01:02:03:04:05",
"ip-addresses": [ "2001:db8:1::101" ]
"ip-addresses": [ "2001:db8:1::101, 2001:db8:1::102" ]
},
{
"duid": "01:02:03:04:05:06:07:08:09:0A",
"ip-addresses": [ "2001:db8:1::102" ],
"ip-addresses": [ "2001:db8:1::103" ],
"prefixes": [ "2001:db8:2:abcd::/64" ],
"hostname": "foo.example.com"
}
@ -2370,19 +2368,36 @@ should include options from the isc option space:
}
]
</screen>
This example makes 3 reservations. The first one reserves 2001:db8:1::100 address
for the client using DUID 01:02:03:04:05:0A:0B:0C:0D:0E. The second one
also reserves an address, but does so using MAC or hardware address, rather than
DUID. The third example is most advanced. It reserves an address, a prefix and
a hostname at the same time.
This example includes reservations for 3 different clients. First reservation
is made for the address 2001:db8:1::100 for a client using DUID
01:02:03:04:05:0A:0B:0C:0D:0E. Second reservation is made for two addresses
2001:db8:1::101 and 2001:db8:1::102 for a client using MAC address
00:01:02:03:04:05. Lastly, address 2001:db8:1::103 and prefix 2001:db8:2:abcd::/64
are reserved for a client using DUID 01:02:03:04:05:06:07:08:09:0A. This
last reservation also assigns a hostname to this client.
</para>
<para>Note that DHCPv6 allows for a single client to lease multiple addresses
and multiple prefixes at the same time. In the upcoming Kea releases, it will
be possible to have multiple addresses and prefixes reserved for a single
host. Therefore <command>ip-addresses</command> and <command>prefixes</command>
are plural and are actually arrays. As of 0.9.1 having more than one IPv6
address or prefix is only partially supported.</para>
and multiple prefixes at the same time. Therefore <command>ip-addresses</command>
and <command>prefixes</command> are plural and are actually arrays.
When the client sends multiple IA options (IA_NA or IA_PD), each reserved
address or prefix is assigned to individual IA of appropriate type. If
the number of IAs of specific type is lower than the number of reservations
of that type, the number of reserved addresses or prefixes assigned to the
client is equal to the number of IA_NAs or IA_PDs sent by the client, i.e.
some reserved addresses or prefixes are not assigned to the client. Though,
they still remain reserved for this client and the server will not assign
them to any other client. If the number of IAs of specific type sent by the
client is greater than the number of reserved addresses or prefixes, the
server will try to assign all reserved addresses or prefixes to the individual
IAs and dynamically allocate addresses or prefixes to remaining IAs. If the
server cannot assign a reserved address or prefix because it is in use,
the server will select next reserved address or prefix and try to assign it to
the client. If the server subsequently finds that there are no more reservations
that can be assigned to the client at the moment, the server will try to
assign leases dynamically.
</para>
<para>Making a reservation for a mobile host that may visit multiple subnets
requires a separate host definition in each subnet it is expected to visit.
@ -2390,8 +2405,8 @@ should include options from the isc option space:
address in a single subnet. It is a valid configuration, if such definitions
are specified in different subnets, though. The reservation for a given host
should include only one identifier, either DUID or hardware address. Defining
both for the same host is considered a configuration error, but as of 0.9.1
beta, it is not rejected.
both for the same host is considered a configuration error, but as of 1.1.0,
it is not rejected.
</para>
<para>Adding host reservation incurs a performance penalty. In principle,
@ -2416,7 +2431,7 @@ should include options from the isc option space:
<command>in-pool reservations</command>. In contrast, those that do not
belong to dynamic pools are called <command>out-of-pool
reservations</command>. There is no formal difference in the reservation
syntax. As of 0.9.1, both reservation types are handled
syntax. As of Kea 1.1.0, both reservation types are handled
uniformly. However, upcoming releases may offer improved performance if
there are only out-of-pool reservations as the server will be able to skip
reservation checks when dealing with existing leases. Therefore, system
@ -2425,7 +2440,7 @@ should include options from the isc option space:
</section>
<section id="reservation6-conflict">
<title>Conflicts in DHCPv6 reservations</title>
<title>Conflicts in DHCPv6 Reservations</title>
<para>As reservations and lease information are stored in different places,
conflicts may arise. Consider the following series of events. The server
has configured the dynamic pool of addresses from the range of 2001:db8::10
@ -2655,6 +2670,9 @@ should include options from the isc option space:
information and examples of how reservations can be inserted into the
database.
</para>
<note><simpara>In Kea 1.1.0 maximum length of an option specified per host is
arbitrarily set to 4096 bytes.</simpara></note>
</section>
<section id="reservations6-cql">
@ -2697,7 +2715,7 @@ should include options from the isc option space:
dynamic pool. Therefore it can skip the reservation checks when dealing
with in-pool addresses, thus improving performance. Do not use this mode
if any of your reservations use in-pool address. Caution is advised when
using this setting. Kea 0.9.1 does not sanity check the reservations against
using this setting. Kea 1.1.0 does not sanity check the reservations against
<command>reservation-mode</command>. Misconfiguration may cause problems.
</simpara></listitem>
@ -2727,7 +2745,7 @@ should include options from the isc option space:
</para>
<para>Another aspect of the host reservations are different types of
identifiers. Currently (June 2016) Kea supports two types of identifiers
identifiers. Kea 1.1.0 supports two types of identifiers
in DHCPv6: hw-address and duid, but more identifier types
are likely to be added in the future. This is beneficial from a
usability perspective. However, there is a drawback. For each incoming