// This is our basic configuration for the Kea DHCPv6 server. See section
// 9.2 DHCPv6 Server Configuration for detailed informations. the direct link
// for the stable version is https://kea.readthedocs.io/).
//
// This configuration file contains only DHCPv6 server's configuration.
// If configurations for other Kea services are also included in this file they
// are ignored by the DHCPv6 server.
//
// DHCPv6 configuration starts here. This section will be read by DHCPv6 server
// and will be ignored by other components.
{
  "Dhcp6": {
    // See section 9.2.4 Interface Configuration for more details:
    "interfaces-config": {
      "interfaces": [ "eth1" ]
    },
 
    // Kea supports control channel, which is a way to receive management
    // commands while the server is running. For detailed description,
    // see Sections 9.14.
    "control-socket": {
      "socket-type": "unix",
      "socket-name": "/var/lib/kea/kea6-ctrl-socket"
    },
    // Use Memfile lease database backend to store leases in a CSV file.
    //  See Section 9.2.2.1 Memfile - Basic Storage for Leases
    "lease-database": {
      "type": "memfile",
      "persist": true,
      "name": "/var/lib/kea/kea-leases6.csv",
      "lfc-interval": 3200,
      "max-row-errors": 100
    },
 
    // Setup reclamation of the expired leases and leases affinity.
    // See section 11. Lease Expiration for more and detailed informations.                                          
    "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 timers specified here apply to all subnets, unless there are
    // subnet specific values defined in particular subnets. See section
    // 9.2.1. Introduction.
    "valid-lifetime": 3600,
    "renew-timer": 1800,
    "rebind-timer": 3200,
    "preferred-lifetime": 3000,
 
    // Many additional parameters can be specified here. Alle datails will be
    // found in following sections:
    // - 9.2.11. Standard DHCPv6 Options
    // - 9.2.14. Custom DHCPv4 Options
    // - 9.2.15. DHCPv6 Vendor-Specific Options                                                                      
    // - 9.2.16. Nested DHCPv6 Options (Custom Option Spaces)                                                        
    // - 9.2.17. Unspecified Parameters for DHCPv6 Option Configuration
    //
    // For a complete list of options currently supported by Kea, see
    // Section 9.2.11 "Standard DHCPv6 Options". Kea also supports
    // vendor options (see Section 7.2.10) and allows users to define their
    // own custom options (see Section 7.2.9).
    "option-data": [
      // Domain-Name-Server:
      {
        "name": "dns-servers",
        "data": "fd00:0:0:7:10:0:10:110"
      },
 
      // Domain-Search-Liste:
      {
        "name": "domain-search",
        "data": "nausch.org"
      }
    ],

    // Finally, we list the subnets from which we will be leasing addresses.
    // See section 9.2.5 IPv6 Subnet Identifier and the following sections
    // for more details.
    "subnet6": [
      {
        "interface": "eth1",

        // This defines the whole subnet. Kea will use this information to
        // determine where the clients are connected. This is the whole
        // subnet in your network.
 
        // Subnet identifier should be unique for each subnet.
        // Subnet identifier for zone intra
        "id": 62,

        // This is mandatory parameter for each subnet.                                                              
        "subnet": "fd00:0:0:7::/64",

        // Pools define the actual part of your subnet that is governed
        // by Kea.
        "pools": [ { "pool": "fd00:0:0:7:10:0:10:300/120" } ],

        "option-data": [
          // You can specify additional options here that are subnet
          // specific. Also, you can override global options here.
          {
            "name": "dns-servers",
            "data": "fd00:0:0:7:10:0:10:110"
          },                                                                                                
          {
            "name": "sntp-servers",
            "data": "fd00:0:0:7:10:0:10:110"
          }                                                                                                

        ],

        // Host reservations can be defined for each subnet.
        // Note that reservations are subnet-specific in Kea. This is
        // different than ISC DHCP. Keep that in mind when migrating
        // your configurations.
        "reservations": [

          // This are the reservations for specific DUID matchings.
          // "MNSS (C7)"
          {
            "duid": "00:03:00:01:ac:1f:6b:00:d3:9b",
            "ip-addresses": [ "fd00:0:0:7:10:0:10:2" ],
            "hostname": "pml010002.intra.nausch.org"
          },

          // "WLAN Router Trendnet TEW-826DAP"
          {
            "duid": "00:03:00:01:d8:eb:97:33:48:62",
            "ip-addresses": [ "fd00:0:0:7:10:0:10:3" ],
            "hostname": "pnc010003.intra.nausch.org"
          },

          // "Netzwerkswitch TP-Link T1600G-52PS (UG)"
          {
            "duid": "00:03:00:01:64:66:b3:c9:98:7c",
            "ip-addresses": [ "fd00:0:0:7:10:0:10:6" ],
            "hostname": "pnc010006.intra.nausch.org"
          },

          // "Netzwerkswitch Netgear GS308E (DG)"
          {
            "duid": "00:03:00:01:6c:cd:d6:b8:52:be",
            "ip-addresses": [ "fd00:0:0:7:10:0:10:7" ],
            "hostname": "pnc010007.intra.nausch.org"
          },

          // "TecVDR (19 Zoll Tischgerät)"
          {
            "duid": "00:03:00:01:00:0b:6a:32:32:95",
            "ip-addresses": [ "fd00:0:0:7:10:0:10:100" ],
            "hostname": "pml010100.intra.nausch.org"
          },

          // "MNSS (ArchLinux)"
          {
            "duid": "00:02:00:00:ab:11:3e:4a:0e:2c:c1:5b:e2:64",
            "ip-addresses": [ "fd00:0:0:7:10:0:10:102" ],
            "hostname": "pml010102.intra.nausch.org"
          },

          // "ArchLinux FWC"
          {
            "duid": "00:03:00:01:52:54:00:41:11:02",
            "ip-addresses": [ "fd00::7:10:0:10:110" ],
            "hostname": "vml010110.intra.nausch.org"
          }
        ]
      }
    ],

    // Logging configuration starts here. Kea uses different loggers to log various
    //# activities. For details (e.g. names of loggers), see Chapter 19.
    "loggers": [
      {
        // This specifies the logging for kea-dhcp6 logger, i.e. all logs
        // generated by Kea DHCPv6 server.
        "name": "kea-dhcp6",
        "output_options": [
          {
            // Specifies the output file. There are several special values
            // supported:
            // - stdout (prints on standard output)
            // - stderr (prints on standard error)
            // - syslog (logs to syslog)
            // - syslog:name (logs to syslog using specified name)
            // Any other value is considered a name of the file
            "output": "syslog"                                                                             
          }
        ],

        // This specifies the severity of log messages to keep. Supported values
        // are: FATAL, ERROR, WARN, INFO, DEBUG
        "severity": "INFO",

        // If DEBUG level is specified, this value is used. 0 is least verbose,
        // 99 is most verbose. Be cautious, Kea can generate lots and lots
        // of logs if told to do so.
        "debuglevel": 0
      }
    ]
  }
}