|
The ndpd.conf file contains configuration information for in.ndpd()1M when used on a router. This file does not need to exist or can
be empty on a host. The file has one configuration entry per line; note that lines can be extended with "\" followed by a newline. There are four forms of configuration entries which are identified by the first field on the line: ifdefault, prefixdefault, if, or prefix. The ifdefault and if entries set interface configuration variables; the former establishes the defaults for all interfaces. Any ifdefault entries must precede any if entries in the file.
The prefixdefault and prefix entries control per-prefix configuration variables. prefixdefault establishes the defaults for all prefixes on all interfaces. Any prefixdefault entries must precede any prefix
entries in the file.
Each ifdefault entry is composed of a single line of the form:
|
ifdefault [ if-variable-name value ]*
|
Each if entry is composed of a single line of the form:
|
if interface [ if-variable-name value ]*
|
Each prefixdefault entry is composed of a single line of the form:
|
prefixdefault [ prefix-variable-name value ]*
|
Each prefix entry is composed of a single line of the form:
|
prefix prefix/prefix_length interface [ prefix-variable-name value ]*
|
Fields are separated by either SPACE or TAB characters. A `#' (number sign) indicates the beginning of a comment. Characters up to the end of the line are not interpreted by routines that search this file.
-
interface
- The name of a network interface, for example, le0.
-
prefix
- An IPv6 address in standard hexadecimal notation, for example, fec0:0:0:1::0.
-
prefix_length
- A number between 0 and 128.
-
if-variable-name
- An interface variable as discussed in RFC 2461 and RFC 2462. The following lists the each interface variable and its default value and unit:
Variable Name | Default | Unit |
DupAddrDetectTransmits | 1 | Counter |
AdvSendAdvertisements | false | Boolean |
MaxRtrAdvInterval | 600 | Seconds |
MinRtrAdvInterval | 200 | Seconds |
AdvManagedFlag | false | Boolean |
AdvOtherConfigFlag | false | Boolean |
AdvLinkMTU | 0 | Bytes |
AdvReachableTime | 0 | Milliseconds |
AdvRetransTimer | 0 | Milliseconds |
AdvCurHopLimit | 0 | Counter |
AdvDefaultLifetime | 1800 | Seconds |
-
prefix-variable-name
- A prefix variable as discussed in RFC 2461 and RFC 2462. The following lists the each interface variable and its default value and unit:
Variable Name | Default | Unit |
AdvValidLifetime | 2592000 | Seconds |
AdvOnLinkFlag | true | Boolean |
AdvPreferredLifetime | 604800 | Seconds |
AdvAutonomousFlag | true | Boolean |
AdvValidExpiration | not set | Date/Time |
AdvPreferredExpiration | not set | Date/TIme |
The "Expiration" variables are used to specify that the lifetime should be decremented in real time as specified in RFC 2461. If an "Expiration" variable is set then it takes precedence over the corresponding "Lifetime" ariable setting.
-
value
- The value is a function of the unit. Boolean values are true, false, on, off, 1, or 0.
Values in seconds can have characters appended for day (d), hour h), minute (m) and second (s). The default is seconds. For example, 1h means 1 hour. This is equivalent to the value 3600.
Values in milliseconds can have characters appended for day (d), hour (h), minute (m) second (s), and millisecond (ms). The default is milliseconds. For example, 1h is equivalent to
the value 3600000.
Date/time values are strings that use the recommended ISO date format described as "%Y-%m-%d %R", which represents a 4 digit year, a dash character, a numeric month, a dash character, and a numeric day of the month, followed by one or more whitespace characters and finally
a 24 hour clock with hours, a colon, and minutes. For example, 1999-01-31 20:00 means 8pm January 31 in 1999. Since the date/time values contain a space, use single or double quotes to declare the value. For example:
|
prefixdefault AdvPreferredExpiration '1999-01-31 20:00'
|
|