simple.json 1.9 KB
Newer Older
1 2 3 4
// This is an example configuration file for DHCPv6 server in Kea.
// It's a basic scenario with one IPv6 subnet configured. It is
// assumed that one subnet (2001:db8:1::/64 is available directly
// over ethX interface.
Tomek Mrugalski's avatar
Tomek Mrugalski committed
5 6 7

{ "Dhcp6":

8
{
9
// Kea is told to listen on ethX interface only.
10
  "interfaces-config": {
11 12
    "interfaces": [ "ethX" ]
  },
Tomek Mrugalski's avatar
Tomek Mrugalski committed
13

14 15 16 17
// 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.
Tomek Mrugalski's avatar
Tomek Mrugalski committed
18
  "lease-database": {
19 20
      "type": "memfile",
      "lfc-interval": 3600
Tomek Mrugalski's avatar
Tomek Mrugalski committed
21 22
  },

23 24 25 26 27 28
// Addresses will be assigned with preferred and valid lifetimes
// being 3000 and 4000, respectively. 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).
Tomek Mrugalski's avatar
Tomek Mrugalski committed
29 30 31 32 33
  "preferred-lifetime": 3000,
  "valid-lifetime": 4000,
  "renew-timer": 1000,
  "rebind-timer": 2000,

34 35
// The following list defines subnets. Each subnet consists of at
// least subnet and pool entries.
36
  "subnet6": [
Tomek Mrugalski's avatar
Tomek Mrugalski committed
37
    {
38
      "pools": [ { "pool": "2001:db8:1::/80" } ],
Tomek Mrugalski's avatar
Tomek Mrugalski committed
39
      "subnet": "2001:db8:1::/64",
Tomek Mrugalski's avatar
Tomek Mrugalski committed
40
      "interface": "ethX"
Tomek Mrugalski's avatar
Tomek Mrugalski committed
41 42 43 44
    }
  ]
},

45 46
// The following configures logging. It assumes that messages with at
// least informational level (info, warn, error and fatal) should be
47 48
// logged to stdout. Alternatively, you can specify stderr here, a filename
// or 'syslog', which will store output messages via syslog.
Tomek Mrugalski's avatar
Tomek Mrugalski committed
49 50 51
"Logging": {
    "loggers": [
        {
Tomek Mrugalski's avatar
Tomek Mrugalski committed
52
            "name": "kea-dhcp6",
Tomek Mrugalski's avatar
Tomek Mrugalski committed
53 54
            "output_options": [
                {
55
                    "output": "stdout"
Tomek Mrugalski's avatar
Tomek Mrugalski committed
56
                }
57 58 59
            ],
            "debuglevel": 0,
            "severity": "INFO"
Tomek Mrugalski's avatar
Tomek Mrugalski committed
60 61 62 63 64 65
        }
    ]
}

}