diff options
author | SUZUKI, Shinsuke <suz@kame.net> | 2008-07-30 15:29:42 +0000 |
---|---|---|
committer | Bjørn Mork <bjorn@mork.no> | 2010-08-06 15:37:37 +0200 |
commit | e185b3c2675c5a62a6003da58ba929e398b6cbc6 (patch) | |
tree | 38532fd5114c82f95f436045b7ab84c71c60c177 /dhcp6c.conf.sample | |
parent | 7f0217cf9414449b28f7b1b2b5882c1a2b3f2bde (diff) |
added several comments/examples. (contributed by Stefan Sperling)
Diffstat (limited to 'dhcp6c.conf.sample')
-rw-r--r-- | dhcp6c.conf.sample | 43 |
1 files changed, 40 insertions, 3 deletions
diff --git a/dhcp6c.conf.sample b/dhcp6c.conf.sample index 3aeede1..0b192b9 100644 --- a/dhcp6c.conf.sample +++ b/dhcp6c.conf.sample @@ -1,11 +1,31 @@ -# The followings are a sample configuration for requiring the "stateless" -# DHCPv6 service. +# 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 followings are a sample configuration to be delegated an IPv6 prefix +# 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, @@ -22,3 +42,20 @@ id-assoc pd { 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; +}; + |