BIND 10 trac1367, updated. 315edfd3b032c8d2b5683212635b81c2bc5f7dbf [1367] DHCPv6 doc added, DHCPv4 doc updated.
BIND 10 source code commits
bind10-changes at lists.isc.org
Wed Dec 28 11:33:57 UTC 2011
The branch, trac1367 has been updated
via 315edfd3b032c8d2b5683212635b81c2bc5f7dbf (commit)
from 126ab0b66824ee084ee1e03cdcf3a2e73d4bca04 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 315edfd3b032c8d2b5683212635b81c2bc5f7dbf
Author: Tomek Mrugalski <tomasz at isc.org>
Date: Wed Dec 28 12:33:38 2011 +0100
[1367] DHCPv6 doc added, DHCPv4 doc updated.
-----------------------------------------------------------------------
Summary of changes:
doc/guide/bind10-guide.html | 216 ++++++++++++++++++++++++++++++-------------
doc/guide/bind10-guide.xml | 207 +++++++++++++++++++++++++++++++++++------
2 files changed, 328 insertions(+), 95 deletions(-)
-----------------------------------------------------------------------
diff --git a/doc/guide/bind10-guide.html b/doc/guide/bind10-guide.html
index bae83c9..1f5154a 100644
--- a/doc/guide/bind10-guide.html
+++ b/doc/guide/bind10-guide.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>BIND 10 Guide</title><link rel="stylesheet" href="./bind10-guide.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><meta name="description" content="BIND 10 is a Domain Name System (DNS) suite managed by Internet Systems Consortium (ISC). It includes DNS libraries and modular components for controlling authoritative and recursive DNS servers. This is the reference guide for BIND 10 version 20111129. The most up-to-date version of this document (in PDF, HTML, and plain text formats), along with other documents for BIND 10, can be found at ."></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" title="BIND 10 Guide"><div class="titlepage"><div><div><h1 class="title"><a name="id447488"></a>BIND 10 Guide</h1></div><div><h2 class="subtitle">Administrator Reference for BIND 10</h2></div><div><p class="r
eleaseinfo">This is the reference guide for BIND 10 version
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>BIND 10 Guide</title><link rel="stylesheet" href="./bind10-guide.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><meta name="description" content="BIND 10 is a Domain Name System (DNS) suite managed by Internet Systems Consortium (ISC). It includes DNS libraries and modular components for controlling authoritative and recursive DNS servers. This is the reference guide for BIND 10 version 20111129. The most up-to-date version of this document (in PDF, HTML, and plain text formats), along with other documents for BIND 10, can be found at ."></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" title="BIND 10 Guide"><div class="titlepage"><div><div><h1 class="title"><a name="id350584"></a>BIND 10 Guide</h1></div><div><h2 class="subtitle">Administrator Reference for BIND 10</h2></div><div><p class="r
eleaseinfo">This is the reference guide for BIND 10 version
20111129.</p></div><div><p class="copyright">Copyright © 2010-2011 Internet Systems Consortium, Inc.</p></div><div><div class="abstract" title="Abstract"><p class="title"><b>Abstract</b></p><p>BIND 10 is a Domain Name System (DNS) suite managed by
Internet Systems Consortium (ISC). It includes DNS libraries
and modular components for controlling authoritative and
@@ -8,7 +8,7 @@
The most up-to-date version of this document (in PDF, HTML,
and plain text formats), along with other documents for
BIND 10, can be found at <a class="ulink" href="http://bind10.isc.org/docs" target="_top">http://bind10.isc.org/docs</a>.
- </p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#intro">1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="#id447299">Supported Platforms</a></span></dt><dt><span class="section"><a href="#id447312">Required Software</a></span></dt><dt><span class="section"><a href="#starting_stopping">Starting and Stopping the Server</a></span></dt><dt><span class="section"><a href="#managing_once_running">Managing BIND 10</a></span></dt></dl></dd><dt><span class="chapter"><a href="#installation">2. Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#id447765">Building Requirements</a></span></dt><dt><span class="section"><a href="#quickstart">Quick start</a></span></dt><dt><span class="section"><a href="#install">Installation from source</a></span></dt><dd><dl><dt><span class="section"><a href="#id447986">Download Tar File</a></span></dt><dt><span class="section"><a hre
f="#id448009">Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id446976">Configure before the build</a></span></dt><dt><span class="section"><a href="#id448261">Build</a></span></dt><dt><span class="section"><a href="#id448278">Install</a></span></dt><dt><span class="section"><a href="#id448304">Install Hierarchy</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#bind10">3. Starting BIND10 with <span class="command"><strong>bind10</strong></span></a></span></dt><dd><dl><dt><span class="section"><a href="#start">Starting BIND 10</a></span></dt><dt><span class="section"><a href="#bind10.config">Configuration of started processes</a></span></dt></dl></dd><dt><span class="chapter"><a href="#msgq">4. Command channel</a></span></dt><dt><span class="chapter"><a href="#cfgmgr">5. Configuration manager</a></span></dt><dt><span class="chapter"><a href="#cmdctl">6. Remote control daemon</a></span></dt><dd><dl><dt><span class="section"><a href="#c
mdctl.spec">Configuration specification for b10-cmdctl</a></span></dt></dl></dd><dt><span class="chapter"><a href="#bindctl">7. Control and configure user interface</a></span></dt><dt><span class="chapter"><a href="#authserver">8. Authoritative Server</a></span></dt><dd><dl><dt><span class="section"><a href="#id449342">Server Configurations</a></span></dt><dt><span class="section"><a href="#id449416">Data Source Backends</a></span></dt><dt><span class="section"><a href="#id449451">Loading Master Zones Files</a></span></dt></dl></dd><dt><span class="chapter"><a href="#xfrin">9. Incoming Zone Transfers</a></span></dt><dd><dl><dt><span class="section"><a href="#id449606">Configuration for Incoming Zone Transfers</a></span></dt><dt><span class="section"><a href="#id449650">Enabling IXFR</a></span></dt><dt><span class="section"><a href="#zonemgr">Secondary Manager</a></span></dt><dt><span class="section"><a href="#id449793">Trigger an Incoming Zone Transfer Manually</a></span></d
t></dl></dd><dt><span class="chapter"><a href="#xfrout">10. Outbound Zone Transfers</a></span></dt><dt><span class="chapter"><a href="#resolverserver">11. Recursive Name Server</a></span></dt><dd><dl><dt><span class="section"><a href="#id450106">Access Control</a></span></dt><dt><span class="section"><a href="#id450245">Forwarding</a></span></dt></dl></dd><dt><span class="chapter"><a href="#dhcp4">12. DHCPv4 Server</a></span></dt><dd><dl><dt><span class="section"><a href="#id450334">Server Usage</a></span></dt><dt><span class="section"><a href="#dhcp4-config">Server Configuration</a></span></dt><dt><span class="section"><a href="#dhcp4-limit">DHCPv4 Server Limitations</a></span></dt></dl></dd><dt><span class="chapter"><a href="#dhcp6-srv">13. DHCPv6 Server</a></span></dt><dd><dl><dt><span class="section"><a href="#dhcp6-limit">DHCPv6 Server Limitations</a></span></dt></dl></dd><dt><span class="chapter"><a href="#libdhcp++">14. libdhcp++ library</a></span></dt><dd><dl><dt><sp
an class="section"><a href="#iface-detect">Interface detection</a></span></dt></dl></dd><dt><span class="chapter"><a href="#statistics">15. Statistics</a></span></dt><dt><span class="chapter"><a href="#logging">16. Logging</a></span></dt><dd><dl><dt><span class="section"><a href="#id450634">Logging configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#id450648">Loggers</a></span></dt><dt><span class="section"><a href="#id450951">Output Options</a></span></dt><dt><span class="section"><a href="#id451145">Example session</a></span></dt></dl></dd><dt><span class="section"><a href="#id451402">Logging Message Format</a></span></dt></dl></dd></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>3.1. <a href="#id448619"></a></dt></dl></div><div class="chapter" title="Chapter 1. Introduction"><div class="titlepage"><div><div><h2 class="title"><a name="intro"></a>Chapter 1. Introduction</h2></div></div></div><div class="toc"><p><b>Table of Cont
ents</b></p><dl><dt><span class="section"><a href="#id447299">Supported Platforms</a></span></dt><dt><span class="section"><a href="#id447312">Required Software</a></span></dt><dt><span class="section"><a href="#starting_stopping">Starting and Stopping the Server</a></span></dt><dt><span class="section"><a href="#managing_once_running">Managing BIND 10</a></span></dt></dl></div><p>
+ </p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#intro">1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="#id350395">Supported Platforms</a></span></dt><dt><span class="section"><a href="#id350407">Required Software</a></span></dt><dt><span class="section"><a href="#starting_stopping">Starting and Stopping the Server</a></span></dt><dt><span class="section"><a href="#managing_once_running">Managing BIND 10</a></span></dt></dl></dd><dt><span class="chapter"><a href="#installation">2. Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#id350861">Building Requirements</a></span></dt><dt><span class="section"><a href="#quickstart">Quick start</a></span></dt><dt><span class="section"><a href="#install">Installation from source</a></span></dt><dd><dl><dt><span class="section"><a href="#id351082">Download Tar File</a></span></dt><dt><span class="section"><a hre
f="#id351104">Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id350071">Configure before the build</a></span></dt><dt><span class="section"><a href="#id351357">Build</a></span></dt><dt><span class="section"><a href="#id351373">Install</a></span></dt><dt><span class="section"><a href="#id351400">Install Hierarchy</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#bind10">3. Starting BIND10 with <span class="command"><strong>bind10</strong></span></a></span></dt><dd><dl><dt><span class="section"><a href="#start">Starting BIND 10</a></span></dt><dt><span class="section"><a href="#bind10.config">Configuration of started processes</a></span></dt></dl></dd><dt><span class="chapter"><a href="#msgq">4. Command channel</a></span></dt><dt><span class="chapter"><a href="#cfgmgr">5. Configuration manager</a></span></dt><dt><span class="chapter"><a href="#cmdctl">6. Remote control daemon</a></span></dt><dd><dl><dt><span class="section"><a href="#c
mdctl.spec">Configuration specification for b10-cmdctl</a></span></dt></dl></dd><dt><span class="chapter"><a href="#bindctl">7. Control and configure user interface</a></span></dt><dt><span class="chapter"><a href="#authserver">8. Authoritative Server</a></span></dt><dd><dl><dt><span class="section"><a href="#id352438">Server Configurations</a></span></dt><dt><span class="section"><a href="#id352511">Data Source Backends</a></span></dt><dt><span class="section"><a href="#id352547">Loading Master Zones Files</a></span></dt></dl></dd><dt><span class="chapter"><a href="#xfrin">9. Incoming Zone Transfers</a></span></dt><dd><dl><dt><span class="section"><a href="#id352701">Configuration for Incoming Zone Transfers</a></span></dt><dt><span class="section"><a href="#id352746">Enabling IXFR</a></span></dt><dt><span class="section"><a href="#zonemgr">Secondary Manager</a></span></dt><dt><span class="section"><a href="#id352888">Trigger an Incoming Zone Transfer Manually</a></span></d
t></dl></dd><dt><span class="chapter"><a href="#xfrout">10. Outbound Zone Transfers</a></span></dt><dt><span class="chapter"><a href="#resolverserver">11. Recursive Name Server</a></span></dt><dd><dl><dt><span class="section"><a href="#id353201">Access Control</a></span></dt><dt><span class="section"><a href="#id353340">Forwarding</a></span></dt></dl></dd><dt><span class="chapter"><a href="#dhcp4">12. DHCPv4 Server</a></span></dt><dd><dl><dt><span class="section"><a href="#dhcp4-usage">DHCPv4 Server Usage</a></span></dt><dt><span class="section"><a href="#dhcp4-config">DHCPv4 Server Configuration</a></span></dt><dt><span class="section"><a href="#dhcp4-limit">DHCPv4 Server Limitations</a></span></dt></dl></dd><dt><span class="chapter"><a href="#dhcp6">13. DHCPv6 Server</a></span></dt><dd><dl><dt><span class="section"><a href="#dhcp6-usage">DHCPv6 Server Usage</a></span></dt><dt><span class="section"><a href="#dhcp6-config">DHCPv6 Server Configuration</a></span></dt><dt><span
class="section"><a href="#dhcp6-limit">DHCPv6 Server Limitations</a></span></dt></dl></dd><dt><span class="chapter"><a href="#libdhcp">14. libdhcp++ library</a></span></dt><dd><dl><dt><span class="section"><a href="#iface-detect">Interface detection</a></span></dt><dt><span class="section"><a href="#packet-handling">DHCPv4/DHCPv6 packet handling</a></span></dt></dl></dd><dt><span class="chapter"><a href="#statistics">15. Statistics</a></span></dt><dt><span class="chapter"><a href="#logging">16. Logging</a></span></dt><dd><dl><dt><span class="section"><a href="#id353968">Logging configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#id353982">Loggers</a></span></dt><dt><span class="section"><a href="#id354286">Output Options</a></span></dt><dt><span class="section"><a href="#id354480">Example session</a></span></dt></dl></dd><dt><span class="section"><a href="#id354736">Logging Message Format</a></span></dt></dl></dd></dl></div><div class="list-of-tables"><
p><b>List of Tables</b></p><dl><dt>3.1. <a href="#id351715"></a></dt></dl></div><div class="chapter" title="Chapter 1. Introduction"><div class="titlepage"><div><div><h2 class="title"><a name="intro"></a>Chapter 1. Introduction</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id350395">Supported Platforms</a></span></dt><dt><span class="section"><a href="#id350407">Required Software</a></span></dt><dt><span class="section"><a href="#starting_stopping">Starting and Stopping the Server</a></span></dt><dt><span class="section"><a href="#managing_once_running">Managing BIND 10</a></span></dt></dl></div><p>
BIND is the popular implementation of a DNS server, developer
interfaces, and DNS tools.
BIND 10 is a rewrite of BIND 9. BIND 10 is written in C++ and Python
@@ -20,7 +20,7 @@
BIND 10 provides a EDNS0- and DNSSEC-capable
authoritative DNS server and a caching recursive name server
which also provides forwarding.
- </p></div><div class="section" title="Supported Platforms"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id447299"></a>Supported Platforms</h2></div></div></div><p>
+ </p></div><div class="section" title="Supported Platforms"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id350395"></a>Supported Platforms</h2></div></div></div><p>
BIND 10 builds have been tested on Debian GNU/Linux 5,
Ubuntu 9.10, NetBSD 5, Solaris 10, FreeBSD 7 and 8, and CentOS
Linux 5.3.
@@ -30,7 +30,7 @@
It is planned for BIND 10 to build, install and run on
Windows and standard Unix-type platforms.
- </p></div><div class="section" title="Required Software"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id447312"></a>Required Software</h2></div></div></div><p>
+ </p></div><div class="section" title="Required Software"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id350407"></a>Required Software</h2></div></div></div><p>
BIND 10 requires Python 3.1. Later versions may work, but Python
3.1 is the minimum version which will work.
</p><p>
@@ -140,7 +140,7 @@
and, of course, DNS. These include detailed developer
documentation and code examples.
- </p></div><div class="chapter" title="Chapter 2. Installation"><div class="titlepage"><div><div><h2 class="title"><a name="installation"></a>Chapter 2. Installation</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id447765">Building Requirements</a></span></dt><dt><span class="section"><a href="#quickstart">Quick start</a></span></dt><dt><span class="section"><a href="#install">Installation from source</a></span></dt><dd><dl><dt><span class="section"><a href="#id447986">Download Tar File</a></span></dt><dt><span class="section"><a href="#id448009">Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id446976">Configure before the build</a></span></dt><dt><span class="section"><a href="#id448261">Build</a></span></dt><dt><span class="section"><a href="#id448278">Install</a></span></dt><dt><span class="section"><a href="#id448304">Install Hierarchy</a></span></dt></dl></dd></dl></div><div class="s
ection" title="Building Requirements"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id447765"></a>Building Requirements</h2></div></div></div><p>
+ </p></div><div class="chapter" title="Chapter 2. Installation"><div class="titlepage"><div><div><h2 class="title"><a name="installation"></a>Chapter 2. Installation</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id350861">Building Requirements</a></span></dt><dt><span class="section"><a href="#quickstart">Quick start</a></span></dt><dt><span class="section"><a href="#install">Installation from source</a></span></dt><dd><dl><dt><span class="section"><a href="#id351082">Download Tar File</a></span></dt><dt><span class="section"><a href="#id351104">Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id350071">Configure before the build</a></span></dt><dt><span class="section"><a href="#id351357">Build</a></span></dt><dt><span class="section"><a href="#id351373">Install</a></span></dt><dt><span class="section"><a href="#id351400">Install Hierarchy</a></span></dt></dl></dd></dl></div><div class="s
ection" title="Building Requirements"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id350861"></a>Building Requirements</h2></div></div></div><p>
In addition to the run-time requirements, building BIND 10
from source code requires various development include headers.
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
@@ -204,14 +204,14 @@
the Git code revision control system or as a downloadable
tar file. It may also be available in pre-compiled ready-to-use
packages from operating system vendors.
- </p><div class="section" title="Download Tar File"><div class="titlepage"><div><div><h3 class="title"><a name="id447986"></a>Download Tar File</h3></div></div></div><p>
+ </p><div class="section" title="Download Tar File"><div class="titlepage"><div><div><h3 class="title"><a name="id351082"></a>Download Tar File</h3></div></div></div><p>
Downloading a release tar file is the recommended method to
obtain the source code.
</p><p>
The BIND 10 releases are available as tar file downloads from
<a class="ulink" href="ftp://ftp.isc.org/isc/bind10/" target="_top">ftp://ftp.isc.org/isc/bind10/</a>.
Periodic development snapshots may also be available.
- </p></div><div class="section" title="Retrieve from Git"><div class="titlepage"><div><div><h3 class="title"><a name="id448009"></a>Retrieve from Git</h3></div></div></div><p>
+ </p></div><div class="section" title="Retrieve from Git"><div class="titlepage"><div><div><h3 class="title"><a name="id351104"></a>Retrieve from Git</h3></div></div></div><p>
Downloading this "bleeding edge" code is recommended only for
developers or advanced users. Using development code in a production
environment is not recommended.
@@ -245,7 +245,7 @@
<span class="command"><strong>autoheader</strong></span>,
<span class="command"><strong>automake</strong></span>,
and related commands.
- </p></div><div class="section" title="Configure before the build"><div class="titlepage"><div><div><h3 class="title"><a name="id446976"></a>Configure before the build</h3></div></div></div><p>
+ </p></div><div class="section" title="Configure before the build"><div class="titlepage"><div><div><h3 class="title"><a name="id350071"></a>Configure before the build</h3></div></div></div><p>
BIND 10 uses the GNU Build System to discover build environment
details.
To generate the makefiles using the defaults, simply run:
@@ -276,16 +276,16 @@
</p><p>
If the configure fails, it may be due to missing or old
dependencies.
- </p></div><div class="section" title="Build"><div class="titlepage"><div><div><h3 class="title"><a name="id448261"></a>Build</h3></div></div></div><p>
+ </p></div><div class="section" title="Build"><div class="titlepage"><div><div><h3 class="title"><a name="id351357"></a>Build</h3></div></div></div><p>
After the configure step is complete, to build the executables
from the C++ code and prepare the Python scripts, run:
</p><pre class="screen">$ <strong class="userinput"><code>make</code></strong></pre><p>
- </p></div><div class="section" title="Install"><div class="titlepage"><div><div><h3 class="title"><a name="id448278"></a>Install</h3></div></div></div><p>
+ </p></div><div class="section" title="Install"><div class="titlepage"><div><div><h3 class="title"><a name="id351373"></a>Install</h3></div></div></div><p>
To install the BIND 10 executables, support files,
and documentation, run:
</p><pre class="screen">$ <strong class="userinput"><code>make install</code></strong></pre><p>
- </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The install step may require superuser privileges.</p></div></div><div class="section" title="Install Hierarchy"><div class="titlepage"><div><div><h3 class="title"><a name="id448304"></a>Install Hierarchy</h3></div></div></div><p>
+ </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The install step may require superuser privileges.</p></div></div><div class="section" title="Install Hierarchy"><div class="titlepage"><div><div><h3 class="title"><a name="id351400"></a>Install Hierarchy</h3></div></div></div><p>
The following is the layout of the complete BIND 10 installation:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
<code class="filename">bin/</code> —
@@ -385,7 +385,7 @@
during startup or shutdown. Unless specified, the component is started
in usual way. This is the list of components that need to be started
in a special way, with the value of special used for them:
- </p><div class="table"><a name="id448619"></a><p class="title"><b>Table 3.1. </b></p><div class="table-contents"><table border="1"><colgroup><col align="left"><col align="left"><col align="left"></colgroup><thead><tr><th align="left">Component</th><th align="left">Special</th><th align="left">Description</th></tr></thead><tbody><tr><td align="left">b10-auth</td><td align="left">auth</td><td align="left">Authoritative server</td></tr><tr><td align="left">b10-resolver</td><td align="left">resolver</td><td align="left">The resolver</td></tr><tr><td align="left">b10-cmdctl</td><td align="left">cmdctl</td><td align="left">The command control (remote control interface)</td></tr><tr><td align="left">setuid</td><td align="left">setuid</td><td align="left">Virtual component, see below</td></tr></tbody></table></div></div><p><br class="table-break">
+ </p><div class="table"><a name="id351715"></a><p class="title"><b>Table 3.1. </b></p><div class="table-contents"><table border="1"><colgroup><col align="left"><col align="left"><col align="left"></colgroup><thead><tr><th align="left">Component</th><th align="left">Special</th><th align="left">Description</th></tr></thead><tbody><tr><td align="left">b10-auth</td><td align="left">auth</td><td align="left">Authoritative server</td></tr><tr><td align="left">b10-resolver</td><td align="left">resolver</td><td align="left">The resolver</td></tr><tr><td align="left">b10-cmdctl</td><td align="left">cmdctl</td><td align="left">The command control (remote control interface)</td></tr><tr><td align="left">setuid</td><td align="left">setuid</td><td align="left">Virtual component, see below</td></tr></tbody></table></div></div><p><br class="table-break">
</p><p>
The kind specifies how a failure of the component should
be handled. If it is set to <span class="quote">“<span class="quote">dispensable</span>”</span>
@@ -610,12 +610,12 @@ shutdown
the details and relays (over a <span class="command"><strong>b10-msgq</strong></span> command
channel) the configuration on to the specified module.
</p><p>
- </p></div><div class="chapter" title="Chapter 8. Authoritative Server"><div class="titlepage"><div><div><h2 class="title"><a name="authserver"></a>Chapter 8. Authoritative Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id449342">Server Configurations</a></span></dt><dt><span class="section"><a href="#id449416">Data Source Backends</a></span></dt><dt><span class="section"><a href="#id449451">Loading Master Zones Files</a></span></dt></dl></div><p>
+ </p></div><div class="chapter" title="Chapter 8. Authoritative Server"><div class="titlepage"><div><div><h2 class="title"><a name="authserver"></a>Chapter 8. Authoritative Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id352438">Server Configurations</a></span></dt><dt><span class="section"><a href="#id352511">Data Source Backends</a></span></dt><dt><span class="section"><a href="#id352547">Loading Master Zones Files</a></span></dt></dl></div><p>
The <span class="command"><strong>b10-auth</strong></span> is the authoritative DNS server.
It supports EDNS0 and DNSSEC. It supports IPv6.
Normally it is started by the <span class="command"><strong>bind10</strong></span> master
process.
- </p><div class="section" title="Server Configurations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id449342"></a>Server Configurations</h2></div></div></div><p>
+ </p><div class="section" title="Server Configurations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id352438"></a>Server Configurations</h2></div></div></div><p>
<span class="command"><strong>b10-auth</strong></span> is configured via the
<span class="command"><strong>b10-cfgmgr</strong></span> configuration manager.
The module name is <span class="quote">“<span class="quote">Auth</span>”</span>.
@@ -635,7 +635,7 @@ This may be a temporary setting until then.
</p><div class="variablelist"><dl><dt><span class="term">shutdown</span></dt><dd>Stop the authoritative DNS server.
</dd></dl></div><p>
- </p></div><div class="section" title="Data Source Backends"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id449416"></a>Data Source Backends</h2></div></div></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
+ </p></div><div class="section" title="Data Source Backends"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id352511"></a>Data Source Backends</h2></div></div></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
For the development prototype release, <span class="command"><strong>b10-auth</strong></span>
supports a SQLite3 data source backend and in-memory data source
backend.
@@ -649,7 +649,7 @@ This may be a temporary setting until then.
The default is <code class="filename">/usr/local/var/</code>.)
This data file location may be changed by defining the
<span class="quote">“<span class="quote">database_file</span>”</span> configuration.
- </p></div><div class="section" title="Loading Master Zones Files"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id449451"></a>Loading Master Zones Files</h2></div></div></div><p>
+ </p></div><div class="section" title="Loading Master Zones Files"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id352547"></a>Loading Master Zones Files</h2></div></div></div><p>
RFC 1035 style DNS master zone files may imported
into a BIND 10 data source by using the
<span class="command"><strong>b10-loadzone</strong></span> utility.
@@ -678,7 +678,7 @@ This may be a temporary setting until then.
If you reload a zone already existing in the database,
all records from that prior zone disappear and a whole new set
appears.
- </p></div></div><div class="chapter" title="Chapter 9. Incoming Zone Transfers"><div class="titlepage"><div><div><h2 class="title"><a name="xfrin"></a>Chapter 9. Incoming Zone Transfers</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id449606">Configuration for Incoming Zone Transfers</a></span></dt><dt><span class="section"><a href="#id449650">Enabling IXFR</a></span></dt><dt><span class="section"><a href="#zonemgr">Secondary Manager</a></span></dt><dt><span class="section"><a href="#id449793">Trigger an Incoming Zone Transfer Manually</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter" title="Chapter 9. Incoming Zone Transfers"><div class="titlepage"><div><div><h2 class="title"><a name="xfrin"></a>Chapter 9. Incoming Zone Transfers</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id352701">Configuration for Incoming Zone Transfers</a></span></dt><dt><span class="section"><a href="#id352746">Enabling IXFR</a></span></dt><dt><span class="section"><a href="#zonemgr">Secondary Manager</a></span></dt><dt><span class="section"><a href="#id352888">Trigger an Incoming Zone Transfer Manually</a></span></dt></dl></div><p>
Incoming zones are transferred using the <span class="command"><strong>b10-xfrin</strong></span>
process which is started by <span class="command"><strong>bind10</strong></span>.
When received, the zone is stored in the corresponding BIND 10
@@ -696,7 +696,7 @@ This may be a temporary setting until then.
In the current development release of BIND 10, incoming zone
transfers are only available for SQLite3-based data sources,
that is, they don't work for an in-memory data source.
- </p></div><div class="section" title="Configuration for Incoming Zone Transfers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id449606"></a>Configuration for Incoming Zone Transfers</h2></div></div></div><p>
+ </p></div><div class="section" title="Configuration for Incoming Zone Transfers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id352701"></a>Configuration for Incoming Zone Transfers</h2></div></div></div><p>
In practice, you need to specify a list of secondary zones to
enable incoming zone transfers for these zones (you can still
trigger a zone transfer manually, without a prior configuration
@@ -712,7 +712,7 @@ This may be a temporary setting until then.
> <strong class="userinput"><code>config commit</code></strong></pre><p>
(We assume there has been no zone configuration before).
- </p></div><div class="section" title="Enabling IXFR"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id449650"></a>Enabling IXFR</h2></div></div></div><p>
+ </p></div><div class="section" title="Enabling IXFR"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id352746"></a>Enabling IXFR</h2></div></div></div><p>
As noted above, <span class="command"><strong>b10-xfrin</strong></span> uses AXFR for
zone transfers by default. To enable IXFR for zone transfers
for a particular zone, set the <strong class="userinput"><code>use_ixfr</code></strong>
@@ -764,7 +764,7 @@ This may be a temporary setting until then.
(i.e. no SOA record for it), <span class="command"><strong>b10-zonemgr</strong></span>
will automatically tell <span class="command"><strong>b10-xfrin</strong></span>
to transfer the zone in.
- </p></div><div class="section" title="Trigger an Incoming Zone Transfer Manually"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id449793"></a>Trigger an Incoming Zone Transfer Manually</h2></div></div></div><p>
+ </p></div><div class="section" title="Trigger an Incoming Zone Transfer Manually"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id352888"></a>Trigger an Incoming Zone Transfer Manually</h2></div></div></div><p>
To manually trigger a zone transfer to retrieve a remote zone,
you may use the <span class="command"><strong>bindctl</strong></span> utility.
For example, at the <span class="command"><strong>bindctl</strong></span> prompt run:
@@ -821,7 +821,7 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)</pre><p>
use the system wide TSIG configuration.
The way to specify zone specific configuration (ACLs, etc) is
likely to be changed, too.
- </p></div></div><div class="chapter" title="Chapter 11. Recursive Name Server"><div class="titlepage"><div><div><h2 class="title"><a name="resolverserver"></a>Chapter 11. Recursive Name Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id450106">Access Control</a></span></dt><dt><span class="section"><a href="#id450245">Forwarding</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter" title="Chapter 11. Recursive Name Server"><div class="titlepage"><div><div><h2 class="title"><a name="resolverserver"></a>Chapter 11. Recursive Name Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id353201">Access Control</a></span></dt><dt><span class="section"><a href="#id353340">Forwarding</a></span></dt></dl></div><p>
The <span class="command"><strong>b10-resolver</strong></span> process is started by
<span class="command"><strong>bind10</strong></span>.
@@ -860,7 +860,7 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)</pre><p>
</pre><p>
</p><p>(Replace the <span class="quote">“<span class="quote"><em class="replaceable"><code>2</code></em></span>”</span>
as needed; run <span class="quote">“<span class="quote"><strong class="userinput"><code>config show
- Resolver/listen_on</code></strong></span>”</span> if needed.)</p><div class="section" title="Access Control"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id450106"></a>Access Control</h2></div></div></div><p>
+ Resolver/listen_on</code></strong></span>”</span> if needed.)</p><div class="section" title="Access Control"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id353201"></a>Access Control</h2></div></div></div><p>
By default, the <span class="command"><strong>b10-resolver</strong></span> daemon only accepts
DNS queries from the localhost (127.0.0.1 and ::1).
The <code class="option">Resolver/query_acl</code> configuration may
@@ -893,7 +893,7 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)</pre><p>
</pre><p>(Replace the <span class="quote">“<span class="quote"><em class="replaceable"><code>2</code></em></span>”</span>
as needed; run <span class="quote">“<span class="quote"><strong class="userinput"><code>config show
Resolver/query_acl</code></strong></span>”</span> if needed.)</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>This prototype access control configuration
- syntax may be changed.</p></div></div><div class="section" title="Forwarding"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id450245"></a>Forwarding</h2></div></div></div><p>
+ syntax may be changed.</p></div></div><div class="section" title="Forwarding"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id353340"></a>Forwarding</h2></div></div></div><p>
To enable forwarding, the upstream address and port must be
configured to forward queries to, such as:
@@ -913,7 +913,7 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)</pre><p>
> <strong class="userinput"><code>config set Resolver/forward_addresses []</code></strong>
> <strong class="userinput"><code>config commit</code></strong>
</pre><p>
- </p></div></div><div class="chapter" title="Chapter 12. DHCPv4 Server"><div class="titlepage"><div><div><h2 class="title"><a name="dhcp4"></a>Chapter 12. DHCPv4 Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id450334">Server Usage</a></span></dt><dt><span class="section"><a href="#dhcp4-config">Server Configuration</a></span></dt><dt><span class="section"><a href="#dhcp4-limit">DHCPv4 Server Limitations</a></span></dt></dl></div><p>Dynamic Host Configuration Protocol for IPv4 (DHCP or
+ </p></div></div><div class="chapter" title="Chapter 12. DHCPv4 Server"><div class="titlepage"><div><div><h2 class="title"><a name="dhcp4"></a>Chapter 12. DHCPv4 Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#dhcp4-usage">DHCPv4 Server Usage</a></span></dt><dt><span class="section"><a href="#dhcp4-config">DHCPv4 Server Configuration</a></span></dt><dt><span class="section"><a href="#dhcp4-limit">DHCPv4 Server Limitations</a></span></dt></dl></div><p>Dynamic Host Configuration Protocol for IPv4 (DHCP or
DHCPv4) and Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
are protocols that allow one node (server) to provision
configuration parameters to many hosts and devices (clients). To
@@ -922,7 +922,8 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)</pre><p>
clients. Even though principles of both DHCPv4 and DHCPv6 are
somewhat similar, these are two radically different
protocols. BIND10 offers server implementations for both DHCPv4
- and DHCPv6.</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
+ and DHCPv6. This chapter is about DHCP for IPv4. For description of
+ DHCPv6 server, see <a class="xref" href="#dhcp6" title="Chapter 13. DHCPv6 Server">Chapter 13, <i>DHCPv6 Server</i></a>.</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
As of December 2011, both DHCPv4 and DHCPv6 components are
skeleton servers. That means that while they are capable of
performing DHCP configuration, they are not fully functional
@@ -930,7 +931,7 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)</pre><p>
databases. This means that they will assign the same, fixed,
hardcoded addresses to any client that will ask. See <a class="xref" href="#dhcp4-limit" title="DHCPv4 Server Limitations">the section called “DHCPv4 Server Limitations”</a> and <a class="xref" href="#dhcp6-limit" title="DHCPv6 Server Limitations">the section called “DHCPv6 Server Limitations”</a> for
detailed description.
- </p></div><div class="section" title="Server Usage"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id450334"></a>Server Usage</h2></div></div></div><p>BIND10 provides experimental DHCPv4 server component since
+ </p></div><div class="section" title="DHCPv4 Server Usage"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp4-usage"></a>DHCPv4 Server Usage</h2></div></div></div><p>BIND10 provides DHCPv4 server component since
December 2011. It is currently described as skeleton server and
can be described as an early prototype that is not yet fully
functional. It is mature enough to conduct first tests in lab
@@ -962,7 +963,7 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)</pre><p>
As DHCPv4 server opens privileged ports, it requires root
access. Make sure you run this daemon as root.
- </p></div><div class="section" title="Server Configuration"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp4-config"></a>Server Configuration</h2></div></div></div><p>
+ </p></div><div class="section" title="DHCPv4 Server Configuration"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp4-config"></a>DHCPv4 Server Configuration</h2></div></div></div><p>
DHCPv4 server does not have lease database implemented yet
or any support for configuration, so every time the same set
of configuration options (including the same fixed address)
@@ -972,46 +973,131 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)</pre><p>
configuration is to tweak its source code. To do so, please edit
src/bin/dhcp4/dhcp4_srv.cc file and modify following parameters:
</p><pre class="screen">
-const std::string HARDCODED_LEASE = "10.3.2.222"; // assigned lease
+const std::string HARDCODED_LEASE = "192.0.2.222"; // assigned lease
const std::string HARDCODED_NETMASK = "255.255.255.0";
const uint32_t HARDCODED_LEASE_TIME = 60; // in seconds
-const std::string HARDCODED_GATEWAY = "10.3.2.2";
-const std::string HARDCODED_DNS_SERVER = "8.8.8.8";
-const std::string HARDCODED_DOMAIN_NAME = "isc.example.org";
-const std::string HARDCODED_SERVER_ID = "10.3.1.1";</pre><p>
+const std::string HARDCODED_GATEWAY = "192.0.2.1";
+const std::string HARDCODED_DNS_SERVER = "192.0.2.2";
+const std::string HARDCODED_DOMAIN_NAME = "isc.example.com";
+const std::string HARDCODED_SERVER_ID = "192.0.2.1";</pre><p>
Lease database and configuration support is planned for 2012.
</p></div><div class="section" title="DHCPv4 Server Limitations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp4-limit"></a>DHCPv4 Server Limitations</h2></div></div></div><p>
This are the current limitations of DHCPv4 server
software. Most of them are reflection of the early stage of
development.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">During initial IPv4 node configuration, where server has to
- send packet to a node that does not have IPv4 address
- assigned yet, server requires certain tricks (or hacks) to
- transmit such packets. This is not implemented yet, therefore
- DHCPv4 server supports relayed traffic only.</li><li class="listitem">It provides a single, fixed, hardcoded lease to
- any client that asks. There is no lease manager
- implemented. If two clients request addresses, they will
- both get the same fixed address.</li><li class="listitem">Server does not support any configuration
- mechanisms yet. The whole configuration is currently
- hardcoded. The only way to tweak configuration is to
- directly modify source code. See see <a class="xref" href="#dhcp4-config" title="Server Configuration">the section called “Server Configuration”</a> for details.</li><li class="listitem">Upon start, server will open sockets on all
+ </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">During initial IPv4 node configuration, where
+ server has to send packet to a node that does not have
+ IPv4 address assigned yet, server requires certain tricks
+ (or hacks) to transmit such packets. This is not
+ implemented yet, therefore DHCPv4 server supports relayed
+ traffic only.</li><li class="listitem"><span class="command"><strong>b10-dhcp4</strong></span> provides a single,
+ fixed, hardcoded lease to any client that asks. There is
+ no lease manager implemented. If two clients request
+ addresses, they will both get the same fixed
+ address.</li><li class="listitem"><span class="command"><strong>b10-dhcp4</strong></span> does not support any
+ configuration mechanisms yet. The whole configuration is
+ currently hardcoded. The only way to tweak configuration
+ is to directly modify source code. See see <a class="xref" href="#dhcp4-config" title="DHCPv4 Server Configuration">the section called “DHCPv4 Server Configuration”</a> for details.</li><li class="listitem">Upon start, server will open sockets on all
interfaces that are not loopback, are up and running and
have IPv4 address. Support for multiple interfaces is not
coded in reception routines yet, so if you are running
this code on a machine that has many interfaces and
<span class="command"><strong>b10-dhcp4</strong></span> happens to listen on wrong
- interface, the easiest way to is to down other
- interfaces. This limitation will be fixed shortly.</li><li class="listitem">PRL (Parameter Request List) is currently ignored
+ interface, the easiest way to work around this problem is
+ to down other interfaces. This limitation will be fixed
+ shortly.</li><li class="listitem">PRL (Parameter Request List) is currently ignored
and server assigns DNS SERVER and DOMAIN NAME
options.</li><li class="listitem"><span class="command"><strong>b10-dhcp4</strong></span> does not support
BOOTP. That is a design choice. This limitation is
- permanent. If have legacy nodes that can't use DHCP and
+ permanent. If you have legacy nodes that can't use DHCP and
require BOOTP support, please use latest version of ISC DHCP
<a class="ulink" href="http://www.isc.org/software/dhcp" target="_top">http://www.isc.org/software/dhcp</a>.</li><li class="listitem">Interface detection is currently working on Linux
- only. See <a class="xref" href="#iface-detect" title="Interface detection">the section called “Interface detection”</a> for details.</li></ul></div></div></div><div class="chapter" title="Chapter 13. DHCPv6 Server"><div class="titlepage"><div><div><h2 class="title"><a name="dhcp6-srv"></a>Chapter 13. DHCPv6 Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#dhcp6-limit">DHCPv6 Server Limitations</a></span></dt></dl></div><div class="section" title="DHCPv6 Server Limitations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp6-limit"></a>DHCPv6 Server Limitations</h2></div></div></div><p>
- Relayed traffic is not supported.
- </p></div></div><div class="chapter" title="Chapter 14. libdhcp++ library"><div class="titlepage"><div><div><h2 class="title"><a name="libdhcp++"></a>Chapter 14. libdhcp++ library</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#iface-detect">Interface detection</a></span></dt></dl></div><p>libdhcp++ is a common library written in C++ that is
+ only. See <a class="xref" href="#iface-detect" title="Interface detection">the section called “Interface detection”</a> for details.</li><li class="listitem">Address renewal (RENEW), rebinding (REBIND),
+ confirmation (CONFIRM), duplication report (DECLINE) and
+ release (RELEASE) are not supported yet.</li><li class="listitem">DNS Update is not supported yet.</li></ul></div></div></div><div class="chapter" title="Chapter 13. DHCPv6 Server"><div class="titlepage"><div><div><h2 class="title"><a name="dhcp6"></a>Chapter 13. DHCPv6 Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#dhcp6-usage">DHCPv6 Server Usage</a></span></dt><dt><span class="section"><a href="#dhcp6-config">DHCPv6 Server Configuration</a></span></dt><dt><span class="section"><a href="#dhcp6-limit">DHCPv6 Server Limitations</a></span></dt></dl></div><p>Dynamic Host Configuration Protocol for IPv6 (DHCPv6) is
+ specified in RFC3315. BIND10 provides DHCPv6 server implementation
+ that is described in this chapter. For DHCPv4 server
+ implementation, see <a class="xref" href="#dhcp4" title="Chapter 12. DHCPv4 Server">Chapter 12, <i>DHCPv4 Server</i></a>.
+ </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
+ As of December 2011, both DHCPv4 and DHCPv6 components are
+ skeleton servers. That means that while they are capable of
+ performing DHCP configuration, they are not fully functional
+ yet. In particular, both do not have functional lease
+ databases. This means that they will assign the same, fixed,
+ hardcoded addresses to any client that will ask. See <a class="xref" href="#dhcp4-limit" title="DHCPv4 Server Limitations">the section called “DHCPv4 Server Limitations”</a> and <a class="xref" href="#dhcp6-limit" title="DHCPv6 Server Limitations">the section called “DHCPv6 Server Limitations”</a> for
+ detailed description.
+ </p></div><div class="section" title="DHCPv6 Server Usage"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp6-usage"></a>DHCPv6 Server Usage</h2></div></div></div><p>
+ BIND10 provides DHCPv6 server component since September
+ 2011. It is currently described as skeleton server and can be
+ described as an early prototype that is not yet fully
+ functional. It is mature enough to conduct first tests in lab
+ environment, but it has significant limitations. See <a class="xref" href="#dhcp6-limit" title="DHCPv6 Server Limitations">the section called “DHCPv6 Server Limitations”</a> for details.
+ </p><p>
+ DHCPv6 server is implemented as <span class="command"><strong>b10-dhcp6</strong></span>
+ daemon. As it is configurable yet, it is fully autonomous,
+ i.e. it does not interact with <span class="command"><strong>b10-cfgmgr</strong></span>.
+ To start DHCPv6 server, simply input:
+
+ </p><pre class="screen">
+#<strong class="userinput"><code>cd src/bin/dhcp6</code></strong>
+#<strong class="userinput"><code>./b10-dhcp6</code></strong>
+</pre><p>
+
+ Depending on your installation, <span class="command"><strong>b10-dhcp6</strong></span>
+ binary may reside in src/bin/dhcp6 in your source code
+ directory, in /usr/local/bin/b10-dhcp6 or other directory
+ you specified during compilation.
+
+ Afre start, server will detect available network interfaces
+ and will attempt to open UDP sockets on all interfaces that
+ are up, running, are not loopback and have IPv4 address
+ assigned.
+
+ Server will then listen to incoming traffic. Currently
+ supported client messages are SOLICIT and REQUEST. Server
+ will respond to them with ADVERTISE and REPLY, respectively.
+
+ As DHCPv6 server opens privileged ports, it requires root
+ access. Make sure you run this daemon as root.
+ </p></div><div class="section" title="DHCPv6 Server Configuration"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp6-config"></a>DHCPv6 Server Configuration</h2></div></div></div><p>
+ DHCPv4 server does not have lease database implemented yet
+ or any support for configuration, so every time the same set
+ of configuration options (including the same fixed address)
+ will be assigned every time.
+ </p><p>
+ At this stage of development, the only way to alter server
+ configuration is to tweak its source code. To do so, please edit
+ src/bin/dhcp6/dhcp6_srv.cc file and modify following parameters:
+ </p><pre class="screen">
+const std::string HARDCODED_LEASE = "2001:db8:1::1234:abcd";
+const uint32_t HARDCODED_T1 = 1500; // in seconds
+const uint32_t HARDCODED_T2 = 2600; // in seconds
+const uint32_t HARDCODED_PREFERRED_LIFETIME = 3600; // in seconds
+const uint32_t HARDCODED_VALID_LIFETIME = 7200; // in seconds
+const std::string HARDCODED_DNS_SERVER = "2001:db8:1::1";</pre><p>
+
+ Lease database and configuration support is planned for 2012.
+ </p></div><div class="section" title="DHCPv6 Server Limitations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp6-limit"></a>DHCPv6 Server Limitations</h2></div></div></div><p>
+ </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">Relayed traffic is not supported.</li><li class="listitem"><span class="command"><strong>b10-dhcp6</strong></span> provides a single,
+ fixed, hardcoded lease to any client that asks. There is no
+ lease manager implemented. If two clients request addresses,
+ they will both get the same fixed address.</li><li class="listitem"><span class="command"><strong>b10-dhcp6</strong></span> does not support any
+ configuration mechanisms yet. The whole configuration is
+ currently hardcoded. The only way to tweak configuration
+ is to directly modify source code. See see <a class="xref" href="#dhcp6-config" title="DHCPv6 Server Configuration">the section called “DHCPv6 Server Configuration”</a> for details.</li><li class="listitem">Upon start, server will open sockets on all
+ interfaces that are not loopback, are up, running and are
+ multicast capable and have IPv6 address. Support for
+ multiple interfaces is not coded in reception routines yet,
+ so if you are running this code on a machine that has many
+ interfaces and <span class="command"><strong>b10-dhcp6</strong></span> happens to
+ listen on wrong interface, the easiest way to work around
+ this problem is to down other interfaces. This limitation
+ will be fixed shortly.</li><li class="listitem">Temporary addresses are not supported yet.</li><li class="listitem">Prefix delegation is not supported yet.</li><li class="listitem">Address renewal (RENEW), rebinding (REBIND),
+ confirmation (CONFIRM), duplication report (DECLINE) and
+ release (RELEASE) are not supported yet.</li><li class="listitem">DNS Update is not supported yet.</li><li class="listitem">Interface detection is currently working on Linux
+ only. See <a class="xref" href="#iface-detect" title="Interface detection">the section called “Interface detection”</a> for details.</li></ul></div><p>
+ </p></div></div><div class="chapter" title="Chapter 14. libdhcp++ library"><div class="titlepage"><div><div><h2 class="title"><a name="libdhcp"></a>Chapter 14. libdhcp++ library</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#iface-detect">Interface detection</a></span></dt><dt><span class="section"><a href="#packet-handling">DHCPv4/DHCPv6 packet handling</a></span></dt></dl></div><p>libdhcp++ is a common library written in C++ that is
handles many DHCP-related tasks, like DHCPv4 and DHCPv6 packets
parsing, manipulation and assembly, option parsing, manipulation
and assembly, network interface detection and socket operations.
@@ -1038,7 +1124,7 @@ eth0 fe80::21e:8cff:fe9b:7349
# For DHCPv4, please use following format:
#eth0 192.0.2.5</pre><p>
- </p></div></div><div class="chapter" title="Chapter 15. Statistics"><div class="titlepage"><div><div><h2 class="title"><a name="statistics"></a>Chapter 15. Statistics</h2></div></div></div><p>
+ </p></div><div class="section" title="DHCPv4/DHCPv6 packet handling"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="packet-handling"></a>DHCPv4/DHCPv6 packet handling</h2></div></div></div><p>TODO: Describe packet handling here, with pointers to wiki</p></div></div><div class="chapter" title="Chapter 15. Statistics"><div class="titlepage"><div><div><h2 class="title"><a name="statistics"></a>Chapter 15. Statistics</h2></div></div></div><p>
The <span class="command"><strong>b10-stats</strong></span> process is started by
<span class="command"><strong>bind10</strong></span>.
It periodically collects statistics data from various modules
@@ -1072,7 +1158,7 @@ eth0 fe80::21e:8cff:fe9b:7349
}
}
</pre><p>
- </p></div><div class="chapter" title="Chapter 16. Logging"><div class="titlepage"><div><div><h2 class="title"><a name="logging"></a>Chapter 16. Logging</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id450634">Logging configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#id450648">Loggers</a></span></dt><dt><span class="section"><a href="#id450951">Output Options</a></span></dt><dt><span class="section"><a href="#id451145">Example session</a></span></dt></dl></dd><dt><span class="section"><a href="#id451402">Logging Message Format</a></span></dt></dl></div><div class="section" title="Logging configuration"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id450634"></a>Logging configuration</h2></div></div></div><p>
+ </p></div><div class="chapter" title="Chapter 16. Logging"><div class="titlepage"><div><div><h2 class="title"><a name="logging"></a>Chapter 16. Logging</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id353968">Logging configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#id353982">Loggers</a></span></dt><dt><span class="section"><a href="#id354286">Output Options</a></span></dt><dt><span class="section"><a href="#id354480">Example session</a></span></dt></dl></dd><dt><span class="section"><a href="#id354736">Logging Message Format</a></span></dt></dl></div><div class="section" title="Logging configuration"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id353968"></a>Logging configuration</h2></div></div></div><p>
The logging system in BIND 10 is configured through the
Logging module. All BIND 10 modules will look at the
@@ -1081,7 +1167,7 @@ eth0 fe80::21e:8cff:fe9b:7349
- </p><div class="section" title="Loggers"><div class="titlepage"><div><div><h3 class="title"><a name="id450648"></a>Loggers</h3></div></div></div><p>
+ </p><div class="section" title="Loggers"><div class="titlepage"><div><div><h3 class="title"><a name="id353982"></a>Loggers</h3></div></div></div><p>
Within BIND 10, a message is logged through a component
called a "logger". Different parts of BIND 10 log messages
@@ -1102,7 +1188,7 @@ eth0 fe80::21e:8cff:fe9b:7349
(what to log), and the <code class="option">output_options</code>
(where to log).
- </p><div class="section" title="name (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id450680"></a>name (string)</h4></div></div></div><p>
+ </p><div class="section" title="name (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id354014"></a>name (string)</h4></div></div></div><p>
Each logger in the system has a name, the name being that
of the component using it to log messages. For instance,
if you want to configure logging for the resolver module,
@@ -1175,7 +1261,7 @@ eth0 fe80::21e:8cff:fe9b:7349
<span class="quote">“<span class="quote">Auth.cache</span>”</span> logger will appear in the output
with a logger name of <span class="quote">“<span class="quote">b10-auth.cache</span>”</span>).
- </p></div><div class="section" title="severity (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id450813"></a>severity (string)</h4></div></div></div><p>
+ </p></div><div class="section" title="severity (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id354148"></a>severity (string)</h4></div></div></div><p>
This specifies the category of messages logged.
Each message is logged with an associated severity which
@@ -1191,7 +1277,7 @@ eth0 fe80::21e:8cff:fe9b:7349
- </p></div><div class="section" title="output_options (list)"><div class="titlepage"><div><div><h4 class="title"><a name="id450871"></a>output_options (list)</h4></div></div></div><p>
+ </p></div><div class="section" title="output_options (list)"><div class="titlepage"><div><div><h4 class="title"><a name="id354206"></a>output_options (list)</h4></div></div></div><p>
Each logger can have zero or more
<code class="option">output_options</code>. These specify where log
@@ -1201,7 +1287,7 @@ eth0 fe80::21e:8cff:fe9b:7349
The other options for a logger are:
- </p></div><div class="section" title="debuglevel (integer)"><div class="titlepage"><div><div><h4 class="title"><a name="id450890"></a>debuglevel (integer)</h4></div></div></div><p>
+ </p></div><div class="section" title="debuglevel (integer)"><div class="titlepage"><div><div><h4 class="title"><a name="id354225"></a>debuglevel (integer)</h4></div></div></div><p>
When a logger's severity is set to DEBUG, this value
specifies what debug messages should be printed. It ranges
@@ -1210,7 +1296,7 @@ eth0 fe80::21e:8cff:fe9b:7349
If severity for the logger is not DEBUG, this value is ignored.
- </p></div><div class="section" title="additive (true or false)"><div class="titlepage"><div><div><h4 class="title"><a name="id450910"></a>additive (true or false)</h4></div></div></div><p>
+ </p></div><div class="section" title="additive (true or false)"><div class="titlepage"><div><div><h4 class="title"><a name="id354244"></a>additive (true or false)</h4></div></div></div><p>
If this is true, the <code class="option">output_options</code> from
the parent will be used. For example, if there are two
@@ -1224,18 +1310,18 @@ eth0 fe80::21e:8cff:fe9b:7349
- </p></div></div><div class="section" title="Output Options"><div class="titlepage"><div><div><h3 class="title"><a name="id450951"></a>Output Options</h3></div></div></div><p>
+ </p></div></div><div class="section" title="Output Options"><div class="titlepage"><div><div><h3 class="title"><a name="id354286"></a>Output Options</h3></div></div></div><p>
The main settings for an output option are the
<code class="option">destination</code> and a value called
<code class="option">output</code>, the meaning of which depends on
the destination that is set.
- </p><div class="section" title="destination (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id450969"></a>destination (string)</h4></div></div></div><p>
+ </p><div class="section" title="destination (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id354303"></a>destination (string)</h4></div></div></div><p>
The destination is the type of output. It can be one of:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"> console </li><li class="listitem"> file </li><li class="listitem"> syslog </li></ul></div></div><div class="section" title="output (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id451002"></a>output (string)</h4></div></div></div><p>
+ </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"> console </li><li class="listitem"> file </li><li class="listitem"> syslog </li></ul></div></div><div class="section" title="output (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id354337"></a>output (string)</h4></div></div></div><p>
Depending on what is set as the output destination, this
value is interpreted as follows:
@@ -1257,12 +1343,12 @@ eth0 fe80::21e:8cff:fe9b:7349
The other options for <code class="option">output_options</code> are:
- </p><div class="section" title="flush (true of false)"><div class="titlepage"><div><div><h5 class="title"><a name="id451096"></a>flush (true of false)</h5></div></div></div><p>
+ </p><div class="section" title="flush (true of false)"><div class="titlepage"><div><div><h5 class="title"><a name="id354430"></a>flush (true of false)</h5></div></div></div><p>
Flush buffers after each log message. Doing this will
reduce performance but will ensure that if the program
terminates abnormally, all messages up to the point of
termination are output.
- </p></div><div class="section" title="maxsize (integer)"><div class="titlepage"><div><div><h5 class="title"><a name="id451108"></a>maxsize (integer)</h5></div></div></div><p>
+ </p></div><div class="section" title="maxsize (integer)"><div class="titlepage"><div><div><h5 class="title"><a name="id354442"></a>maxsize (integer)</h5></div></div></div><p>
Only relevant when destination is file, this is maximum
file size of output files in bytes. When the maximum
size is reached, the file is renamed and a new file opened.
@@ -1271,11 +1357,11 @@ eth0 fe80::21e:8cff:fe9b:7349
etc.)
</p><p>
If this is 0, no maximum file size is used.
- </p></div><div class="section" title="maxver (integer)"><div class="titlepage"><div><div><h5 class="title"><a name="id451125"></a>maxver (integer)</h5></div></div></div><p>
+ </p></div><div class="section" title="maxver (integer)"><div class="titlepage"><div><div><h5 class="title"><a name="id354459"></a>maxver (integer)</h5></div></div></div><p>
Maximum number of old log files to keep around when
rolling the output file. Only relevant when
<code class="option">destination</code> is <span class="quote">“<span class="quote">file</span>”</span>.
- </p></div></div></div><div class="section" title="Example session"><div class="titlepage"><div><div><h3 class="title"><a name="id451145"></a>Example session</h3></div></div></div><p>
+ </p></div></div></div><div class="section" title="Example session"><div class="titlepage"><div><div><h3 class="title"><a name="id354480"></a>Example session</h3></div></div></div><p>
In this example we want to set the global logging to
write to the file <code class="filename">/var/log/my_bind10.log</code>,
@@ -1436,7 +1522,7 @@ Logging/loggers[0]/output_options[0]/maxver 8 integer (modified)
And every module will now be using the values from the
logger named <span class="quote">“<span class="quote">*</span>”</span>.
- </p></div></div><div class="section" title="Logging Message Format"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id451402"></a>Logging Message Format</h2></div></div></div><p>
+ </p></div></div><div class="section" title="Logging Message Format"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id354736"></a>Logging Message Format</h2></div></div></div><p>
Each message written by BIND 10 to the configured logging
destinations comprises a number of components that identify
the origin of the message and, if the message indicates
diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml
index c4f0268..4fb781d 100644
--- a/doc/guide/bind10-guide.xml
+++ b/doc/guide/bind10-guide.xml
@@ -1817,7 +1817,8 @@ then change those defaults with config set Resolver/forward_addresses[0]/address
clients. Even though principles of both DHCPv4 and DHCPv6 are
somewhat similar, these are two radically different
protocols. BIND10 offers server implementations for both DHCPv4
- and DHCPv6.</para>
+ and DHCPv6. This chapter is about DHCP for IPv4. For description of
+ DHCPv6 server, see <xref linkend="dhcp6"/>.</para>
<note>
<para>
@@ -1832,9 +1833,9 @@ then change those defaults with config set Resolver/forward_addresses[0]/address
</para>
</note>
- <section>
- <title>Server Usage</title>
- <para>BIND10 provides experimental DHCPv4 server component since
+ <section id="dhcp4-usage">
+ <title>DHCPv4 Server Usage</title>
+ <para>BIND10 provides DHCPv4 server component since
December 2011. It is currently described as skeleton server and
can be described as an early prototype that is not yet fully
functional. It is mature enough to conduct first tests in lab
@@ -1873,7 +1874,7 @@ then change those defaults with config set Resolver/forward_addresses[0]/address
</section>
<section id="dhcp4-config">
- <title>Server Configuration</title>
+ <title>DHCPv4 Server Configuration</title>
<para>
DHCPv4 server does not have lease database implemented yet
or any support for configuration, so every time the same set
@@ -1885,13 +1886,13 @@ then change those defaults with config set Resolver/forward_addresses[0]/address
configuration is to tweak its source code. To do so, please edit
src/bin/dhcp4/dhcp4_srv.cc file and modify following parameters:
<screen>
-const std::string HARDCODED_LEASE = "10.3.2.222"; // assigned lease
+const std::string HARDCODED_LEASE = "192.0.2.222"; // assigned lease
const std::string HARDCODED_NETMASK = "255.255.255.0";
const uint32_t HARDCODED_LEASE_TIME = 60; // in seconds
-const std::string HARDCODED_GATEWAY = "10.3.2.2";
-const std::string HARDCODED_DNS_SERVER = "8.8.8.8";
-const std::string HARDCODED_DOMAIN_NAME = "isc.example.org";
-const std::string HARDCODED_SERVER_ID = "10.3.1.1";</screen>
+const std::string HARDCODED_GATEWAY = "192.0.2.1";
+const std::string HARDCODED_DNS_SERVER = "192.0.2.2";
+const std::string HARDCODED_DOMAIN_NAME = "isc.example.com";
+const std::string HARDCODED_SERVER_ID = "192.0.2.1";</screen>
Lease database and configuration support is planned for 2012.
</para>
@@ -1906,23 +1907,25 @@ const std::string HARDCODED_SERVER_ID = "10.3.1.1";</screen>
</para>
<itemizedlist>
<listitem>
- <simpara>During initial IPv4 node configuration, where server has to
- send packet to a node that does not have IPv4 address
- assigned yet, server requires certain tricks (or hacks) to
- transmit such packets. This is not implemented yet, therefore
- DHCPv4 server supports relayed traffic only.</simpara>
+ <simpara>During initial IPv4 node configuration, where
+ server has to send packet to a node that does not have
+ IPv4 address assigned yet, server requires certain tricks
+ (or hacks) to transmit such packets. This is not
+ implemented yet, therefore DHCPv4 server supports relayed
+ traffic only.</simpara>
</listitem>
<listitem>
- <simpara>It provides a single, fixed, hardcoded lease to
- any client that asks. There is no lease manager
- implemented. If two clients request addresses, they will
- both get the same fixed address.</simpara>
+ <simpara><command>b10-dhcp4</command> provides a single,
+ fixed, hardcoded lease to any client that asks. There is
+ no lease manager implemented. If two clients request
+ addresses, they will both get the same fixed
+ address.</simpara>
</listitem>
<listitem>
- <simpara>Server does not support any configuration
- mechanisms yet. The whole configuration is currently
- hardcoded. The only way to tweak configuration is to
- directly modify source code. See see <xref
+ <simpara><command>b10-dhcp4</command> does not support any
+ configuration mechanisms yet. The whole configuration is
+ currently hardcoded. The only way to tweak configuration
+ is to directly modify source code. See see <xref
linkend="dhcp4-config"/> for details.</simpara>
</listitem>
<listitem>
@@ -1932,8 +1935,9 @@ const std::string HARDCODED_SERVER_ID = "10.3.1.1";</screen>
coded in reception routines yet, so if you are running
this code on a machine that has many interfaces and
<command>b10-dhcp4</command> happens to listen on wrong
- interface, the easiest way to is to down other
- interfaces. This limitation will be fixed shortly.</simpara>
+ interface, the easiest way to work around this problem is
+ to down other interfaces. This limitation will be fixed
+ shortly.</simpara>
</listitem>
<listitem>
<simpara>PRL (Parameter Request List) is currently ignored
@@ -1943,7 +1947,7 @@ const std::string HARDCODED_SERVER_ID = "10.3.1.1";</screen>
<listitem>
<simpara><command>b10-dhcp4</command> does not support
BOOTP. That is a design choice. This limitation is
- permanent. If have legacy nodes that can't use DHCP and
+ permanent. If you have legacy nodes that can't use DHCP and
require BOOTP support, please use latest version of ISC DHCP
<ulink url="http://www.isc.org/software/dhcp"/>.</simpara>
</listitem>
@@ -1951,24 +1955,162 @@ const std::string HARDCODED_SERVER_ID = "10.3.1.1";</screen>
<simpara>Interface detection is currently working on Linux
only. See <xref linkend="iface-detect"/> for details.</simpara>
</listitem>
+ <listitem>
+ <simpara>Address renewal (RENEW), rebinding (REBIND),
+ confirmation (CONFIRM), duplication report (DECLINE) and
+ release (RELEASE) are not supported yet.</simpara>
+ </listitem>
+ <listitem>
+ <simpara>DNS Update is not supported yet.</simpara>
+ </listitem>
</itemizedlist>
</section>
</chapter>
- <chapter id="dhcp6-srv">
+ <chapter id="dhcp6">
<title>DHCPv6 Server</title>
+ <para>Dynamic Host Configuration Protocol for IPv6 (DHCPv6) is
+ specified in RFC3315. BIND10 provides DHCPv6 server implementation
+ that is described in this chapter. For DHCPv4 server
+ implementation, see <xref linkend="dhcp4"/>.
+ </para>
+
+ <note>
+ <para>
+ As of December 2011, both DHCPv4 and DHCPv6 components are
+ skeleton servers. That means that while they are capable of
+ performing DHCP configuration, they are not fully functional
+ yet. In particular, both do not have functional lease
+ databases. This means that they will assign the same, fixed,
+ hardcoded addresses to any client that will ask. See <xref
+ linkend="dhcp4-limit"/> and <xref linkend="dhcp6-limit"/> for
+ detailed description.
+ </para>
+ </note>
+
+ <section id="dhcp6-usage">
+ <title>DHCPv6 Server Usage</title>
+ <para>
+ BIND10 provides DHCPv6 server component since September
+ 2011. It is currently described as skeleton server and can be
+ described as an early prototype that is not yet fully
+ functional. It is mature enough to conduct first tests in lab
+ environment, but it has significant limitations. See <xref
+ linkend="dhcp6-limit"/> for details.
+ </para>
+
+ <para>
+ DHCPv6 server is implemented as <command>b10-dhcp6</command>
+ daemon. As it is configurable yet, it is fully autonomous,
+ i.e. it does not interact with <command>b10-cfgmgr</command>.
+ To start DHCPv6 server, simply input:
+
+ <screen>
+#<userinput>cd src/bin/dhcp6</userinput>
+#<userinput>./b10-dhcp6</userinput>
+</screen>
+
+ Depending on your installation, <command>b10-dhcp6</command>
+ binary may reside in src/bin/dhcp6 in your source code
+ directory, in /usr/local/bin/b10-dhcp6 or other directory
+ you specified during compilation.
+
+ Afre start, server will detect available network interfaces
+ and will attempt to open UDP sockets on all interfaces that
+ are up, running, are not loopback and have IPv4 address
+ assigned.
+
+ Server will then listen to incoming traffic. Currently
+ supported client messages are SOLICIT and REQUEST. Server
+ will respond to them with ADVERTISE and REPLY, respectively.
+
+ As DHCPv6 server opens privileged ports, it requires root
+ access. Make sure you run this daemon as root.
+ </para>
+ </section>
+
+ <section id="dhcp6-config">
+ <title>DHCPv6 Server Configuration</title>
+ <para>
+ DHCPv4 server does not have lease database implemented yet
+ or any support for configuration, so every time the same set
+ of configuration options (including the same fixed address)
+ will be assigned every time.
+ </para>
+ <para>
+ At this stage of development, the only way to alter server
+ configuration is to tweak its source code. To do so, please edit
+ src/bin/dhcp6/dhcp6_srv.cc file and modify following parameters:
+ <screen>
+const std::string HARDCODED_LEASE = "2001:db8:1::1234:abcd";
+const uint32_t HARDCODED_T1 = 1500; // in seconds
+const uint32_t HARDCODED_T2 = 2600; // in seconds
+const uint32_t HARDCODED_PREFERRED_LIFETIME = 3600; // in seconds
+const uint32_t HARDCODED_VALID_LIFETIME = 7200; // in seconds
+const std::string HARDCODED_DNS_SERVER = "2001:db8:1::1";</screen>
+
+ Lease database and configuration support is planned for 2012.
+ </para>
+
+ </section>
+
<section id="dhcp6-limit">
<title>DHCPv6 Server Limitations</title>
<para>
- Relayed traffic is not supported.
+ <itemizedlist>
+ <listitem>
+ <simpara>Relayed traffic is not supported.</simpara>
+ </listitem>
+ <listitem>
+ <simpara><command>b10-dhcp6</command> provides a single,
+ fixed, hardcoded lease to any client that asks. There is no
+ lease manager implemented. If two clients request addresses,
+ they will both get the same fixed address.</simpara>
+ </listitem>
+ <listitem>
+ <simpara><command>b10-dhcp6</command> does not support any
+ configuration mechanisms yet. The whole configuration is
+ currently hardcoded. The only way to tweak configuration
+ is to directly modify source code. See see <xref
+ linkend="dhcp6-config"/> for details.</simpara>
+ </listitem>
+ <listitem>
+ <simpara>Upon start, server will open sockets on all
+ interfaces that are not loopback, are up, running and are
+ multicast capable and have IPv6 address. Support for
+ multiple interfaces is not coded in reception routines yet,
+ so if you are running this code on a machine that has many
+ interfaces and <command>b10-dhcp6</command> happens to
+ listen on wrong interface, the easiest way to work around
+ this problem is to down other interfaces. This limitation
+ will be fixed shortly.</simpara>
+ </listitem>
+ <listitem>
+ <simpara>Temporary addresses are not supported yet.</simpara>
+ </listitem>
+ <listitem>
+ <simpara>Prefix delegation is not supported yet.</simpara>
+ </listitem>
+ <listitem>
+ <simpara>Address renewal (RENEW), rebinding (REBIND),
+ confirmation (CONFIRM), duplication report (DECLINE) and
+ release (RELEASE) are not supported yet.</simpara>
+ </listitem>
+ <listitem>
+ <simpara>DNS Update is not supported yet.</simpara>
+ </listitem>
+ <listitem>
+ <simpara>Interface detection is currently working on Linux
+ only. See <xref linkend="iface-detect"/> for details.</simpara>
+ </listitem>
+ </itemizedlist>
</para>
</section>
-
</chapter>
- <chapter id="libdhcp++">
+ <chapter id="libdhcp">
<title>libdhcp++ library</title>
<para>libdhcp++ is a common library written in C++ that is
handles many DHCP-related tasks, like DHCPv4 and DHCPv6 packets
@@ -2008,6 +2150,11 @@ eth0 fe80::21e:8cff:fe9b:7349
</para>
</section>
+ <section id="packet-handling">
+ <title>DHCPv4/DHCPv6 packet handling</title>
+ <para>TODO: Describe packet handling here, with pointers to wiki</para>
+ </section>
+
</chapter>
<chapter id="statistics">
More information about the bind10-changes
mailing list