reservations.json 2.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172
  1. # This is an example configuration file for the DHCPv4 server in Kea.
  2. # It contains one subnet in which there are two static address reservations
  3. # for the clients identified by the MAC addresses.
  4. { "Dhcp4":
  5. {
  6. # Kea is told to listen on eth0 interface only.
  7. "interfaces": [ "eth0" ],
  8. # We need to specify lease type. As of May 2014, three backends are supported:
  9. # memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
  10. # any prior set up.
  11. "lease-database": {
  12. "type": "memfile"
  13. },
  14. # Addresses will be assigned with valid lifetimes being 4000. Client
  15. # is told to start renewing after 1000 seconds. If the server does not respond
  16. # after 2000 seconds since the lease was granted, client is supposed
  17. # to start REBIND procedure (emergency renewal that allows switching
  18. # to a different server).
  19. "valid-lifetime": 4000,
  20. # Renew and rebind timers are commented out. This implies that options
  21. # 58 and 59 will not be sent to the client. In this case it is up to
  22. # the client to pick the timer values according to RFC2131. Uncomment the
  23. # timers to send these options to the client.
  24. # "renew-timer": 1000,
  25. # "rebind-timer": 2000,
  26. # Define a subnet with two reservations for the 192.0.2.202 and
  27. # 192.0.2.100 address. Note that the latter is a reservation for the
  28. # address which is within the range of the pool of the dynamically
  29. # allocated address. The server will exclude this address from this
  30. # pool and only assign it to the client which has a reservation for
  31. # it.
  32. "subnet4": [
  33. {
  34. "pools": [ { "pool": "192.0.2.1 - 192.0.2.200" } ],
  35. "subnet": "192.0.2.0/24",
  36. "interface": "eth0",
  37. "reservations": [
  38. {
  39. "hw-address": "1a:1b:1c:1d:1e:1f",
  40. "ip-address": "192.0.2.202"
  41. },
  42. {
  43. "hw-address": "0a:0b:0c:0d:0e:0f",
  44. "ip-address": "192.0.2.100"
  45. }
  46. ]
  47. }
  48. ]
  49. },
  50. # The following configures logging. It assumes that messages with at least
  51. # informational level (info, warn, error) will will be logged to stdout.
  52. "Logging": {
  53. "loggers": [
  54. {
  55. "name": "kea-dhcp4",
  56. "output_options": [
  57. {
  58. "output": "stdout"
  59. }
  60. ],
  61. "severity": "INFO"
  62. }
  63. ]
  64. }
  65. }