WIDE-DHCPv6 client configuration and dhcp6c manual

- 日理万妓 2021-12-17 14:33 425阅读 0赞

# WIDE-DHCPv6 client configuration #

The `/etc/config/dhcp6c` file controls the WIDE-DHCPv6 client package *wide-dhcpv6\-client* configuration. It defines *basic properties* and *interface settings*.

## Sections ##

A typical default configuration consists of one `dhcp6c` section with common settings and one or more `interface` sections, usually covering the *lan* and *loopback* networks.

### Basic Properties ###

The section of type `dhcp6c` named `basic` defines common client settings.

Example:

<table> 
 <tbody> 
  <tr> 
   <td><code>config 'dhcp6c' 'basic' option 'enabled' '1' option 'interface' 'wan' option 'pd' '1' option 'domain_name_servers' '1' option 'script' '/usr/bin/dhcp6c-state</code>'</td> 
  </tr> 
 </tbody> 
</table>

All defined options of this section are listed below.

<table> 
 <tbody> 
  <tr> 
   <th>Name</th> 
   <th>Type</th> 
   <th>Required</th> 
   <th>Default</th> 
   <th>Description</th> 
  </tr> 
  <tr> 
   <td><code>enabled</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>0</code></td> 
   <td>Specifies whether the <span>DHCPv6</span> <span>client</span> should be started on boot</td> 
  </tr> 
  <tr> 
   <td><code>interface</code></td> 
   <td>string</td> 
   <td>yes</td> 
   <td><code>wan</code></td> 
   <td>Specifies the <em>logical interface name</em> the <span>client</span> is running on</td> 
  </tr> 
  <tr> 
   <td><code>dns</code></td> 
   <td>string</td> 
   <td>no</td> 
   <td><code>dnsmasq</code></td> 
   <td>Specifies the type of DNS server in use to propagate received DNS information. At the time of writing, only <em>dnsmasq</em> is supported</td> 
  </tr> 
  <tr> 
   <td><code>debug</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>0</code></td> 
   <td>Enables additional debug information in the system log</td> 
  </tr> 
  <tr> 
   <td><code>pd</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>1</code></td> 
   <td>Requests prefix delegation at the <span>DHCPv6</span> server</td> 
  </tr> 
  <tr> 
   <td><code>na</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>0</code></td> 
   <td>Requests a permanent, non temporary address at the <span>DHCPv6</span> server</td> 
  </tr> 
  <tr> 
   <td><code>rapid_commit</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>1</code></td> 
   <td>Signalize a rapid commit two message exchange (<a title="http://tools.ietf.org/html/rfc3315#section-22.14" href="http://tools.ietf.org/html/rfc3315#section-22.14" rel="nofollow">RFC3315</a>)</td> 
  </tr> 
  <tr> 
   <td><code>domain_name_servers</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>1</code></td> 
   <td>Request a DNS server addresses</td> 
  </tr> 
  <tr> 
   <td><code>domain_name</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>0</code></td> 
   <td>Request the domain name</td> 
  </tr> 
  <tr> 
   <td><code>ntp_servers</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>0</code></td> 
   <td>Request NTP server addresses (<a title="http://tools.ietf.org/html/rfc5908#section-4.1" href="http://tools.ietf.org/html/rfc5908#section-4.1" rel="nofollow">RFC5908</a>)</td> 
  </tr> 
  <tr> 
   <td><code>sip_server_address</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>0</code></td> 
   <td>Request SIP server address (<a title="http://tools.ietf.org/html/rfc3319#section-3" href="http://tools.ietf.org/html/rfc3319#section-3" rel="nofollow">RFC3319</a>)</td> 
  </tr> 
  <tr> 
   <td><code>sip_server_domain_name</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>0</code></td> 
   <td>Request SIP domain names (<a title="http://tools.ietf.org/html/rfc3319#section-3.1" href="http://tools.ietf.org/html/rfc3319#section-3.1" rel="nofollow">RFC3319</a>)</td> 
  </tr> 
  <tr> 
   <td><code>nis_server_address</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>0</code></td> 
   <td>Request Network Information Service (NIS) server address (<a title="http://tools.ietf.org/html/rfc3898#section-3" href="http://tools.ietf.org/html/rfc3898#section-3" rel="nofollow">RFC3898</a>)</td> 
  </tr> 
  <tr> 
   <td><code>nis_domain_name</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>0</code></td> 
   <td>Request Network Information Service (NIS) domain name (<a title="http://tools.ietf.org/html/rfc3898#section-5" href="http://tools.ietf.org/html/rfc3898#section-5" rel="nofollow">RFC3898</a>)</td> 
  </tr> 
  <tr> 
   <td><code>nisp_server_address</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>0</code></td> 
   <td>Request Network Information Service V2 (NIS+) server address (<a title="http://tools.ietf.org/html/rfc3898#section-4" href="http://tools.ietf.org/html/rfc3898#section-4" rel="nofollow">RFC3898</a>)</td> 
  </tr> 
  <tr> 
   <td><code>nisp_domain_name</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>0</code></td> 
   <td>Request Network Information Service V2 (NIS+) domain name (<a title="http://tools.ietf.org/html/rfc3898#section-6" href="http://tools.ietf.org/html/rfc3898#section-6" rel="nofollow">RFC3898</a>)</td> 
  </tr> 
  <tr> 
   <td><code>bcmcs_server_address</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>0</code></td> 
   <td>Request Broadcast and Multicast Control Service (BCMCS) address (<a title="http://tools.ietf.org/html/rfc4280#section-4.4" href="http://tools.ietf.org/html/rfc4280#section-4.4" rel="nofollow">RFC4280</a>)</td> 
  </tr> 
  <tr> 
   <td><code>bcmcs_server_domain_name</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>0</code></td> 
   <td>Request Broadcast and Multicast Control Service (BCMCS) domain name (<a title="http://tools.ietf.org/html/rfc4280#section-4.2" href="http://tools.ietf.org/html/rfc4280#section-4.2" rel="nofollow">RFC4280</a>)</td> 
  </tr> 
  <tr> 
   <td><code>duid</code></td> 
   <td>string</td> 
   <td>no</td> 
   <td><em>(derived from MAC address)</em></td> 
   <td>Override the DUID used for <span>DHCPv6</span> requests. The DUID must be specified as a set of at least 7 colon separated heximal digits, e.g. <code>00:03:00:06:D8:5D:4C:A5:03:F2</code></td> 
  </tr> 
  <tr> 
   <td><code>script</code></td> 
   <td>file path</td> 
   <td>no</td> 
   <td><code>/usr/bin/dhcp6c-state</code></td> 
   <td>Path of script which is executed when a reply is received</td> 
  </tr> 
 </tbody> 
</table>

### Interface Settings ###

Sections of type `interface` define on which interfaces delegated prefixes are added and how they're aggregated. This sections are *named*, the section name corresponds to the covered *logical interface*.

Example:

<table> 
 <tbody> 
  <tr> 
   <td><code>config 'interface' 'lan' option 'enabled' '1' option 'sla_id' '0' option 'sla_len' '8</code>'</td> 
  </tr> 
 </tbody> 
</table>

*  `lan` specifies that this section belongs to the LAN interface
 *  `sla_id 0` selects the 1st subnet out of the delegated prefix
 *  `sla_len 8` defines that the received prefix is expected to be 56 bits in size ( `64` \- `8` = `56`)

The valid options of this section are listed blow.

<table> 
 <tbody> 
  <tr> 
   <th>Name</th> 
   <th>Type</th> 
   <th>Required</th> 
   <th>Default</th> 
   <th>Description</th> 
  </tr> 
  <tr> 
   <td><code>enabled</code></td> 
   <td>boolean</td> 
   <td>no</td> 
   <td><code>0</code></td> 
   <td>Specifies whether a prefix should be added on this interface</td> 
  </tr> 
  <tr> 
   <td><code>sla_id</code></td> 
   <td>integer</td> 
   <td>yes</td> 
   <td><em>(none)</em></td> 
   <td>Specifies the <em>site level aggregator identifier</em> (selects the subnet out of the delegated prefix)</td> 
  </tr> 
  <tr> 
   <td><code>sla_len</code></td> 
   <td>integer</td> 
   <td>yes</td> 
   <td><em>(none)</em></td> 
   <td>Specifies the <em>site level aggregator length</em> which is the difference of 64 and the delegated prefix size, e.g. <code>/64</code> minus <code>/56</code> from ISP = <code>8</code></td> 
  </tr> 
 </tbody> 
</table>

## Example ##

This example requests a `/56` sized prefix and DNS servers on `wan` and configures two `/64` subnets out of the prefix on `lan` and `loopback`. The `loopback` interface gets the first subnet assigned, `lan` the second.

`config 'dhcp6c' 'basic' option 'enabled' '1' option 'interface' 'wan' option 'pd' '1' option 'domain_name_servers' '1' option 'script' '/usr/bin/dhcp6c-state' config 'interface' 'loopback' option 'enabled' '1' option 'sla_id' '0' option 'sla_len' '8' config 'interface' 'lan' option 'enabled' '1' option 'sla_id' '1' option 'sla_len' '8`'

\-------------------

# dhcp6c(8) - Linux man page #

## Name ##

dhcp6c - DHCPv6 client daemon

## Synopsis ##

**dhcp6c** \[ **-dDf** \] \[ **-r** *all* | *<addresses...>* \] \[ **-R** *<addresses...>* \] \[ **-c** *pathspec* \] \[ **-I** \] *<interface>*

## Description ##

**dhcp6c** is an implementation of the DHCPv6 client.

Using DHCPv6 messages and DHCPv6 options, **dhcp6c** is used to request and configure IPv6 addresses and host network configuration information (e.g., DNS) for a network interface from the DHCPv6 server. It can also be used as a requesting router to request and configure Prefix Delegation for a subnet.

The assigned IPv6 addresses and prefixes are saved as /var/lib/dhcpv6/client6.leasesXXXXXX; this file is used to request the same addresses and prefixes from the DHCPv6 server. Each **dhcp6c** client has a client DHCP Unique Identifier (DUID); the DUID file is saved as /var/lib/dhcpv6/dhcp6c\_duid. The **dhcp6c** client configuration is defined in /etc/dhcp6c.conf.

## Options ##

**-c pathspec**

Specifies

the configuration file for **dhcp6c**

**-d**

Enables **dhcp6c** to print debugging messages.

**-D**

Enables **dhcp6c** to print verbose debugging messages.

**-f**

Enables **dhcp6c** to work as a foreground application. This option is helpful for debugging.

**-I**

Allows **dhcp6c** to request network information only. Do not configure the interface.