single-subnet.json 1.84 KB
Newer Older
1 2 3
// This is an example configuration file for the DHCPv4 server in Kea.
// It is a basic scenario with one IPv4 subnet configured. The subnet
// contains a single pool of dynamically allocated addresses.
4 5 6

{ "Dhcp4":

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

13 14 15 16
// 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.
17
  "lease-database": {
18 19
      "type": "memfile",
      "lfc-interval": 3600
20 21
  },

22
// Addresses will be assigned with a lifetime of 4000 seconds.
23
  "valid-lifetime": 4000,
24

25 26 27 28 29 30
// Renew and rebind timers are commented out. This implies that options
// 58 and 59 will not be sent to the client. In this case it is up to
// the client to pick the timer values according to RFC2131. Uncomment the
// timers to send these options to the client.
//  "renew-timer": 1000,
//  "rebind-timer": 2000,
31

32 33
// The following list defines subnets. We have only one subnet
// here. We tell Kea that it is directly available over local interface.
Tomek Mrugalski's avatar
Tomek Mrugalski committed
34
  "subnet4": [
Tomek Mrugalski's avatar
Tomek Mrugalski committed
35
    {
36
       "pools": [ { "pool":  "192.0.2.1 - 192.0.2.200" } ],
Tomek Mrugalski's avatar
Tomek Mrugalski committed
37
       "subnet": "192.0.2.0/24",
Tomek Mrugalski's avatar
Tomek Mrugalski committed
38 39
       "interface": "ethX"
    }
Tomek Mrugalski's avatar
Tomek Mrugalski committed
40
  ]
Tomek Mrugalski's avatar
Tomek Mrugalski committed
41 42
},

43 44
// The following configures logging. It assumes that messages with at
// least informational level (info, warn, error and fatal) should be
45 46
// 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
47 48 49
"Logging": {
    "loggers": [
        {
Tomek Mrugalski's avatar
Tomek Mrugalski committed
50
            "name": "kea-dhcp4",
Tomek Mrugalski's avatar
Tomek Mrugalski committed
51 52 53 54 55 56 57 58
            "output_options": [
                {
                    "output": "stdout"
                }
            ],
            "severity": "INFO"
        }
    ]
59 60 61
}

}