Bonsoir
le serveur dhcp "isc-dhcp-server" est actuellement soumis a un gros bug sur stretch
j'ai remarqué un paquet free "kea" dans les dépots
extrait syslog
Oct 10 17:51:56 debian1 systemd[1]: Started ISC KEA IPv4 DHCP daemon.
Oct 10 17:51:56 debian1 kea-dhcp4[4763]: 2016-10-10 17:51:56.475 INFO [kea-dhcp4.dhcp4/4763] DHCP4_STARTING Kea DHCPv4 server version 1.0.0 starting
Oct 10 17:51:56 debian1 kea-dhcp4[4763]: 2016-10-10 17:51:56.477 INFO [kea-dhcp4.dhcpsrv/4763] DHCPSRV_CFGMGR_ADD_IFACE listening on interface enp6s0f1
Oct 10 17:51:56 debian1 kea-dhcp4[4763]: 2016-10-10 17:51:56.477 INFO [kea-dhcp4.dhcpsrv/4763] DHCPSRV_CFGMGR_SOCKET_TYPE_DEFAULT "dhcp-socket-type" not specified , using default socket type raw
Oct 10 17:51:56 debian1 kea-dhcp4[4763]: 2016-10-10 17:51:56.477 INFO [kea-dhcp4.dhcp4/4763] DHCP4_CONFIG_NEW_SUBNET a new subnet has been added to configuration: 192.168.10.0/24 with params: valid-lifetime=40$
Oct 10 17:51:56 debian1 kea-dhcp4[4763]: 2016-10-10 17:51:56.477 INFO [kea-dhcp4.dhcpsrv/4763] DHCPSRV_MEMFILE_DB opening memory file lease database: type=memfile universe=4
Oct 10 17:51:56 debian1 kea-dhcp4[4763]: 2016-10-10 17:51:56.478 INFO [kea-dhcp4.dhcpsrv/4763] DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file /var/lib/kea/kea-leases4.csv
Oct 10 17:51:56 debian1 kea-dhcp4[4763]: 2016-10-10 17:51:56.478 INFO [kea-dhcp4.dhcp4/4763] DHCP4_CONFIG_COMPLETE DHCPv4 server has completed configuration: added IPv4 subnets: 1; DDNS: disabled
le fichier de configuration basic
# This is a basic configuration for the Kea DHCPv4 sever.
# Subnet declarations are commented out and no interfaces are listed.
# Therefore, the servers will not listen or respond to any queries.
# The basic configuration must be extended to specify interfaces on
# which the servers should listen. Also, subnets and options must be
# declared.
{
# DHCPv4 configuration starts here.
"Dhcp4":
{
# Add names of interfaces to listen on.
"interfaces-config": {
"interfaces": [ "enp6s0f1" ]
},
# Use Memfile lease database backend to store leases in a CSV file.
"lease-database": {
"type": "memfile"
},
# Setup reclamation of the expired leases and leases affinity.
# Expired leases will be reclaimed every 10 seconds. Every 25
# seconds reclaimed leases, which have expired more than 3600
# seconds ago, will be removed. The limits for leases reclamation
# are 100 leases or 250 ms for a single cycle. A warning message
# will be logged if there are still expired leases in the
# database after 5 consecutive reclamation cycles.
"expired-leases-processing": {
"reclaim-timer-wait-time": 10,
"flush-reclaimed-timer-wait-time": 25,
"hold-reclaimed-time": 3600,
"max-reclaim-leases": 100,
"max-reclaim-time": 250,
"unwarned-reclaim-cycles": 5
},
# Global (inherited by all subnets) lease lifetime is mandatory parameter.
"valid-lifetime": 4000,
# Below an example of the simple subnet declaration. Uncomment to
# enable it. This is a list, denoted with [ ], of structure, denoted
# with { }. Each structure describes a single subnet and may have
# several parameters. One of those parameters is "pools" that is
# also a list of structures.
"subnet4": [
{ "subnet": "192.168.10.0/24",
"pools": [ { "pool": "192.168.10.20 - 192.168.10.50" } ] }
]
},
# Logging configuration starts here. It tells Kea servers to store
# all log messages (on severity INFO or more) in a file.
# debuglevel variable is used on DEBUG level only.
"Logging":
{
"loggers": [
{
"name": "kea-dhcp4",
"output_options": [
{
"output": "/var/log/kea-dhcp4.log"
}
],
"severity": "INFO",
"debuglevel": 0
},
]
}
}
personnellement je découvre et je pense un rapport avec bind10
quelqu un a testé ? avec une configuration plus poussé .
lien documentation => http://kea.isc.org/docs/kea-guide.html# … figuration
Dernière modification par anonyme (10-10-2016 17:10:06)