From: Tomek Mrugalski <tomasz@isc.org>
Date: Thu, 20 Feb 2014 16:12:37 +0000 (+0100)
Subject: [3322] Guide updated.
X-Git-Tag: bind10-1.2.0beta1-release~27^2~4
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=c4c70d6d679becb3cff8bca225f17ac3ac7f0afd;p=thirdparty%2Fkea.git

[3322] Guide updated.
---

diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml
index e3319f0513..8f719a921f 100644
--- a/doc/guide/bind10-guide.xml
+++ b/doc/guide/bind10-guide.xml
@@ -4592,6 +4592,11 @@ Dhcp4/subnet4	[]	list	(default)
         If the message is relayed it is accepted through any interface. The giaddr
         set by the relay agent is used to select the subnet for the client.
       </para>
+      <para>
+	It is also possible to specify a relay IPv4 address for a given subnet. It
+	can be used to match incoming packets into a subnet in uncommon configurations,
+	e.g. shared subnets. See <xref linkend="dhcp4-relay-override"/> for details.
+      </para>
       <note>
         <para>The subnet selection mechanism described in this section is based
         on the assumption that client classification is not used. The classification
@@ -4601,7 +4606,7 @@ Dhcp4/subnet4	[]	list	(default)
     </section>
 
     <section id="dhcp4-relay-override">
-      <title>Using specific relay for a subnet</title>
+      <title>Using specific relay agent for a subnet</title>
       <para>
         The relay has to have an interface connected to the link on which
         the clients are being configured. Typically the relay has an IPv4