]> git.ipfire.org Git - thirdparty/kea.git/commitdiff
[3191] User's Guide updated
authorTomek Mrugalski <tomasz@isc.org>
Fri, 11 Oct 2013 18:17:32 +0000 (20:17 +0200)
committerTomek Mrugalski <tomasz@isc.org>
Fri, 11 Oct 2013 18:17:32 +0000 (20:17 +0200)
doc/guide/bind10-guide.xml

index 83c50b6a303a0318d52b9b3c6526cb941bf8eec3..36fd6d54e50bf53945b3c7763874d74dfc1fefc2 100644 (file)
@@ -4388,6 +4388,27 @@ Dhcp4/subnet4    []      list    (default)
       </para>
     </section>
 
+    <section id="dhcp4-next-server">
+      <title>Next server (siaddr)</title>
+      <para>In some cases, clients want to obtain configuration form the TFTP server.
+      Although there is a dedicated option for it, some devices may use siaddr field
+      in the DHCPv4 packet for that purpose. That specific field can be configured
+      using next-server directive. It is possible to define it in global scope or
+      for a given subnet only. If both are defined, subnet value takes precedence.
+      </para>
+
+<screen>
+&gt; <userinput>config add Dhcp4/next-server</userinput>
+&gt; <userinput>config set Dhcp4/next-server "192.0.2.123"</userinput>
+&gt; <userinput>config commit</userinput>
+<userinput></userinput>
+&gt; <userinput>config add Dhcp4/subnet[0]/next-server</userinput>
+&gt; <userinput>config set Dhcp4/subnet[0]/next-server "192.0.2.234"</userinput>
+&gt; <userinput>config commit</userinput>
+</screen>
+
+    </section>
+
     <section id="dhcp4-std">
       <title>Supported Standards</title>
       <para>The following standards and draft standards are currently