skeleton server. That means that while it is capable of
performing DHCP configuration, it is not fully functional.
In particular, it does not have a functional lease
- databases. This means that they will assign the same, fixed,
+ database. This means that they will assign the same, fixed,
hardcoded addresses to any client that will ask. See <xref
linkend="dhcp4-limit"/> for a
detailed description.
> <userinput>config commit</userinput></screen></para>
<para>
- To shutdown running <command>b10-dhcp4</command>, please use the
+ To stop running <command>b10-dhcp4</command>, please use the
following command:
- <screen>> <userinput>Dhcp4 shutdown</userinput></screen>
- or
<screen>> <userinput>config remove Boss/components b10-dhcp4</userinput>
> <userinput>config commit</userinput></screen></para>
<simpara><command>b10-dhcp4</command> does not support
BOOTP. That is a design choice. This limitation is
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>
+ require BOOTP support, please use the latest version of ISC DHCP
+ via <ulink url="http://www.isc.org/software/dhcp"/>.</simpara>
</listitem>
<listitem>
<simpara>Interface detection is currently working on Linux
<section id="dhcp6-install">
<title>DHCPv6 Server Build and Installation</title>
<para>
- DHCPv6 is part of the BIND suite of programs and is built as part of
+ DHCPv6 is part of the BIND 10 suite of programs and is built as part of
the build of BIND 10. With the use of MySQL, some additional
installation steps are needed:
</para>
i.e.
<screen><userinput>./configure [other-options] --with-dhcp-mysql</userinput></screen>
...if MySQL was installed in the default location, or:
- <screen><userinput>./configure [other-options] --with-dhcp-mysql=<path-to-mysql_config></userinput></screen>
+ <screen><userinput>./configure [other-options] --with-dhcp-mysql=<replaceable><path-to-mysql_config></replaceable></userinput></screen>
...if not.
</para>
</section>
<para>
3. Create the database tables:
<screen>mysql> <userinput>CONNECT kea;</userinput>
-mysql> <userinput>SOURCE <path-to-bind10>/share/bind10-devel/dhcpdb_create.mysql</userinput></screen>
+mysql> <userinput>SOURCE <replaceable><path-to-bind10></replaceable>/share/bind10-devel/dhcpdb_create.mysql</userinput></screen>
</para>
<para>
4. Create the user under which BIND 10 will access the database and grant it access to the database tables:
</para>
<para>
- To shutdown running <command>b10-dhcp6</command>, use use the
+ To stop running <command>b10-dhcp6</command>, use the
following command:
- <screen>> <userinput>Dhcp6 shutdown</userinput></screen>
- or
<screen>> <userinput>config remove Boss/components b10-dhcp6</userinput>
> <userinput>config commit</userinput></screen>
</para>
<para>
While this library is currently used by
<command>b10-dhcp4</command> and <command>b10-dhcp6</command>
- only, it is designed to be portable, universal library, useful for
+ only, it is designed to be a portable, universal library, useful for
any kind of DHCP-related software.
</para>
+<!-- TODO: point to doxygen docs -->
+
<section id="iface-detect">
<title>Interface detection</title>
<para>Both the DHCPv4 and DHCPv6 components share network
in running DHCP components on systems other than Linux.</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>