1ndpd.conf(4) File Formats ndpd.conf(4)
2
3
4
6 ndpd.conf - configuration file for IPv6 router autoconfiguration
7
9 /etc/inet/ndpd.conf
10
11
13 The ndpd.conf file contains configuration information for in.ndpd(1M).
14 On a host, this file does not need to exist or can be empty. The file
15 has one configuration entry per line; note that lines can be extended
16 with a backslash (\) followed by a NEWLINE. There are four forms of
17 configuration entries which are identified by the first field on the
18 line: ifdefault, prefixdefault, if, or prefix. The ifdefault and if
19 entries set interface configuration variables. The former establishes
20 the routing behavior for all interfaces, the latter sets per-interface
21 parameters. Any ifdefault entries must precede any if entries in the
22 file.
23
24
25 The prefixdefault and prefix entries control prefix configuration vari‐
26 ables. prefixdefault establishes the default behavior for all prefix
27 advertisements on all interfaces. The prefix keyword advertises per-
28 prefix information. Any prefixdefault entries must precede any prefix
29 entries in the file.
30
31
32 Each ifdefault entry is composed of a single line of the form:
33
34 ifdefault [ if-variable-name value ]*
35
36
37
38 Each if entry is composed of a single line of the form:
39
40 if interface [ if-variable-name value ]*
41
42
43
44 Each prefixdefault entry is composed of a single line of the form:
45
46 prefixdefault [ prefix-variable-name value ]*
47
48
49
50 Each prefix entry is composed of a single line of the form:
51
52 prefix prefix/prefix_length interface [ prefix-variable-name value ]*
53
54
55
56 Fields are separated by either SPACE or TAB characters. A `#' (number
57 sign) indicates the beginning of a comment. Characters up to the end of
58 the line are not interpreted by routines that search this file.
59
60 interface The name of a network interface, for example,
61 eri0.
62
63
64 prefix An IPv6 address in standard hexadecimal nota‐
65 tion, for example, fec0:0:0:1::0.
66
67
68 prefix_length A number between 0 and 128.
69
70
71 if-variable-name An interface variable. Below is the list of
72 interface variables applicable to routers only
73 along with their default values and units as
74 discussed in RFC 2461 and RFC 2462. The Tmp*
75 variables apply to hosts and routers. The Tmp*
76 variables configure temporary address function‐
77 ality as defined in RFC 3041.
78
79 Variable Name Default Unit
80
81 AdvSendAdvertisements false Boolean
82 DupAddrDetectTransmits 1 Counter
83 MaxRtrAdvInterval 600 Seconds
84 MinRtrAdvInterval 200 Seconds
85 AdvManagedFlag false Boolean
86 AdvOtherConfigFlag false Boolean
87 AdvLinkMTU 0 Bytes
88 AdvReachableTime 0 Milliseconds
89 AdvRetransTimer 0 Milliseconds
90 AdvCurHopLimit see below Counter
91 AdvDefaultLifetime 1800 Seconds
92
93
94 These variables are described as follows:
95
96 AdvSendAdvertisements Indicates whether the
97 node should send out
98 advertisements and
99 respond to router
100 solicitations. You
101 need to explicitly
102 configure this value
103 to turn on router
104 advertisement func‐
105 tions.
106
107
108 DupAddrDetectTransmits Defines the number of
109 consecutive Neighbor
110 Solicitation messages
111 that the Neighbor
112 Discovery protocol
113 should send during
114 Duplicate Address
115 Detection of the
116 local node's address.
117
118
119 MaxRtrAdvInterval Specifies the maximum
120 time to wait between
121 sending unsolicited
122 multicast advertise‐
123 ments.
124
125
126 MinRtrAdvInterval Specifies the minimum
127 amount of time to
128 wait between sending
129 unsolicited multicast
130 advertisements.
131
132
133 AdvManagedFlag Indicates the value
134 to be placed in the
135 "Manage address con‐
136 figuration" flag in
137 the Router Advertise‐
138 ment. This flag
139 causes hosts to run
140 DHCPv6 to acquire
141 addresses and other
142 configuration infor‐
143 mation. This flag
144 causes hosts to run
145 DHCPv6 to acquire
146 configuration infor‐
147 mation, but only if
148 AdvManagedFlag is not
149 set.
150
151
152 AdvOtherConfigFlag Indicates the value
153 to be placed in the
154 "Other stateful con‐
155 figuration"flag in
156 the Router Advertise‐
157 ment.
158
159
160 AdvLinkMTU Specifies an MTU
161 value to be sent by
162 the router. The
163 default of zero indi‐
164 cates that the router
165 does not specify MTU
166 options.
167
168
169 AdvReachableTime Specifies the value
170 in the Reachable Time
171 field in the adver‐
172 tisement messages
173 sent by the router.
174
175
176 AdvRetransTimer Specifies the value
177 in the Retrans Timer
178 field in the adver‐
179 tisement messages
180 sent by the router.
181
182
183 AdvCurHopLimit Specifies the value
184 to be placed in the
185 current hop limit
186 field in the adver‐
187 tisement messages
188 sent by the router.
189 The default is the
190 current diameter of
191 the Internet.
192
193
194 AdvDefaultLifetime Specifies the default
195 lifetime of the
196 router advertise‐
197 ments.
198
199 Listed below is the interface variable that
200 applies to both hosts and routers.
201
202 Variable Name Default Unit
203
204 StatefulAddrConf true Boolean
205 StatelessAddrConf true Boolean
206 TmpAddrsEnabled false Boolean
207 TmpValidLifetime 604800 Seconds
208 (1 week)
209 TmpPreferredLifetime 86400 Seconds
210 (1 day)
211 TmpRegenAdvance 5 Seconds
212 TmpMaxDesyncFactor 600 Seconds
213
214
215
216 StatefulAddrConf Controls whether the
217 system configures its
218 IPv6 addresses by means
219 of the Stateful Address
220 Autoconfiguration mech‐
221 anism, also known as
222 DHCPv6, as described in
223 RFC 3315. If enabled
224 (the default), hosts
225 automatically run
226 DHCPv6 based on the
227 "managed" and "other"
228 flags sent by routers.
229 If disabled, in.ndpd
230 will not invoke DHCPv6
231 automatically. DHCPv6
232 can still be invoked
233 manually by using
234 ifconfig(1M), in which
235 case in.ndpd automati‐
236 cally sets the prefix
237 length as needed.
238
239
240 StatelessAddrConf Controls whether the
241 system configures its
242 IPv6 addresses by means
243 of the Stateless
244 Address Autoconfigura‐
245 tion mechanism
246 described in RFC 2462.
247 If enabled hosts (the
248 default) autoconfigure
249 addresses based on pre‐
250 fixes advertised by
251 routers, routers will
252 only autoconfigure
253 addresses based on the
254 prefixes they advertise
255 themselves. In other
256 words, even when
257 enabled, routers do not
258 autoconfigure addresses
259 based on prefixes that
260 other routers adver‐
261 tise. If you specify
262 false for this vari‐
263 able, then the address
264 must be configured man‐
265 ually.
266
267
268 TmpAddrsEnabled Indicates whether a
269 temporary address
270 should be created for
271 all interfaces or for a
272 particular interface of
273 a node.
274
275
276 TmpValidLifetime Sets the valid lifetime
277 for a temporary
278 address.
279
280
281 TmpPreferredLifetime Sets the preferred
282 lifetime of a temporary
283 address.
284
285
286 TmpRegenAdvance Specifies the lead time
287 in advance of address
288 deprecation for genera‐
289 tion of a new temporary
290 address.
291
292
293 TmpMaxDesyncFactor Sets the upper bound on
294 the DesyncFactor, which
295 is a random value that
296 is used to shorten the
297 preferred lifetime so
298 that clients do not
299 regenerate an address
300 at the same time.
301
302
303
304 prefix-variable-name A prefix variable as discussed in RFC 2461 and
305 RFC 2462. The following lists the each inter‐
306 face variable and its default value and unit:
307
308
309
310
311 ┌─────────────────────────────┬────────────────┬───────────────┐
312 │ Variable Name │ Default │ Unit │
313 ├─────────────────────────────┼────────────────┼───────────────┤
314 │AdvValidLifetime │2592000 │Seconds │
315 ├─────────────────────────────┼────────────────┼───────────────┤
316 │AdvOnLinkFlag │true │Boolean │
317 ├─────────────────────────────┼────────────────┼───────────────┤
318 │AdvPreferredLifetime │604800 │Seconds │
319 ├─────────────────────────────┼────────────────┼───────────────┤
320 │AdvAutonomousFlag │true │Boolean │
321 ├─────────────────────────────┼────────────────┼───────────────┤
322 │AdvValidExpiration │not set │Date/Time │
323 ├─────────────────────────────┼────────────────┼───────────────┤
324 │AdvPreferredExpiration │not set │Date/TIme │
325 └─────────────────────────────┴────────────────┴───────────────┘
326 These variables are described as follows:
327
328 AdvValidLifetime Specifies the valid
329 lifetime of the pre‐
330 fix that is being
331 configured.
332
333
334 AdvOnLinkFlag Specifies the value
335 to be placed in the
336 on-link flag ("L-
337 bit") field in the
338 Prefix Information
339 option.
340
341
342 AdvPreferredLifetime Specifies the value
343 to be placed in the
344 Preferred Lifetime in
345 the Prefix Informa‐
346 tion option.
347
348
349 AdvAutonomousFlag Specifies the value
350 to be placed in the
351 Autonomous Flag field
352 in the Prefix Infor‐
353 mation option.
354
355
356 AdvValidExpiration Specifies the valid
357 expiration date of
358 the prefix.
359
360
361 AdvPreferredExpiration Specifies the pre‐
362 ferred expiration
363 date of the prefix.
364
365 The AdvValidExpiration and AdvPreferredExpira‐
366 tion variables are used to specify that the
367 lifetime should be decremented in real time as
368 specified in RFC 2461. If an Expiration vari‐
369 able is set, it takes precedence over the cor‐
370 responding AdvValidLifetime or AdvPre‐
371 ferredLifetime variable setting.
372
373
374 value The value is a function of the unit. Boolean
375 values are true, false, on, off, 1, or 0.
376
377 Values in seconds can have characters appended
378 for day (d), hour h), minute (m) and second(s).
379 The default is seconds. For example, 1h means 1
380 hour. This is equivalent to the value 3600.
381
382 Values in milliseconds can have characters
383 appended for day (d),hour (h), minute (m) sec‐
384 ond (s),and millisecond (ms). The default is
385 milliseconds. For example, 1h is equivalent to
386 the value 3600000.
387
388 Date/time values are strings that use the rec‐
389 ommended ISO date format described as "%Y-%m-%d
390 %R", which represents a 4 digit year, a dash
391 character, a numeric month, a dash character,
392 and a numeric day of the month, followed by one
393 or more whitespace characters and finally a 24
394 hour clock with hours, a colon, and minutes.
395 For example, 1999-01-31 20:00 means 8pm January
396 31 in 1999. Since the date/time values contain
397 a space, use single or double quotes to declare
398 the value. For example:
399
400 prefixdefault AdvPreferredExpiration '1999-01-31 20:00'
401
402
403
405 Example 1 Sending Router Advertisements for all Interfaces
406
407
408 The following example can be used to send router advertisements out to
409 all interfaces:
410
411
412 # Send router advertisements out all interfaces
413 ifdefault AdvSendAdvertisements on
414 prefixdefault AdvOnLinkFlag on AdvAutonomousFlag on
415
416 # Advertise a (bogus) global prefix and a site
417 # local prefix on three interfaces using the default lifetimes
418 prefix 2:0:0:9255::0/64 eri0
419 prefix fec0:0:0:9255::0/64 eri0
420
421 prefix 2:0:0:9256::0/64 eri1
422 prefix fec0:0:0:9256::0/64 eri1
423
424 prefix 2:0:0:9259::0/64 eri2
425 prefix fec0:0:0:9259::0/64 eri2
426
427
429 See attributes(5) for descriptions of the following attributes:
430
431
432
433
434 ┌─────────────────────────────┬─────────────────────────────┐
435 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
436 ├─────────────────────────────┼─────────────────────────────┤
437 │Availability │SUNWcsr │
438 ├─────────────────────────────┼─────────────────────────────┤
439 │Interface Stability │Committed │
440 └─────────────────────────────┴─────────────────────────────┘
441
443 dhcpagent(1M), ifconfig(1M), in.ndpd(1M), routeadm(1M), attributes(5),
444 icmp6(7P), ip6(7P)
445
446
447 Narten, T., Nordmark, E., and Simpson, W. RFC 2461, Neighbor Discovery
448 for IP Version 6 (IPv6). The Internet Society. December 1998.
449
450
451 Thomson, S., and Narten, T. RFC 2462, IPv6 Stateless Address Autocon‐
452 figuration. The Internet Society. December 1998.
453
454
455 Narten, T., and Draves, R. RFC 3041, Privacy Extensions for Stateless
456 Address Autoconfiguration in IPv6. The Internet Society. January 2001.
457
458
459 Droms, R. RFC 3315, Dynamic Host Configuration Protocol for IPv6
460 (DHCPv6). Cisco Systems. July 2003.
461
462
463 System Administration Guide: IP Services
464
465
466
467SunOS 5.11 4 Jan 2007 ndpd.conf(4)