File: dhcp6c.conf.sample

package info (click to toggle)
wide-dhcpv6 20080615-22
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, sid
  • size: 4,616 kB
  • sloc: ansic: 14,877; yacc: 1,114; sh: 615; lex: 469; makefile: 119
file content (61 lines) | stat: -rw-r--r-- 1,818 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
# The following is an example for use with IPv6 auto-configuration.
# The "information-only" statement makes dhcp6c exchange informational
# configuration parameters with servers. A list of DNS server addresses
# is an example of such parameters. This statement is useful when the
# client does not need stateful configuration parameters such as IPv6
# addresses or prefixes.

interface ne0 {
	information-only;
};


# The following is a sample configuration for a client on a LAN
# where IPv6 addresses are assigned via DHCPv6 ("stateful address
# assignment"). Use this if you want the client to query the
# DHCPv6 server for an IPv6 address and for DNS servers, as in
# traditional IPv4 DHCP.

interface em0 {
       send ia-na 0;
       send rapid-commit;
       send domain-name-servers;
};

id-assoc na {
};

# The following is an example configuration for delegation of an IPv6 prefix
# from an upstream service provider.  With this configuration dhcp6c will
# send solicit messages containing an IA_PD option, with an IAID 0, on to
# an upstream PPP link, ppp0.  After receiving some 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 was to be configured in both the client and the server
# for DHCPv6 authentication, it would be specified in this file as follows:

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

# And the interface statement would be modified as follows:

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