Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
Adam Osuchowski
Kea
Commits
1d9abefe
Commit
1d9abefe
authored
Mar 27, 2014
by
Marcin Siodelski
Browse files
[3281] Corrected bind10-guide DHCP server limitation sections.
parent
0a5a96b3
Changes
1
Hide whitespace changes
Inline
Side-by-side
doc/guide/bind10-guide.xml
View file @
1d9abefe
...
...
@@ -3848,7 +3848,7 @@ Dhcp4/dhcp-ddns/qualifying-suffix "example.com" string
</para>
</section>
<section>
<section
id=
"ipv4-subnet-id"
>
<title>
IPv4 Subnet Identifier
</title>
<para>
Subnet identifier is a unique number associated with a particular subnet.
...
...
@@ -5047,19 +5047,11 @@ Dhcp4/dhcp-ddns/qualifying-suffix "example.com" string
yet
</quote>
, rather than actual limitations.
</para>
<itemizedlist>
<listitem>
<!-- see tickets #3234, #3281 -->
<para>
On-line configuration has some limitations. Adding new subnets or
modifying existing ones work, as is removing the last subnet from
the list. However, removing non-last (e.g. removing subnet 1,2 or 3 if
there are 4 subnets configured) will cause issues. The problem is
caused by simplistic subnet-id assignment. The subnets are always
numbered, starting from 1. That subnet-id is then used in leases
that are stored in the lease database. Removing non-last subnet will
cause the configuration information to mismatch data in the lease
database. It is possible to manually update subnet-id fields in
MySQL database, but it is awkward and error prone process. A better
reconfiguration support is planned.
</para>
<simpara>
Removal of a subnet during server reconfiguration may cause renumbering
of auto-generated subnet identifiers, as described in section
<xref
linkend=
"ipv4-subnet-id"
/>
.
</simpara>
</listitem>
<listitem>
<para>
...
...
@@ -5338,7 +5330,7 @@ Dhcp6/dhcp-ddns/qualifying-suffix "example.com" string
</para>
</section>
<section>
<section
id=
"ipv6-subnet-id"
>
<title>
IPv6 Subnet Identifier
</title>
<para>
Subnet identifier is a unique number associated with a particular subnet.
...
...
@@ -6513,19 +6505,11 @@ Dhcp6/dhcp-ddns/qualifying-suffix "example.com" string
<itemizedlist>
<listitem>
<!-- see tickets #3234, #3281 -->
<para>
On-line configuration has some limitations. Adding new subnets or
modifying existing ones work, as is removing the last subnet from
the list. However, removing non-last (e.g. removing subnet 1,2 or 3 if
there are 4 subnets configured) will cause issues. The problem is
caused by simplistic subnet-id assignment. The subnets are always
numbered, starting from 1. That subnet-id is then used in leases
that are stored in the lease database. Removing non-last subnet will
cause the configuration information to mismatch data in the lease
database. It is possible to manually update subnet-id fields in
MySQL database, but it is awkward and error prone process. A better
reconfiguration support is planned.
</para>
<simpara>
Removal of a subnet during server reconfiguration may cause renumbering
of auto-generated subnet identifiers, as described in section
<xref
linkend=
"ipv6-subnet-id"
/>
.
</simpara>
</listitem>
<listitem>
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment