wide-dhcpv6的dhcp6c配置

源码里面已经有man文档，直接打开用如下命令打开就好

man -l wide-dhcpv6/dhcp6c.conf.5

DHCP6C.CONF(5) BSD File Formats Manual DHCP6C.CONF(5)

NAME
dhcp6c.conf — DHCPv6 client configuration fileSYNOPSIS
/usr/local/etc/dhcp6c.confDESCRIPTION
The dhcp6c.conf file contains configuration information for KAME's DHCPv6 client, dhcp6c. The configuration file consists of asequence of statements terminated by a semi-colon (`;'). Statements are composed of tokens separated by white space, which can beany combination of blanks, tabs and newlines. In some cases a set of statements is combined with a pair of brackets, which isregarded as a single token. Lines beginning with ‘#’ are comments.

Interface specification
There are some statements that may or have to specify interface. Interfaces are specified in the form of "name unit", such as fxp0and gif1.

DHCPv6 options
Some configuration statements take the description of a DHCPv6 option as an argument. The followings are the format and descriptionof available DHCPv6 options.
domain-name-servers
means a Domain Name Server option.
domain-name
means a domain name option.
ntp-servers
means an NTP server option. As of this writing, the option type for this option is not officially assigned. dhcp6c willreject this option unless it is explicitly built to accept the option.
sip-server-address
means a SIP Server address option.
sip-server-domain-name
means a SIP server domain name option.
nis-server-address
means a NIS Server address option.
nis-domain-name
means a NIS domain name option.
nisp-server-address
means a NIS+ Server address option.
nisp-domain-name
means a NIS+ domain name option.
bcmcs-server-address
means a BCMCS Server address option.
bcmcs-server-domain-name
means a BCMCS server domain name option.
ia-pd ID
means an IA_PD (Identity Association for Prefix Delegation) option. ID is a decimal number of the IAID (see below aboutidentity associations).
ia-na ID
means an IA_PD (Identity Association for Non-temporary Addresses) option. ID is a decimal number of the IAID (see belowabout identity associations).
rapid-commit
means a rapid-commit option.
authentication authname
means an authentication option. authname is a string specifying parameters of the authentication protocol. Anauthentication statement for authname must be provided.

Interface statement
An interface statement specifies configuration parameters on the interface. The generic format of an interface statement is as fol‐lows:
interface interface { substatements };
The followings are possible substatements in an interface statement.
send send-options ;
This statement specifies DHCPv6 options to be sent to the server(s). Some options can only appear in particularmessages according to the specification, in which case the appearance of the options is limited to be compliant withthe specification.

send-options is a comma-separated list of options, each of which should be specified as described above. Multiplesend statements can also be specified, in which case all the specified options will be sent.

When rapid-commit is specified, dhcp6c will include a rapid-commit option in solicit messages and wait for an imme‐diate reply instead of advertisements.

When ia-pd is specified, dhcp6c will initiate prefix delegation as a requesting router by including an IA_PD optionwith the specified ID in solicit messages.

When ia-na is specified, dhcp6c will initiate stateful address assignment by including an IA_NA option with thespecified ID in solicit messages.

In either case, a corresponding identity association statement must exist with the same ID.
request request-options;
This statement specifies DHCPv6 options to be included in an option-request option. request-options is a comma-sep‐arated list of options, which can consist of the following options.
domain-name-servers
requests a list of Domain Name Server addresses.
domain-name
requests a DNS search path.
ntp-servers
requests a list of NTP server addresses. As of this writing, the option type for this option is not offi‐cially assigned. dhcp6c will reject this option unless it is explicitly built to accept the option.
sip-server-address
requests a list of SIP server addresses.
sip-domain-name
requests a SIP server domain name.
nis-server-address
requests a list of NIS server addresses.
nis-domain-name
requests a NIS domain name.
nisp-server-address
requests a list of NIS+ server addresses.
nisp-domain-name
requests a NIS+ domain name.
bcmcs-server-address
requests a list of BCMCS server addresses.
bcmcs-domain-name
requests a BCMCS domain name.
refreshtime
means an information refresh time option. This can only be specified when sent with information-requestmessages; dhcp6c will ignore this option for other messages.
Multiple request statements can also be specified, in which case all the specified options will be requested.
information-only;
This statement specifies dhcp6c to only exchange informational configuration parameters with servers. A list of DNSserver addresses is an example of such parameters. This statement is useful when the client does not need statefulconfiguration parameters such as IPv6 addresses or prefixes.
script "script-name";
This statement specifies a path to script invoked by dhcp6c on a certain condition including when the daemonreceives a reply message. script-name must be the absolute path from root to the script file, be a regular file,
and be created by the same owner who runs the daemon.

Identity association statement
Identity association (IA) is a key notion of DHCPv6. An IA is uniquely identified in a client by a pair of IA type and IA identi‐fier (IAID). An IA is associated with configuration information dependent on the IA type.

An identity association statement defines a single IA with some client-side configuration parameters. Its format is as follows:
id-assoc type [ID] { substatements };
type is a string for the type of this IA. The current implementation supports ‘na’ (non-temporary address allocation) ‘pd’
(prefix delegation) for the IA type. ID is a decimal number of IAID. If omitted, the value 0 will be used by default.
substatements is a sequence of statements that specifies configuration parameters for this IA. Each statement may or maynot be specific to the type of IA.

The followings are possible substatements for an IA of type na.
address ipv6-address pltime [vltime];
specifies an address and related parameters that the client wants to be allocated. Multiple addresses can be speci‐fied, each of which is described as a separate address substatement. dhcp6c will include all the addresses (andrelated parameters) in Solicit messages, as an IA_NA prefix option encapsulated in the corresponding IA_NA option.
Note, however, that the server may or may not respect the specified prefix parameters. For parameters of theaddress substatement, see dhcp6s.conf(5).

The followings are possible substatements for an IA of type pd.
prefix_interface_statement
specifies the client's local configuration of how delegated prefixes should be used (see below).
prefix ipv6-prefix pltime [vltime];
specifies a prefix and related parameters that the client wants to be delegated. Multiple prefixes can be speci‐fied, each of which is described as a separate prefix substatement. dhcp6c will include all the prefixes (andrelated parameters) in Solicit messages, as an IA_PD prefix option encapsulated in the corresponding IA_PD option.
Note, however, that the server may or may not respect the specified prefix parameters. For parameters of the prefixsubstatement, see dhcp6s.conf(5).

Prefix interface statement
A prefix interface statement specifies configuration parameters of prefixes on local interfaces that are derived from delegated pre‐fixes. A prefix interface statement can only appear as a substatement of an identity association statement with the type pd. Thegeneric format of an interface statement is as follows:
prefix-interface interface { substatements };
When an IPv6 prefix is delegated from a DHCPv6 server, dhcp6c will assign a prefix on the interface unless the interfacereceives the DHCPv6 message that contains the prefix with the delegated prefix and the parameters provided in substatements.
Possible substatements are as follows:
sla-id ID ;
This statement specifies the identifier value of the site-level aggregator (SLA) on the interface. ID must be adecimal integer which fits in the length of SLA IDs (see below). For example, if ID is 1 and the client is dele‐gated an IPv6 prefix 2001:db8:ffff::/48, dhcp6c will combine the two values into a single IPv6 prefix,
2001:db8:ffff:1::/64, and will configure the prefix on the specified interface.
sla-len length ;
This statement specifies the length of the SLA ID in bits. length must be a decimal number between 0 and 128. Ifthe length is not specified by this statement, the default value 16 will be used.

Authentication statement
An authentication statement defines a set of authentication parameters used in DHCPv6 exchanges with the server(s). The format ofan authentication statement is as follows:
authentication authname { substatements };
authname is a string which is unique among all authentication statements in the configuration file. It will specify a par‐ticular set of authentication parameters when authentication option is specified in the interface statement. Possible sub‐statements of the authentication statement are as follows:
protocol authprotocol ;
specifies the authentication protocol. Currently, the only available protocol as authprotocol is delayed, whichmeans the DHCPv6 delayed authentication protocol.
algorithm authalgorithm ;
specifies the algorithm for this authentication. Currently, the only available algorithm is HMAC-MD5, which can bespecified as one of the followings: hmac-md5, HMAC-MD5, hmacmd5, or HMACMD5. This substatement can be omitted. Inthis case, HMAC-MD5 will be used as the algorithm.
rdm replay-detection-method ;
specifies the replay protection method for this authentication. Currently, the only available method ismonocounter, which means the use of a monotonically increasing counter. If this method is specified, dhcp6c willuse an NTP-format timestamp when it authenticates the message. This substatement can be omitted, in which casemonocounter will be used as the method.

Keyinfo statement
A keyinfo statement defines a secret key shared with the server(s) to authenticate DHCPv6 messages. The format of a keyinfo state‐ment is as follows:
keyinfo keyname { substatements };
keyname is an arbitrary string. It does not affect client's behavior but is provided for readability of log messages. Pos‐sible substatements of the keyinfo statement are as follows:
realm "realmname" ;
specifies the DHCP realm. realmname is an arbitrary string, but is typically expected to be a domain name like"kame.net" .
keyid ID ;
specifies the key identifier, ID, as a decimal number. A secret key is uniquely identified within the client by theDHCP realm and the key identifier.
secret "secret-value" ;
specifies the shared secret of this key. "secret-value" is a base-64 encoded string of the secret.
expire "expiration-time" ;
specifies the expiration time of this key. "expiration-time" should be formatted in one of the followings:
yyyy-mm-dd HH:MM, mm-dd HH:MM, or HH:MM, where yyyy is the year with century (e.g., 2004), mm is the month, dd isthe day of the month, HH is the hour of 24-hour clock, and MM is the minute, each of which is given as a decimalnumber. Additionally, a special keyword forever can be specified as expiration-time, which means the key has aninfinite lifetime and never expires. This substatement can be omitted, in which case forever will be used bydefault.

Examples
The followings are a sample configuration to be delegated an IPv6 prefix from an upstream service provider. With this configurationdhcp6c will send solicit messages containing an IA_PD option, with an IAID 0, on to an upstream PPP link, ppp0. After receivingsome prefixes from a server, dhcp6c will then configure derived IPv6 prefixes with the SLA ID 1 on a local ethernet interface, ne0.
Note that the IAID for the id-assoc statement is 0 according to the default.

interface ppp0 {
send ia-pd 0;
};

id-assoc pd {
prefix-interface ne0 {
sla-id 1;
};
};

If a shared secret should be configured in both the client and the server for DHCPv6 authentication, it would be specified in theconfiguration file as follows:

keyinfo kame-key {
realm "kame.net";
keyid 1;
secret "5pvW2g48OHPvkYMJSw0vZA==";
};

One easy way of generating a new secret in the base64 format is to execute the openssl(1) command (when available) as follows,

% openssl rand -base64 16 and copy the output to the dhcp6c.conf file.

To include an authentication option for DHCPv6 authentication, the interface statement should be modified and an authenticationstatement should be added as follows:

interface ppp0 {
send ia-pd 0;
send authentication kame;
};

authentication kame {
protocol delayed;
};

interface fxp0 {
send ia-na 0;
};

wide-dhcpv6的dhcp6c配置相关推荐

IPv6基础介绍--IPv6路由基础--DHCPv6原理与配置——总结
一.IPv6基础介绍 1.IPv6是Internet工程任务组(IETF)设计的一套规范,它是网络层协议的第二代标准协议,也是IPv4(Internet Protocol Version 4)的升级版 ...
10.3、DHCPv6原理与配置
10.3.DHCPv6原理与配置前言主机在运行IPv6时,可以通过使用无状态地址自动配置或DHCPv6协议来获取IPv6地址.IPv6动态主机配置协议DHCPv6(Dynamic Host Con ...
DHCPv6原理与配置
主机在运行IPv6时,可以通过使用无状态地址自动配置或DHCPv6协议来获取IPv6地址.IPv6动态主机配置协议DHCPv6(Dynamic Host Configuration Protocol ...
linux dhcpv6有状态配置,ipv6 有状态和无状态什么意思
这是IPv6协议的一个突出特点:支持网络节点的地址自动配置. 一.有状态就是有数据存储功能.有状态对象(Stateful Bean),就是有实例变量的对象 ,可以保存数据,是非线程安全的.在不同方法调 ...
华为路由器相同网段DHCPv6配置
首先上一张基本拓扑图我们可以知道PC9是自己配置的IPv6地址,这个就不展示了. 那么我们先配置SW10(DHCPv6与DHCPv4不同点:DHCPv4不同网段才需要配中继,DHCPv6相同网段也需 ...
华为DHCPv6实验配置
目录配置AR1作为DHCPv6服务器为PC1分配IPv6地址配置AR2作为DHCPv6服务器,AR1作为DHCPv6中继器为PC2分配IPv6地址配置AR3作为DHCPv6 PD服务器为AR1分 ...
实验2：配置DHCPv6
2.1[实验目的] 3.深刻理解DHCPv6原理. 4.掌握DHCPv6的配置方法 2.2[实验环境] 用1个交换机1台路由器,两台终端,做实验了解DHCPv6. 2.3[实验过程] 拓扑图 2.3. ...
配置DHCPv6服务器实验详解
配置DHCPv6服务器示例组网需求如果大量的企业用户IPv6地址都是手动配置,那么网络管理员工作量大,而且可管理性很差.管理员希望实现公司用户IPv6地址和网络配置参数的自动获取,便于统一管理,实 ...
IPv6 — 地址配置方式
目录文章目录目录 IPv6 的地址配置方式 ICMPv6 NDP 协议 ICMPv6 NDP 协议的消息类型 ICMP NDP 协议的地址配置流程 1.路由器发现 2.自动生成链路本地地址 3.重 ...

wide-dhcpv6的dhcp6c配置

wide-dhcpv6的dhcp6c配置相关推荐

最新文章

热门文章