leases-expiration.json 2.2 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768
  1. # This is an example configuration file for the DHCPv4 server in Kea.
  2. # It provides parameters controlling processing of expired leases,
  3. # a.k.a. leases reclamation.
  4. { "Dhcp4":
  5. {
  6. # Kea is told to listen on ethX interface only.
  7. "interfaces-config": {
  8. "interfaces": [ "ethX" ]
  9. },
  10. # We need to specify the the database used to store leases. As of
  11. # September 2016, four database backends are supported: MySQL,
  12. # PostgreSQL, Cassandra, and the in-memory database, Memfile.
  13. # We'll use memfile because it doesn't require any prior set up.
  14. "lease-database": {
  15. "type": "memfile"
  16. },
  17. # The following parameters control processing expired leases. Expired leases
  18. # will be reclaimed periodically according to the "reclaim-timer-wait-time"
  19. # parameter. Reclaimed leases will be held in the database for 1800s to
  20. # facilitate lease affinity. After this period the leases will be removed.
  21. # The frequency of removal is controlled by the "flush-reclaimed-timer-wait-time"
  22. # parameter. The lease reclamation routine will process at most 500 leases
  23. # or will last for at most 100ms, during a single run. If there are still
  24. # some unreclaimed leases after 10 attempts, a warning message is issued.
  25. "expired-leases-processing": {
  26. "reclaim-timer-wait-time": 5,
  27. "hold-reclaimed-time": 1800,
  28. "flush-reclaimed-timer-wait-time": 10,
  29. "max-reclaim-leases": 500,
  30. "max-reclaim-time": 100,
  31. "unwarned-reclaim-cycles": 10
  32. },
  33. # Addresses will be assigned with a lifetime of 4000 seconds.
  34. "valid-lifetime": 4000,
  35. # The following list defines subnets. We have only one subnet
  36. # here. We tell Kea that it is directly available over local interface.
  37. "subnet4": [
  38. {
  39. "pools": [ { "pool": "192.0.2.1 - 192.0.2.200" } ],
  40. "subnet": "192.0.2.0/24",
  41. "interface": "ethX"
  42. }
  43. ]
  44. },
  45. # The following configures logging. It assumes that messages with at least
  46. # informational level (info, warn, error and fatal) should be logged to stdout.
  47. "Logging": {
  48. "loggers": [
  49. {
  50. "name": "kea-dhcp4",
  51. "output_options": [
  52. {
  53. "output": "stdout"
  54. }
  55. ],
  56. "severity": "INFO"
  57. }
  58. ]
  59. }
  60. }