From: Tomek Mrugalski Date: Fri, 18 Jan 2013 15:36:13 +0000 (+0100) Subject: [2596] Removing guide changes per Stephen's request X-Git-Tag: bind10-1.1.0beta1-release~72^2~42^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=a70f6172194a976b514cd7d67ce097bbca3c2798;p=thirdparty%2Fkea.git [2596] Removing guide changes per Stephen's request - This will be moved to 2642. --- diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml index 02901aa472..f1f5859d2c 100644 --- a/doc/guide/bind10-guide.xml +++ b/doc/guide/bind10-guide.xml @@ -3839,32 +3839,6 @@ Dhcp6/subnet6 [] list (default) and problems in the DHCPv6 server. See . -
- Subnet selection - - DHCPv6 server may receive requests from local (connected to the same - subnet as the server) and remote (connecting via relays) - clients. Server may have many subnet configurations defined, so it - must select appropriate subnet for a given request. Server first - checks if there is only one subnet defined and source of the packet is - link-local. If this is the case server assumes that the only subnet - defined is local and client is indeed connected to it. This check - simplifies small deployments. - - If there are two or more subnets defined, server can not assume - which of those (if any) subnets are local. Therefore an optional - "interface" parameter has been defined to designate that a given subnet - is local, i.e. reachable directly over specified interface. For example - the server that is intended to serve local subnet over eth0 may be configured - as follows: - -> config add Dhcp6/subnet6 -> config set Dhcp6/subnet6[1]/subnet "2001:db8:beef::/48" -> config set Dhcp6/subnet6[1]/pool [ "2001:db8:beef::/48" ] -> config set Dhcp6/subnet6[1]/interface "eth0" -> config commit - -