1DHCP6S.CONF(5)              BSD File Formats Manual             DHCP6S.CONF(5)
2

NAME

4     dhcp6s.conf — DHCPv6 server configuration file
5

SYNOPSIS

7     /etc/wide-dhcpv6/dhcp6s.conf
8

DESCRIPTION

10     The dhcp6s.conf file contains configuration information for KAME's DHCPv6
11     server, dhcp6s.  The configuration file consists of a sequence of state‐
12     ments terminated by a semi-colon (`;').  Statements are composed of
13     tokens separated by white space, which can be any combination of blanks,
14     tabs and newlines.  In some cases a set of statements is combined with a
15     pair of brackets, which is regarded as a single token.  Lines beginning
16     with ‘#’ are comments.
17

Interface specification

19     There are some statements that may or have to specify interface.  Inter‐
20     faces are specified in the form of "name unit", such as fxp0 and gif1.
21

Include statement

23     An include statement specifies another configuration file to be included.
24     The format of an include statement is as follows:
25     include "filename";
26             Where "filename" is the name (full path) of the file to be
27             included.
28

Option statement

30     An option statement specifies configuration parameters provided for every
31     client.  The format of the statement is as follows.
32     option option-name [option-value] ;
33             The following options can be specified in an option statement.
34             domain-name-servers dns-address [dns-addresses...];
35                     provides DNS server address(es).  Each dns-address must
36                     be a numeric IPv6 address.  Multiple server addresses can
37                     also be specified by a sequence of these statements.
38             domain-name "dns-name";
39                     provides a domain name of a DNS search path.  Multiple
40                     names in the path can be specified by a sequence of these
41                     statements.
42             ntp-servers ntp-address [ntp-addresses...];
43                     provides NTP server address(es).  Each ntp-address must
44                     be a numeric IPv6 address.  Multiple server addresses can
45                     also be specified by a sequence of these statements.
46             sip-server-address sip-server-address [sip-server-addresses...];
47                     provides SIP server address(es).  Each sip-server-address
48                     must be a numeric IPv6 address.  Multiple server
49                     addresses can also be specified by a sequence of these
50                     statements.
51             sip-server-domain-name "sip-server-domain-name";
52                     provides a domain name of a SIP server.  Multiple names
53                     in the path can be specified by a sequence of these
54                     statements.
55             nis-server-address nis-server-address [nis-server-addresses...];
56                     provides NIS server address(es).  Each nis-server-address
57                     must be a numeric IPv6 address.  Multiple server
58                     addresses can also be specified by a sequence of these
59                     statements.
60             nis-domain-name "nis-domain-name";
61                     provides a NIS domain name.  Multiple names in the path
62                     can be specified by a sequence of these statements.
63             nisp-server-address nisp-server-address
64                     [nisp-server-addresses...];
65                     provides NIS+ server address(es).  Each
66                     nisp-server-address must be a numeric IPv6 address.  Mul‐
67                     tiple server addresses can also be specified by a
68                     sequence of these statements.
69             nisp-domain-name "nisp-domain-name";
70                     provides a NIS+ domain name.  Multiple names in the path
71                     can be specified by a sequence of these statements.
72             bcmcs-server-address bcmcs-server-address
73                     [bcmcs-server-addresses...];
74                     provides BCMCS server address(es).  Each
75                     bcmcs-server-address must be a numeric IPv6 address.
76                     Multiple server addresses can also be specified by a
77                     sequence of these statements.
78             bcmcs-server-domain-name "bcmcs-server-domain-name";
79                     provides a domain name of a BCMCS server.  Multiple names
80                     in the path can be specified by a sequence of these
81                     statements.
82             refreshtime interval;
83                     specifies the refresh time of stateless information that
84                     does not have particular lease duration in seconds.  This
85                     option is only applicable to stateless configuration by
86                     information-request and reply exchanges.
87

Interface statement

89     An interface statement specifies configuration parameters on the inter‐
90     face.  The generic format of an interface statement is as follows:
91     interface interface { substatements };
92             The followings are possible substatements in an interface state‐
93             ment.
94             allow allow-options ;
95                     This statement specifies DHCPv6 options accepted by the
96                     server.  Currently only rapid-commit can be specified in
97                     an allow statement, which specifies the server to accept
98                     a rapid-commit option in solicit messages.
99             preference pref;
100                     This statement sets the server's preference value on the
101                     interface to the value pref.  The specified value will be
102                     contained in a preference option of advertise messages.
103                     The preference value must be a decimal integer and be
104                     between 0 and 255 (inclusive.)
105             address-pool pool pltime [vltime];
106                     This statement assigns an address pool pool to the inter‐
107                     face. When dhcp6s.conf receives a allocation request for
108                     an IA-NA, it assigns one IPv6 address from this pool.
109                     The specified pool name will be defined in a pool state‐
110                     ment.  Regarding the pltime and vltime , please see the
111                     explanation in the prefix substatement in host statement
112                     section.
113

Host statement

115     A host statement specifies configuration parameters for a particular
116     client.  The generic format of a host statement is as follows:
117     host name { substatements };
118             name is an arbitrary string.  It does not affect server's behav‐
119             ior but is provided for readability of log messages.  Possible
120             substatements are as follows.
121             duid ID;
122                     This statement defines the client's DHCP unique identi‐
123                     fier (DUID).  ID is a colon-separated hexadecimal
124                     sequence where each separated part must be composed of
125                     two hexadecimal values.  This statement is used to iden‐
126                     tify a particular host by the server and must be included
127                     in a host statement.
128             prefix ipv6-prefix pltime [vltime];
129                     This statement specifies an IPv6 prefix to be delegated
130                     to the client.  ipv6-prefix is a string representing a
131                     valid IPv6 prefix (see the example below).  pltime and
132                     vltime are preferred and valid lifetimes of the prefix,
133                     respectively.  When the latter is omitted, it will be set
134                     to the same value of pltime. A positive decimal number or
135                     a special string infinity can be specified as a lifetime.
136                     A decimal number provides the lifetime in seconds, while
137                     infinity means the corresponding lifetime never expires.
138                     When both lifetimes are specified, pltime must not be
139                     larger than vltime.  Multiple prefixes can be specified,
140                     each of which is given by a single prefix statement.  In
141                     that case, all or some of the specified prefixes will be
142                     delegated to the client, based on required parameters by
143                     the client.
144             address ipv6-address pltime [vltime];
145                     This statement specifies an IPv6 address to be assigned
146                     to the client.  Everything is same as prefix option,
147                     except that you do not need specify prefix length.
148             delayedkey keyname;
149                     This statement specifies a secret key shared with the
150                     client for the DHCPv6 delayed authentication protocol.
151                     keyname is a string that identifies a particular set of
152                     key parameters.  A separate keyinfo statement for keyname
153                     must be provided in the configuration file.  When this
154                     statement is specified and the client includes an authen‐
155                     tication option for the delayed authentication protocol
156                     in a Solicit message, dhcp6s will perform the authentica‐
157                     tion protocol for succeeding message exchanges.
158

Pool statement

160     A pool statement specifies an address pool for a particular interface.
161     The generic format of a pool statement is as follows:
162     pool name { substatements; };
163             name is an arbitrary string.  It does not affect server's behav‐
164             ior but is provided for readability of log messages.  Possible
165             substatements are as follows.
166             range min-addr to max-addr
167                     This substatement defines the range of addresses allo‐
168                     cated for the pool, i.e. from min-addr to max-addr.
169

Keyinfo statement

171     This statement defines a secret key shared with a client to authenticate
172     DHCPv6 messages.  The format and the description of this statement is
173     provided in dhcp6c.conf(5).  One important difference in the server con‐
174     figuration is, however, the keyname is referred from a host statement as
175     described above.
176

Examples

178     The followings are a sample configuration to provide a DNS server address
179     for every client as well as to delegate a permanent IPv6 prefix
180     2001:db8:1111::/48 to a client whose DUID is 00:01:00:01:aa:bb.
181
182     option domain-name-servers 2001:db8::35;
183
184     host kame {
185             duid 00:01:00:01:aa:bb;
186             prefix 2001:db8:1111::/48 infinity;
187     };
188
189     If a shared secret should be configured in both the server and the client
190     for DHCPv6 authentication, it would be specified in the configuration
191     file as follows:
192
193     keyinfo kame {
194             realm "kame.net";
195             keyid 1;
196             secret "5pvW2g48OHPvkYMJSw0vZA==";
197     };
198
199     And the host statement would be modified as follows:
200
201     host kame {
202             duid 00:01:00:01:aa:bb;
203             prefix 2001:db8:1111::/48 infinity;
204             delayedkey kame;
205     };
206

SEE ALSO

208     dhcp6c.conf(5) dhcp6s(8)
209

HISTORY

211     The dhcp6s.conf configuration file first appeared in the WIDE/KAME IPv6
212     protocol stack kit.
213
214KAME                             July 29, 2004                            KAME
Impressum