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
Sebastian Schrader
Kea
Commits
e98ccfe6
Commit
e98ccfe6
authored
Oct 11, 2013
by
Tomek Mrugalski
🛰
Browse files
[3191] User's Guide updated
parent
f296e302
Changes
1
Hide whitespace changes
Inline
Side-by-side
doc/guide/bind10-guide.xml
View file @
e98ccfe6
...
...
@@ -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>
>
<userinput>
config add Dhcp4/next-server
</userinput>
>
<userinput>
config set Dhcp4/next-server "192.0.2.123"
</userinput>
>
<userinput>
config commit
</userinput>
<userinput></userinput>
>
<userinput>
config add Dhcp4/subnet[0]/next-server
</userinput>
>
<userinput>
config set Dhcp4/subnet[0]/next-server "192.0.2.234"
</userinput>
>
<userinput>
config commit
</userinput>
</screen>
</section>
<section
id=
"dhcp4-std"
>
<title>
Supported Standards
</title>
<para>
The following standards and draft standards are currently
...
...
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