ple of this is shown under the VENDOR ENCAPSULATED OPTIONS
head later on in this document.
-P\bPE\bER\bR-\b-C\bCL\bLA\bAS\bSS\bS A\bAD\bDD\bDR\bRE\bES\bSS\bS A\bAS\bSS\bSI\bIG\bGN\bNM\bME\bEN\bNT\bT L\bLI\bIM\bMI\bIT\bTS\bS
+P\bPE\bER\bR-\b-C\bCL\bLA\bAS\bSS\bS L\bLI\bIM\bMI\bIT\bTS\bS O\bON\bN D\bDY\bYN\bNA\bAM\bMI\bIC\bC A\bAD\bDD\bDR\bRE\bES\bSS\bS A\bAL\bLL\bLO\bOC\bCA\bAT\bTI\bIO\bON\bN
You may specify a limit to the number of clients in a
class that can be assigned leases. The effect of this
will be to make it difficult for a new client in a class
ple is given only because it is a fairly straightforward
one.
-R\bRE\bEF\bFE\bER\bRE\bEN\bNC\bCE\bE:\b: E\bEV\bVE\bEN\bNT\bTS\bS
- There are three kinds of events that can happen regarding
- a lease, and it is possible to declare statements that
- occur when any of these events happen. These events are
- the commit event, when the server has made a commitment of
- a certain lease to a client, the release event, when the
- client has released the server from its commitment, and
- the expiry event, when the commitment expires.
+D\bDY\bYN\bNA\bAM\bMI\bIC\bC D\bDN\bNS\bS U\bUP\bPD\bDA\bAT\bTE\bES\bS
+ The DHCP server has the ability to dynamically update the
+ Domain Name System. Within the configuration files, you
+ can define how you want the Domain Name System to be
+ updated. These updates are RFC 2136 compliant so any DNS
+ server supporting RFC 2136 should be able to accept
+ updates from the DHCP server. The DHCP server will only
+ perform DNS updates if it has been built with DNS updates
+ enabled as described in the README file that comes with
+ the DHCP distribution.
- Currently, only the commit event is fully supported. The
- commit event occurs just before the DHCP server sends a
- DHCPACK message to a DHCP client, or a BOOTREPLY message
- to a BOOTP client.
+ The Dynamic DNS update scheme implemented in this version
+ of the ISC DHCP server is an interim implementation, which
+ does not implement any of the standard update methods that
+ have been discussed in the working group, but rather
+ implements some very basic, yet useful, update capabili
+ ties.
- The release event is partially supported, but currently
- will not occur if the server is restarted after the lease
- is assigned. This will be fixed in the near future.
+ There are three parameters, which may vary according to
+ the scope, that control how DDNS updates will be done.
+ The first two are the _\bd_\bd_\bn_\bs_\b-_\bd_\bo_\bm_\ba_\bi_\bn_\bn_\ba_\bm_\be and _\bd_\bd_\bn_\bs_\b-_\br_\be_\bv_\b-_\bd_\bo_\bm_\ba_\bi_\bn_\b
+ _\bn_\ba_\bm_\be statements. The _\bd_\bd_\bn_\bs_\b-_\bd_\bo_\bm_\ba_\bi_\bn_\bn_\ba_\bm_\be parameter sets the
- The expiry event is not currently supported at all. This
- will also be fixed in the reasonably near future.
- To declare a set of statements to execute when an event
+
+ 10
+
+
+
+
+
+dhcpd.conf(5) dhcpd.conf(5)
+
+
+ domain name that will be appended to the client's hostname
+ to form a fully-qualified domain-name (FQDN). For exam
+ ple, if the client's hostname is "hutson" and the _\bd_\bd_\bn_\bs_\b-
+ _\bd_\bo_\bm_\ba_\bi_\bn_\bn_\ba_\bm_\be is set to "sneedville.edu", then the client's
+ FQDN will be "hutson.sneedville.edu".
+
+ The _\bd_\bd_\bn_\bs_\b-_\br_\be_\bv_\b-_\bd_\bo_\bm_\ba_\bi_\bn_\bn_\ba_\bm_\be parameter sets the domain name
+ that will be appended to the client's reversed IP address
+ to produce a name for use in the client's PTR record.
+ Normally, you would set this to "in-addr.arpa", but this
+ is not required.
+
+ A third parameter, _\bd_\bd_\bn_\bs_\b-_\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be can be used to specify
+ the hostname that will be used as the client's hostname.
+ If no ddns-hostname is specified in scope, then the server
+ will use a host-name option sent by the client. If the
+ client did not send a host-name option, then if there is a
+ host declaration that applies to the client, the name from
+ that declaration will be used. If none of these applies,
+ the server will not have a hostname for the client, and
+ will not be able to do a DDNS update.
+
+H\bHO\bOW\bW D\bDN\bNS\bS U\bUP\bPD\bDA\bAT\bTE\bES\bS W\bWO\bOR\bRK\bK
+ The client's FQDN, derived as we have described, is used
+ as the name on which an "A" record will be stored. The A
+ record will contain the IP address that the client was
+ assigned in its lease. If there is already an A record
+ with the same name in the DNS server, no update of either
+ the A or PTR records will occur - this prevents a client
+ from claiming that its hostname is the name of some net
+ work server. For example, if you have a fileserver
+ called "fs.sneedville.edu", and the client claims its
+ hostname is "fs", no DNS update will be done for that
+ client, and an error message will be logged.
+
+ If the A record update succeeds, a PTR record update for
+ the assigned IP address will be done, pointing to the A
+ record. This update is unconditional - it will be done
+ even if another PTR record of the same name exists.
+ Since the IP address has been assigned to the DHCP server,
+ this should be safe.
+
+ Please note that the current implementation assumes
+ clients only have a single network interface. A client
+ with two network interfaces will see unpredictable
+ behaviour. This is considered a bug, and will be fixed
+ in a later release. It may be helpful to enable the _\bo_\bn_\be_\b-
+ _\bl_\be_\ba_\bs_\be_\b-_\bp_\be_\br_\b-_\bc_\bl_\bi_\be_\bn_\bt parameter so that roaming clients do not
+ trigger this same behavior.
+
+ The DHCP protocol normally involves a four-packet exchange
+ - first the client sends a DHCPDISCOVER message, then the
+ server sends a DHCPOFFER, then the client sends a DHCPRE
+ QUEST, then the server sends a DHCPACK. In the current
+
+
+
+ 11
+
- 10
+
+dhcpd.conf(5) dhcpd.conf(5)
+
+
+ version of the server, the server will do a DNS update
+ after it has received the DHCPREQUEST, and before it has
+ sent the DHCPOFFER. It only sends the DNS update if it
+ has not sent one for the client's address before, in order
+ to minimize the impact on the DHCP server.
+
+ When the client's lease expires, the DHCP server (if it is
+ operating at the time, or when next it operates) will
+ remove the client's A and PTR records from the DNS
+ database. If the client releases its lease by sending a
+ DHCPRELEASE message, the server will likewise remove the A
+ and PTR records.
+
+D\bDY\bYN\bNA\bAM\bMI\bIC\bC D\bDN\bNS\bS U\bUP\bPD\bDA\bAT\bTE\bE S\bSE\bEC\bCU\bUR\bRI\bIT\bTY\bY
+ Support for TSIG and DNSSEC is not yet available. When
+ you set your DNS server up to allow updates from the DHCP
+ server, you may be exposing it to unauthorized updates.
+ To avoid this, the best you can do right now is to use IP
+ address-based packet filtering to prevent unauthorized
+ hosts from submitting update requests.
+
+ The DNS server must be configured to allow updates for any
+ zone that the DHCP server will be updating. For example,
+ let us say that clients in the sneedville.edu domain will
+ be assigned addresses on the 10.10.17.0/24 subnet. In
+ that case, assuming you are using ISC BIND 8.2.1 or later,
+ you would need to have the following declarations in your
+ /etc/named.conf file:
+
+ zone "sneedville.edu" {
+ type master;
+ file "sneedville.edu.db";
+ allow-update { localhost; };
+ };
+
+ zone "17.10.10.in-addr.arpa" {
+ type master;
+ file "10.10.17.db";
+ allow-update { localhost; };
+ };
+
+ This assumes that your DHCP server and your name server
+ will be running on the same computer - the "localhost"
+ name is taken in the DNS server as an alias for all of
+ that host's IP addresses, and updates from any of those
+ addresses will be accepted.
+
+ You may wish to enable logging of DNS transactions on your
+ DNS server. To do so, you might write a logging statement
+ like the following:
+
+ logging {
+ channel update_debug {
+ file "/var/log/update-debug.log";
+
+
+
+ 12
dhcpd.conf(5) dhcpd.conf(5)
- happens, you must use the o\bon\bn statement, followed by the
- name of the event, followed by a series of statements to
- execute when the event happens, enclosed in braces. For
- example:
-
- on commit {
- if dns-update ("a",
- concat (option host-name, ".ssd.example.net"),
- binary-to-ascii (10, 8, ".", leased-address),
- lease-time) {
- if dns-update ("ptr", concat(binary-to-ascii(10, 8, ".",
- reverse(1, leased-address)),
- ".in-addr.arpa"),
- concat (option host-name,
- ".ssd.example.net"),
- lease-time) {
- }
- }
- }
+ severity debug 3;
+ print-category yes;
+ print-severity yes;
+ print-time yes;
+ };
+ channel security_info {
+ file "/var/log/named-auth.info";
+ severity info;
+ print-category yes;
+ print-severity yes;
+ print-time yes;
+ };
+
+ category update { update_debug; };
+ category security { security_info; };
+ };
+
+ You must create the /var/log/named-auth.info and
+ /var/log/update-debug.log files before starting the name
+ server. For more information on configuring ISC BIND,
+ consult the documentation that accompanies it.
+
+R\bRE\bEF\bFE\bER\bRE\bEN\bNC\bCE\bE:\b: E\bEV\bVE\bEN\bNT\bTS\bS
+ There are three kinds of events that can happen regarding
+ a lease, and it is possible to declare statements that
+ occur when any of these events happen. These events are
+ the commit event, when the server has made a commitment of
+ a certain lease to a client, the release event, when the
+ client has released the server from its commitment, and
+ the expiry event, when the commitment expires.
+
+ To declare a set of statements to execute when an event
+ happens, you must use the o\bon\bn statement, followed by the
+ name of the event, followed by a series of statements to
+ execute when the event happens, enclosed in braces.
+ Events are used to implement dynamic DNS updates, so you
+ should not define your own event handlers if you are using
+ the built-in dynamic DNS update mechanism.
R\bRE\bEF\bFE\bER\bRE\bEN\bNC\bCE\bE:\b: D\bDE\bEC\bCL\bLA\bAR\bRA\bAT\bTI\bIO\bON\bNS\bS
T\bTh\bhe\be _\bs_\bh_\ba_\br_\be_\bd_\b-_\bn_\be_\bt_\bw_\bo_\br_\bk s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
[ _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn_\bs ]
}\b}
- The _\bs_\bh_\ba_\br_\be_\bd_\b-_\bn_\be_\bt_\bw_\bo_\br_\bk statement is used to inform the DHCP
+ The _\bs_\bh_\ba_\br_\be_\bd_\b-_\bn_\be_\bt_\bw_\bo_\br_\bk statement is used to inform the DHCP
server that some IP subnets actually share the same physi
- cal network. Any subnets in a shared network should be
- declared within a _\bs_\bh_\ba_\br_\be_\bd_\b-_\bn_\be_\bt_\bw_\bo_\br_\bk statement. Parameters
- specified in the _\bs_\bh_\ba_\br_\be_\bd_\b-_\bn_\be_\bt_\bw_\bo_\br_\bk statement will be used
- when booting clients on those subnets unless parameters
- provided at the subnet or host level override them. If
- any subnet in a shared network has addresses available for
- dynamic allocation, those addresses are collected into a
- common pool for that shared network and assigned to
- clients as needed. There is no way to distinguish on
- which subnet of a shared network a client should boot.
+ cal network. Any subnets in a shared network should be
+ declared within a _\bs_\bh_\ba_\br_\be_\bd_\b-_\bn_\be_\bt_\bw_\bo_\br_\bk statement. Parameters
+ specified in the _\bs_\bh_\ba_\br_\be_\bd_\b-_\bn_\be_\bt_\bw_\bo_\br_\bk statement will be used
+ when booting clients on those subnets unless parameters
+ provided at the subnet or host level override them. If
- _\bN_\ba_\bm_\be should be the name of the shared network. This name
- is used when printing debugging messages, so it should be
- descriptive for the shared network. The name may have
- the syntax of a valid domain name (although it will never
- be used as such), or it may be any arbitrary name,
- enclosed in quotes.
- T\bTh\bhe\be _\bs_\bu_\bb_\bn_\be_\bt s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
- s\bsu\bub\bbn\bne\bet\bt _\bs_\bu_\bb_\bn_\be_\bt_\b-_\bn_\bu_\bm_\bb_\be_\br n\bne\bet\btm\bma\bas\bsk\bk _\bn_\be_\bt_\bm_\ba_\bs_\bk {\b{
- [ _\bp_\ba_\br_\ba_\bm_\be_\bt_\be_\br_\bs ]
- [ _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn_\bs ]
- }\b}
+ 13
- 11
+dhcpd.conf(5) dhcpd.conf(5)
+ any subnet in a shared network has addresses available for
+ dynamic allocation, those addresses are collected into a
+ common pool for that shared network and assigned to
+ clients as needed. There is no way to distinguish on
+ which subnet of a shared network a client should boot.
-dhcpd.conf(5) dhcpd.conf(5)
+ _\bN_\ba_\bm_\be should be the name of the shared network. This name
+ is used when printing debugging messages, so it should be
+ descriptive for the shared network. The name may have
+ the syntax of a valid domain name (although it will never
+ be used as such), or it may be any arbitrary name,
+ enclosed in quotes.
+ T\bTh\bhe\be _\bs_\bu_\bb_\bn_\be_\bt s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
- The _\bs_\bu_\bb_\bn_\be_\bt statement is used to provide dhcpd with enough
- information to tell whether or not an IP address is on
- that subnet. It may also be used to provide subnet-spe
- cific parameters and to specify what addresses may be
- dynamically allocated to clients booting on that subnet.
- Such addresses are specified using the _\br_\ba_\bn_\bg_\be declaration.
+ s\bsu\bub\bbn\bne\bet\bt _\bs_\bu_\bb_\bn_\be_\bt_\b-_\bn_\bu_\bm_\bb_\be_\br n\bne\bet\btm\bma\bas\bsk\bk _\bn_\be_\bt_\bm_\ba_\bs_\bk {\b{
+ [ _\bp_\ba_\br_\ba_\bm_\be_\bt_\be_\br_\bs ]
+ [ _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn_\bs ]
+ }\b}
+
+ The _\bs_\bu_\bb_\bn_\be_\bt statement is used to provide dhcpd with enough
+ information to tell whether or not an IP address is on
+ that subnet. It may also be used to provide subnet-spe
+ cific parameters and to specify what addresses may be
+ dynamically allocated to clients booting on that subnet.
+ Such addresses are specified using the _\br_\ba_\bn_\bg_\be declaration.
- The _\bs_\bu_\bb_\bn_\be_\bt_\b-_\bn_\bu_\bm_\bb_\be_\br should be an IP address or domain name
- which resolves to the subnet number of the subnet being
+ The _\bs_\bu_\bb_\bn_\be_\bt_\b-_\bn_\bu_\bm_\bb_\be_\br should be an IP address or domain name
+ which resolves to the subnet number of the subnet being
described. The _\bn_\be_\bt_\bm_\ba_\bs_\bk should be an IP address or domain
name which resolves to the subnet mask of the subnet being
described. The subnet number, together with the netmask,
- are sufficient to determine whether any given IP address
+ are sufficient to determine whether any given IP address
is on the specified subnet.
- Although a netmask must be given with every subnet decla
+ Although a netmask must be given with every subnet decla
ration, it is recommended that if there is any variance in
- subnet masks at a site, a subnet-mask option statement be
- used in each subnet declaration to set the desired subnet
+ subnet masks at a site, a subnet-mask option statement be
+ used in each subnet declaration to set the desired subnet
mask, since any subnet-mask option statement will override
the subnet mask declared in the subnet statement.
r\bra\ban\bng\bge\be [ d\bdy\byn\bna\bam\bmi\bic\bc-\b-b\bbo\boo\bot\btp\bp ] _\bl_\bo_\bw_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [ _\bh_\bi_\bg_\bh_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs];\b;
For any subnet on which addresses will be assigned dynami
- cally, there must be at least one _\br_\ba_\bn_\bg_\be statement. The
- range statement gives the lowest and highest IP addresses
- in a range. All IP addresses in the range should be in
+ cally, there must be at least one _\br_\ba_\bn_\bg_\be statement. The
+ range statement gives the lowest and highest IP addresses
+ in a range. All IP addresses in the range should be in
the subnet in which the _\br_\ba_\bn_\bg_\be statement is declared. The
- _\bd_\by_\bn_\ba_\bm_\bi_\bc_\b-_\bb_\bo_\bo_\bt_\bp flag may be specified if addresses in the
- specified range may be dynamically assigned to BOOTP
- clients as well as DHCP clients. When specifying a sin
- gle address, _\bh_\bi_\bg_\bh_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs can be omitted.
+ _\bd_\by_\bn_\ba_\bm_\bi_\bc_\b-_\bb_\bo_\bo_\bt_\bp flag may be specified if addresses in the
+ specified range may be dynamically assigned to BOOTP
+ clients as well as DHCP clients. When specifying a
- T\bTh\bhe\be _\bh_\bo_\bs_\bt s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
- h\bho\bos\bst\bt _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be {
- [ _\bp_\ba_\br_\ba_\bm_\be_\bt_\be_\br_\bs ]
- [ _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn_\bs ]
- }\b}
- There must be at least one h\bho\bos\bst\bt statement for every BOOTP
- client that is to be served. h\bho\bos\bst\bt statements may also be
- specified for DHCP clients, although this is not required
- unless booting is only enabled for known hosts.
+ 14
- If it is desirable to be able to boot a DHCP or BOOTP
- client on more than one subnet with fixed addresses, more
- than one address may be specified in the _\bf_\bi_\bx_\be_\bd_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
- parameter, or more than one h\bho\bos\bst\bt statement may be speci
- fied.
- 12
+dhcpd.conf(5) dhcpd.conf(5)
+ single address, _\bh_\bi_\bg_\bh_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs can be omitted.
+ T\bTh\bhe\be _\bh_\bo_\bs_\bt s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
+ h\bho\bos\bst\bt _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be {
+ [ _\bp_\ba_\br_\ba_\bm_\be_\bt_\be_\br_\bs ]
+ [ _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn_\bs ]
+ }\b}
-dhcpd.conf(5) dhcpd.conf(5)
+ There must be at least one h\bho\bos\bst\bt statement for every BOOTP
+ client that is to be served. h\bho\bos\bst\bt statements may also be
+ specified for DHCP clients, although this is not required
+ unless booting is only enabled for known hosts.
+ If it is desirable to be able to boot a DHCP or BOOTP
+ client on more than one subnet with fixed addresses, more
+ than one address may be specified in the _\bf_\bi_\bx_\be_\bd_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ parameter, or more than one h\bho\bos\bst\bt statement may be speci
+ fied.
- If client-specific boot parameters must change based on
+ If client-specific boot parameters must change based on
the network to which the client is attached, then multiple
h\bho\bos\bst\bt statements should be used.
- If a client is to be booted using a fixed address if it's
+ If a client is to be booted using a fixed address if it's
possible, but should be allocated a dynamic address other
- wise, then a h\bho\bos\bst\bt statement must be specified without a
+ wise, then a h\bho\bos\bst\bt statement must be specified without a
f\bfi\bix\bxe\bed\bd-\b-a\bad\bdd\bdr\bre\bes\bss\bs clause. _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be should be a name identify
- ing the host. If a _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be option is not specified for
+ ing the host. If a _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be option is not specified for
the host, _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be is used.
- _\bH_\bo_\bs_\bt declarations are matched to actual DHCP or BOOTP
+ _\bH_\bo_\bs_\bt declarations are matched to actual DHCP or BOOTP
clients by matching the dhcp-client-identifier option
- specified in the _\bh_\bo_\bs_\bt declaration to the one supplied by
+ specified in the _\bh_\bo_\bs_\bt declaration to the one supplied by
the client, or, if the _\bh_\bo_\bs_\bt declaration or the client does
- not provide a dhcp-client-identifier option, by matching
+ not provide a dhcp-client-identifier option, by matching
the _\bh_\ba_\br_\bd_\bw_\ba_\br_\be parameter in the _\bh_\bo_\bs_\bt declaration to the net
- work hardware address supplied by the client. BOOTP
- clients do not normally provide a _\bd_\bh_\bc_\bp_\b-_\bc_\bl_\bi_\be_\bn_\bt_\b-_\bi_\bd_\be_\bn_\bt_\bi_\bf_\bi_\be_\br,
- so the hardware address must be used for all clients that
+ work hardware address supplied by the client. BOOTP
+ clients do not normally provide a _\bd_\bh_\bc_\bp_\b-_\bc_\bl_\bi_\be_\bn_\bt_\b-_\bi_\bd_\be_\bn_\bt_\bi_\bf_\bi_\be_\br,
+ so the hardware address must be used for all clients that
may boot using the BOOTP protocol.
T\bTh\bhe\be _\bg_\br_\bo_\bu_\bp s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
[ _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn_\bs ]
}\b}
- The group statement is used simply to apply one or more
+ The group statement is used simply to apply one or more
parameters to a group of declarations. It can be used to
- group hosts, shared networks, subnets, or even other
+ group hosts, shared networks, subnets, or even other
groups.
-R\bRE\bEF\bFE\bER\bRE\bEN\bNC\bCE\bE:\b: A\bAL\bLL\bLO\bOW\bW A\bAN\bND\bD D\bDE\bEN\bNY\bY
- The _\ba_\bl_\bl_\bo_\bw and _\bd_\be_\bn_\by statements can be used to control the
- response of the DHCP server to various sorts of requests.
- The allow and deny keywords actually have different mean
- ings depending on the context. In a pool context, these
- keywords can be used to set up access lists for address
- allocation pools. In other contexts, the keywords simply
- control general server behaviour with respect to clients
- based on scope. In a non-pool context, the _\bi_\bg_\bn_\bo_\br_\be key
- word can be used in place of the _\bd_\be_\bn_\by keyword to prevent
- logging of denied requests.
-A\bAL\bLL\bLO\bOW\bW D\bDE\bEN\bNY\bY A\bAN\bND\bD I\bIG\bGN\bNO\bOR\bRE\bE I\bIN\bN S\bSC\bCO\bOP\bPE\bE
- The following usages of allow and deny will work in any
- scope, although it is not recommended that they be used in
- pool declarations.
- T\bTh\bhe\be _\bu_\bn_\bk_\bn_\bo_\bw_\bn_\b-_\bc_\bl_\bi_\be_\bn_\bt_\bs k\bke\bey\byw\bwo\bor\brd\bd
+ 15
- 13
+dhcpd.conf(5) dhcpd.conf(5)
+R\bRE\bEF\bFE\bER\bRE\bEN\bNC\bCE\bE:\b: A\bAL\bLL\bLO\bOW\bW A\bAN\bND\bD D\bDE\bEN\bNY\bY
+ The _\ba_\bl_\bl_\bo_\bw and _\bd_\be_\bn_\by statements can be used to control the
+ response of the DHCP server to various sorts of requests.
+ The allow and deny keywords actually have different mean
+ ings depending on the context. In a pool context, these
+ keywords can be used to set up access lists for address
+ allocation pools. In other contexts, the keywords simply
+ control general server behaviour with respect to clients
+ based on scope. In a non-pool context, the _\bi_\bg_\bn_\bo_\br_\be key
+ word can be used in place of the _\bd_\be_\bn_\by keyword to prevent
+ logging of denied requests.
-dhcpd.conf(5) dhcpd.conf(5)
+A\bAL\bLL\bLO\bOW\bW D\bDE\bEN\bNY\bY A\bAN\bND\bD I\bIG\bGN\bNO\bOR\bRE\bE I\bIN\bN S\bSC\bCO\bOP\bPE\bE
+ The following usages of allow and deny will work in any
+ scope, although it is not recommended that they be used in
+ pool declarations.
+ T\bTh\bhe\be _\bu_\bn_\bk_\bn_\bo_\bw_\bn_\b-_\bc_\bl_\bi_\be_\bn_\bt_\bs k\bke\bey\byw\bwo\bor\brd\bd
a\bal\bll\blo\bow\bw u\bun\bnk\bkn\bno\bow\bwn\bn-\b-c\bcl\bli\bie\ben\bnt\bts\bs;\b;
d\bde\ben\bny\by u\bun\bnk\bkn\bno\bow\bwn\bn-\b-c\bcl\bli\bie\ben\bnt\bts\bs;\b;
i\big\bgn\bno\bor\bre\be u\bun\bnk\bkn\bno\bow\bwn\bn-\b-c\bcl\bli\bie\ben\bnt\bts\bs;\b;
- The u\bun\bnk\bkn\bno\bow\bwn\bn-\b-c\bcl\bli\bie\ben\bnt\bts\bs flag is used to tell dhcpd whether or
- not to dynamically assign addresses to unknown clients.
- Dynamic address assignment to unknown clients is a\bal\bll\blo\bow\bwed
+ The u\bun\bnk\bkn\bno\bow\bwn\bn-\b-c\bcl\bli\bie\ben\bnt\bts\bs flag is used to tell dhcpd whether or
+ not to dynamically assign addresses to unknown clients.
+ Dynamic address assignment to unknown clients is a\bal\bll\blo\bow\bwed
by default.
T\bTh\bhe\be _\bb_\bo_\bo_\bt_\bp k\bke\bey\byw\bwo\bor\brd\bd
d\bde\ben\bny\by b\bbo\boo\bot\btp\bp;\b;
i\big\bgn\bno\bor\bre\be b\bbo\boo\bot\btp\bp;\b;
- The b\bbo\boo\bot\btp\bp flag is used to tell dhcpd whether or not to
- respond to bootp queries. Bootp queries are a\bal\bll\blo\bow\bwed by
+ The b\bbo\boo\bot\btp\bp flag is used to tell dhcpd whether or not to
+ respond to bootp queries. Bootp queries are a\bal\bll\blo\bow\bwed by
default.
T\bTh\bhe\be _\bb_\bo_\bo_\bt_\bi_\bn_\bg k\bke\bey\byw\bwo\bor\brd\bd
d\bde\ben\bny\by b\bbo\boo\bot\bti\bin\bng\bg;\b;
i\big\bgn\bno\bor\bre\be b\bbo\boo\bot\bti\bin\bng\bg;\b;
- The b\bbo\boo\bot\bti\bin\bng\bg flag is used to tell dhcpd whether or not to
+ The b\bbo\boo\bot\bti\bin\bng\bg flag is used to tell dhcpd whether or not to
respond to queries from a particular client. This keyword
- only has meaning when it appears in a host declaration.
- By default, booting is a\bal\bll\blo\bow\bwed, but if it is disabled for
- a particular client, then that client will not be able to
+ only has meaning when it appears in a host declaration.
+ By default, booting is a\bal\bll\blo\bow\bwed, but if it is disabled for
+ a particular client, then that client will not be able to
get and address from the DHCP server. T\bTh\bhe\be _\bd_\bu_\bp_\bl_\bi_\bc_\ba_\bt_\be_\bs k\bke\bey\by\b
w\bwo\bor\brd\bd
a\bal\bll\blo\bow\bw d\bdu\bup\bpl\bli\bic\bca\bat\bte\bes\bs;\b;
- d\bde\ben\bny\by d\bdu\bup\bpl\bli\bic\bca\bat\bte\bes\bs;\b;
- Host declarations can match client messages based on the
- DHCP Client Identifer option or based on the client's net
- work hardware type and MAC address. If the MAC address
- is used, the host declaration will match any client with
- that MAC address - even clients with different client
- identifiers. This doesn't normally happen, but is possi
- ble when one computer has more than one operating system
- installed on it - for example, Microsoft Windows and
- NetBSD or Linux.
- The d\bdu\bup\bpl\bli\bic\bca\bat\bte\bes\bs flag tells the DHCP server that if a
- request is received from a client that matches the MAC
- address of a host declaration, any other leases matching
- that MAC address should be discarded by the server, even
- if the UID is not the same. This is a violation of the
- DHCP protocol, but can prevent clients whose client iden
- tifiers change regularly from holding many leases at the
- same time. By default, duplicates are a\bal\bll\blo\bow\bwed. T\bTh\bhe\be
+ 16
- 14
+dhcpd.conf(5) dhcpd.conf(5)
-dhcpd.conf(5) dhcpd.conf(5)
+ d\bde\ben\bny\by d\bdu\bup\bpl\bli\bic\bca\bat\bte\bes\bs;\b;
+ Host declarations can match client messages based on the
+ DHCP Client Identifer option or based on the client's net
+ work hardware type and MAC address. If the MAC address
+ is used, the host declaration will match any client with
+ that MAC address - even clients with different client
+ identifiers. This doesn't normally happen, but is possi
+ ble when one computer has more than one operating system
+ installed on it - for example, Microsoft Windows and
+ NetBSD or Linux.
+ The d\bdu\bup\bpl\bli\bic\bca\bat\bte\bes\bs flag tells the DHCP server that if a
+ request is received from a client that matches the MAC
+ address of a host declaration, any other leases matching
+ that MAC address should be discarded by the server, even
+ if the UID is not the same. This is a violation of the
+ DHCP protocol, but can prevent clients whose client iden
+ tifiers change regularly from holding many leases at the
+ same time. By default, duplicates are a\bal\bll\blo\bow\bwed. T\bTh\bhe\be
_\bd_\be_\bc_\bl_\bi_\bn_\be_\bs k\bke\bey\byw\bwo\bor\brd\bd
a\bal\bll\blo\bow\bw d\bde\bec\bcl\bli\bin\bne\bes\bs;\b;
d\bde\ben\bny\by d\bde\bec\bcl\bli\bin\bne\bes\bs;\b;
i\big\bgn\bno\bor\bre\be d\bde\bec\bcl\bli\bin\bne\bes\bs;\b;
- The DHCPDECLINE message is used by DHCP clients to indi
- cate that the lease the server has offered is not valid.
- When the server receives a DHCPDECLINE for a particular
- address, it normally abandons that address, assuming that
- some unauthorized system is using it. Unfortunately, a
+ The DHCPDECLINE message is used by DHCP clients to indi
+ cate that the lease the server has offered is not valid.
+ When the server receives a DHCPDECLINE for a particular
+ address, it normally abandons that address, assuming that
+ some unauthorized system is using it. Unfortunately, a
malicious or buggy client can, using DHCPDECLINE messages,
- completely exhaust the DHCP server's allocation pool.
+ completely exhaust the DHCP server's allocation pool.
The server will reclaim these leases, but while the client
- is running through the pool, it may cause serious thrash
- ing in the DNS, and it will also cause the DHCP server to
+ is running through the pool, it may cause serious thrash
+ ing in the DNS, and it will also cause the DHCP server to
forget old DHCP client address allocations.
- The d\bde\bec\bcl\bli\bin\bne\bes\bs flag tells the DHCP server whether or not to
- honor DHCPDECLINE messages. If it is set to d\bde\ben\bny\by or
- i\big\bgn\bno\bor\bre\be in a particular scope, the DHCP server will not
+ The d\bde\bec\bcl\bli\bin\bne\bes\bs flag tells the DHCP server whether or not to
+ honor DHCPDECLINE messages. If it is set to d\bde\ben\bny\by or
+ i\big\bgn\bno\bor\bre\be in a particular scope, the DHCP server will not
respond to DHCPDECLINE messages.
A\bAL\bLL\bLO\bOW\bW A\bAN\bND\bD D\bDE\bEN\bNY\bY W\bWI\bIT\bTH\bHI\bIN\bN P\bPO\bOO\bOL\bL D\bDE\bEC\bCL\bLA\bAR\bRA\bAT\bTI\bIO\bON\bNS\bS
The uses of the allow and deny keyword shown in the previ
- ous section work pretty much the same way whether the
- client is sending a DHCPDISCOVER or a DHCPREQUEST message
- - an address will be allocated to the client (either the
- old address it's requesting, or a new address) and then
+ ous section work pretty much the same way whether the
+ client is sending a DHCPDISCOVER or a DHCPREQUEST message
+ - an address will be allocated to the client (either the
+ old address it's requesting, or a new address) and then
that address will be tested to see if it's okay to let the
client have it. If the client requested it, and it's not
okay, the server will send a DHCPNAK message. Otherwise,
- the server will simply not respond to the client. If it
+ the server will simply not respond to the client. If it
is okay to give the address to the client, the server will
- send a DHCPACK message.
- The primary motivation behind pool declarations is to have
- address allocation pools whose allocation policies are
- different. A client may be denied access to one pool,
- but allowed access to another pool on the same network
- segment. In order for this to work, access control has
- to be done during address allocation, not after address
- allocation is done.
- When a DHCPREQUEST message is processed, address alloca
- tion simply consists of looking up the address the client
- is requesting and seeing if it's still available for the
- client. If it is, then the DHCP server checks both the
- address pool permit lists and the relevant in-scope allow
- and deny statements to see if it's okay to give the lease
- to the client. In the case of a DHCPDISCOVER message, the
- allocation process is done as described previously in the
- ADDRESS ALLOCATION section.
+ 17
- 15
+dhcpd.conf(5) dhcpd.conf(5)
+ send a DHCPACK message.
-dhcpd.conf(5) dhcpd.conf(5)
+ The primary motivation behind pool declarations is to have
+ address allocation pools whose allocation policies are
+ different. A client may be denied access to one pool,
+ but allowed access to another pool on the same network
+ segment. In order for this to work, access control has
+ to be done during address allocation, not after address
+ allocation is done.
+ When a DHCPREQUEST message is processed, address alloca
+ tion simply consists of looking up the address the client
+ is requesting and seeing if it's still available for the
+ client. If it is, then the DHCP server checks both the
+ address pool permit lists and the relevant in-scope allow
+ and deny statements to see if it's okay to give the lease
+ to the client. In the case of a DHCPDISCOVER message, the
+ allocation process is done as described previously in the
+ ADDRESS ALLOCATION section.
- When declaring permit lists for address allocation pools,
- the following syntaxes are recognized following the allow
+ When declaring permit lists for address allocation pools,
+ the following syntaxes are recognized following the allow
or deny keyword:
k\bkn\bno\bow\bwn\bn c\bcl\bli\bie\ben\bnt\bts\bs;\b;
- If specified, this statement either allows or prevents
- allocation from this pool to any client that has a host
- declaration (i.e., is known).
+ If specified, this statement either allows or prevents
+ allocation from this pool to any client that has a host
+ declaration (i.e., is known). A client is known if it has
+ a host declaration in _\ba_\bn_\by scope, not just the current
+ scope.
u\bun\bnk\bkn\bno\bow\bwn\bn c\bcl\bli\bie\ben\bnt\bts\bs;\b;
- If specified, this statement either allows or prevents
- allocation from this pool to any client that has no host
+ If specified, this statement either allows or prevents
+ allocation from this pool to any client that has no host
declaration (i.e., is not known).
m\bme\bem\bmb\bbe\ber\brs\bs o\bof\bf "\b"class"\b";\b;
- If specified, this statement either allows or prevents
- allocation from this pool to any client that is a member
+ If specified, this statement either allows or prevents
+ allocation from this pool to any client that is a member
of the named class.
d\bdy\byn\bna\bam\bmi\bic\bc b\bbo\boo\bot\btp\bp c\bcl\bli\bie\ben\bnt\bts\bs;\b;
- If specified, this statement either allows or prevents
+ If specified, this statement either allows or prevents
allocation from this pool to any bootp client.
a\bau\but\bth\bhe\ben\bnt\bti\bic\bca\bat\bte\bed\bd c\bcl\bli\bie\ben\bnt\bts\bs;\b;
- If specified, this statement either allows or prevents
- allocation from this pool to any client that has been
+ If specified, this statement either allows or prevents
+ allocation from this pool to any client that has been
authenticated using the DHCP authentication protocol.
- This is not yet supported.
- u\bun\bna\bau\but\bth\bhe\ben\bnt\bti\bic\bca\bat\bte\bed\bd c\bcl\bli\bie\ben\bnt\bts\bs;\b;
- If specified, this statement either allows or prevents
- allocation from this pool to any client that has not been
- authenticated using the DHCP authentication protocol.
- This is not yet supported.
- a\bal\bll\bl c\bcl\bli\bie\ben\bnt\bts\bs;\b;
+ 18
- If specified, this statement either allows or prevents
- allocation from this pool to all clients. This can be
- used when you want to write a pool declaration for some
- reason, but hold it in reserve, or when you want to renum
- ber your network quickly, and thus want the server to
- force all clients that have been allocated addresses from
- this pool to obtain new addresses immediately when they
- next renew.
-R\bRE\bEF\bFE\bER\bRE\bEN\bNC\bCE\bE:\b: P\bPA\bAR\bRA\bAM\bME\bET\bTE\bER\bRS\bS
- T\bTh\bhe\be _\bl_\be_\ba_\bs_\be_\b-_\bf_\bi_\bl_\be_\b-_\bn_\ba_\bm_\be s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
- 16
+dhcpd.conf(5) dhcpd.conf(5)
+ This is not yet supported.
+ u\bun\bna\bau\but\bth\bhe\ben\bnt\bti\bic\bca\bat\bte\bed\bd c\bcl\bli\bie\ben\bnt\bts\bs;\b;
+ If specified, this statement either allows or prevents
+ allocation from this pool to any client that has not been
+ authenticated using the DHCP authentication protocol.
+ This is not yet supported.
-dhcpd.conf(5) dhcpd.conf(5)
+ a\bal\bll\bl c\bcl\bli\bie\ben\bnt\bts\bs;\b;
+ If specified, this statement either allows or prevents
+ allocation from this pool to all clients. This can be
+ used when you want to write a pool declaration for some
+ reason, but hold it in reserve, or when you want to renum
+ ber your network quickly, and thus want the server to
+ force all clients that have been allocated addresses from
+ this pool to obtain new addresses immediately when they
+ next renew.
+
+R\bRE\bEF\bFE\bER\bRE\bEN\bNC\bCE\bE:\b: P\bPA\bAR\bRA\bAM\bME\bET\bTE\bER\bRS\bS
+ T\bTh\bhe\be _\bl_\be_\ba_\bs_\be_\b-_\bf_\bi_\bl_\be_\b-_\bn_\ba_\bm_\be s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
l\ble\bea\bas\bse\be-\b-f\bfi\bil\ble\be-\b-n\bna\bam\bme\be _\bn_\ba_\bm_\be;\b;
- _\bN_\ba_\bm_\be should be the name of the DHCP server's lease file.
+ _\bN_\ba_\bm_\be should be the name of the DHCP server's lease file.
By default, this is /var/db/dhcpd.leases. This statement
m\bmu\bus\bst\bt appear in the outer scope of the configuration file -
if it appears in some other scope, it will have no effect.
p\bpi\bid\bd-\b-f\bfi\bil\ble\be-\b-n\bna\bam\bme\be _\bn_\ba_\bm_\be;\b;
- _\bN_\ba_\bm_\be should be the name of the DHCP server's process ID
- file. This is the file in which the DHCP server's pro
- cess ID is stored when the server starts. By default,
- this is /var/run/dhcpd.pid. Like the lease-file-name
- statement, this statement must appear in the outer scope
+ _\bN_\ba_\bm_\be should be the name of the DHCP server's process ID
+ file. This is the file in which the DHCP server's pro
+ cess ID is stored when the server starts. By default,
+ this is /var/run/dhcpd.pid. Like the lease-file-name
+ statement, this statement must appear in the outer scope
of the configuration file.
T\bTh\bhe\be _\bd_\be_\bf_\ba_\bu_\bl_\bt_\b-_\bl_\be_\ba_\bs_\be_\b-_\bt_\bi_\bm_\be s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
m\bma\bax\bx-\b-l\ble\bea\bas\bse\be-\b-t\bti\bim\bme\be _\bt_\bi_\bm_\be;\b;
- _\bT_\bi_\bm_\be should be the maximum length in seconds that will be
- assigned to a lease. The only exception to this is that
- Dynamic BOOTP lease lengths, which are not specified by
+ _\bT_\bi_\bm_\be should be the maximum length in seconds that will be
+
+
+
+ 19
+
+
+
+
+
+dhcpd.conf(5) dhcpd.conf(5)
+
+
+ assigned to a lease. The only exception to this is that
+ Dynamic BOOTP lease lengths, which are not specified by
the client, are not limited by this maximum.
T\bTh\bhe\be _\bm_\bi_\bn_\b-_\bl_\be_\ba_\bs_\be_\b-_\bt_\bi_\bm_\be s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
m\bmi\bin\bn-\b-l\ble\bea\bas\bse\be-\b-t\bti\bim\bme\be _\bt_\bi_\bm_\be;\b;
- _\bT_\bi_\bm_\be should be the minimum length in seconds that will be
+ _\bT_\bi_\bm_\be should be the minimum length in seconds that will be
assigned to a lease.
T\bTh\bhe\be _\bm_\bi_\bn_\b-_\bs_\be_\bc_\bs s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
m\bmi\bin\bn-\b-s\bse\bec\bcs\bs _\bs_\be_\bc_\bo_\bn_\bd_\bs;\b;
- _\bS_\be_\bc_\bo_\bn_\bd_\bs should be the minimum number of seconds since a
+ _\bS_\be_\bc_\bo_\bn_\bd_\bs should be the minimum number of seconds since a
client began trying to acquire a new lease before the DHCP
server will respond to its request. The number of seconds
is based on what the client reports, and the maximum value
- that the client can report is 255 seconds. Generally,
- setting this to one will result in the DHCP server not
- responding to the client's first request, but always
+ that the client can report is 255 seconds. Generally,
+ setting this to one will result in the DHCP server not
+ responding to the client's first request, but always
responding to its second request.
+ This can be used to set up a secondary DHCP server which
+ never offers an address to a client until the primary
+ server has been given a chance to do so. If the primary
+ server is down, the client will bind to the secondary
+ server, but otherwise clients should always bind to the
+ primary. Note that this does not, by itself, permit a
+ primary server and a secondary server to share a pool of
+ dynamically-allocatable addresses.
+ T\bTh\bhe\be _\bh_\ba_\br_\bd_\bw_\ba_\br_\be s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
- 17
+ h\bha\bar\brd\bdw\bwa\bar\bre\be _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\bt_\by_\bp_\be _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs;\b;
+
+ In order for a BOOTP client to be recognized, its network
+ hardware address must be declared using a _\bh_\ba_\br_\bd_\bw_\ba_\br_\be clause
+ in the _\bh_\bo_\bs_\bt statement. _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\bt_\by_\bp_\be must be the name of
+ a physical hardware interface type. Currently, only the
+ e\bet\bth\bhe\ber\brn\bne\bet\bt and t\bto\bok\bke\ben\bn-\b-r\bri\bin\bng\bg types are recognized, although
+ support for a f\bfd\bdd\bdi\bi hardware type (and others) would also
+ be desirable. The _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs should be a set of
+ hexadecimal octets (numbers from 0 through ff) seperated
+ by colons. The _\bh_\ba_\br_\bd_\bw_\ba_\br_\be statement may also be used for
+ DHCP clients.
+ T\bTh\bhe\be _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
+ f\bfi\bil\ble\ben\bna\bam\bme\be "\b"_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be"\b";\b;
+ The _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be statement can be used to specify the name of
+ the initial boot file which is to be loaded by a client.
-dhcpd.conf(5) dhcpd.conf(5)
+ 20
- This can be used to set up a secondary DHCP server which
- never offers an address to a client until the primary
- server has been given a chance to do so. If the primary
- server is down, the client will bind to the secondary
- server, but otherwise clients should always bind to the
- primary. Note that this does not, by itself, permit a
- primary server and a secondary server to share a pool of
- dynamically-allocatable addresses.
- T\bTh\bhe\be _\bh_\ba_\br_\bd_\bw_\ba_\br_\be s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
- h\bha\bar\brd\bdw\bwa\bar\bre\be _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\bt_\by_\bp_\be _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs;\b;
- In order for a BOOTP client to be recognized, its network
- hardware address must be declared using a _\bh_\ba_\br_\bd_\bw_\ba_\br_\be clause
- in the _\bh_\bo_\bs_\bt statement. _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\bt_\by_\bp_\be must be the name of
- a physical hardware interface type. Currently, only the
- e\bet\bth\bhe\ber\brn\bne\bet\bt and t\bto\bok\bke\ben\bn-\b-r\bri\bin\bng\bg types are recognized, although
- support for a f\bfd\bdd\bdi\bi hardware type (and others) would also
- be desirable. The _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs should be a set of
- hexadecimal octets (numbers from 0 through ff) seperated
- by colons. The _\bh_\ba_\br_\bd_\bw_\ba_\br_\be statement may also be used for
- DHCP clients.
- T\bTh\bhe\be _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
+dhcpd.conf(5) dhcpd.conf(5)
- f\bfi\bil\ble\ben\bna\bam\bme\be "\b"_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be"\b";\b;
- The _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be statement can be used to specify the name of
- the initial boot file which is to be loaded by a client.
The _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be should be a filename recognizable to whatever
- file transfer protocol the client can be expected to use
+ file transfer protocol the client can be expected to use
to load the file.
T\bTh\bhe\be _\bs_\be_\br_\bv_\be_\br_\b-_\bn_\ba_\bm_\be s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
n\bne\bex\bxt\bt-\b-s\bse\ber\brv\bve\ber\br _\bs_\be_\br_\bv_\be_\br_\b-_\bn_\ba_\bm_\be;\b;
- The _\bn_\be_\bx_\bt_\b-_\bs_\be_\br_\bv_\be_\br statement is used to specify the host
- address of the server from which the initial boot file
- (specified in the _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be statement) is to be loaded.
- _\bS_\be_\br_\bv_\be_\br_\b-_\bn_\ba_\bm_\be should be a numeric IP address or a domain
- name. If no _\bn_\be_\bx_\bt_\b-_\bs_\be_\br_\bv_\be_\br parameter applies to a given
+ The _\bn_\be_\bx_\bt_\b-_\bs_\be_\br_\bv_\be_\br statement is used to specify the host
+ address of the server from which the initial boot file
+ (specified in the _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be statement) is to be loaded.
+ _\bS_\be_\br_\bv_\be_\br_\b-_\bn_\ba_\bm_\be should be a numeric IP address or a domain
+ name. If no _\bn_\be_\bx_\bt_\b-_\bs_\be_\br_\bv_\be_\br parameter applies to a given
client, the DHCP server's IP address is used.
T\bTh\bhe\be _\bf_\bi_\bx_\be_\bd_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
-
-
- 18
-
-
-
-
-
-dhcpd.conf(5) dhcpd.conf(5)
-
-
f\bfi\bix\bxe\bed\bd-\b-a\bad\bdd\bdr\bre\bes\bss\bs _\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\ba_\bd_\bd_\br_\be_\bs_\bs ... ];\b;
- The _\bf_\bi_\bx_\be_\bd_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs statement is used to assign one or more
- fixed IP addresses to a client. It should only appear in
+ The _\bf_\bi_\bx_\be_\bd_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs statement is used to assign one or more
+ fixed IP addresses to a client. It should only appear in
a _\bh_\bo_\bs_\bt declaration. If more than one address is supplied,
- then when the client boots, it will be assigned the
- address which corresponds to the network on which it is
- booting. If none of the addresses in the _\bf_\bi_\bx_\be_\bd_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
- statement are on the network on which the client is boot
- ing, that client will not match the _\bh_\bo_\bs_\bt declaration con
+ then when the client boots, it will be assigned the
+ address which corresponds to the network on which it is
+ booting. If none of the addresses in the _\bf_\bi_\bx_\be_\bd_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ statement are on the network on which the client is boot
+ ing, that client will not match the _\bh_\bo_\bs_\bt declaration con
taining that _\bf_\bi_\bx_\be_\bd_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs statement. Each _\ba_\bd_\bd_\br_\be_\bs_\bs should
be either an IP address or a domain name which resolves to
one or more IP addresses.
d\bdy\byn\bna\bam\bmi\bic\bc-\b-b\bbo\boo\bot\btp\bp-\b-l\ble\bea\bas\bse\be-\b-c\bcu\but\bto\bof\bff\bf _\bd_\ba_\bt_\be;\b;
- The _\bd_\by_\bn_\ba_\bm_\bi_\bc_\b-_\bb_\bo_\bo_\bt_\bp_\b-_\bl_\be_\ba_\bs_\be_\b-_\bc_\bu_\bt_\bo_\bf_\bf statement sets the ending
+ The _\bd_\by_\bn_\ba_\bm_\bi_\bc_\b-_\bb_\bo_\bo_\bt_\bp_\b-_\bl_\be_\ba_\bs_\be_\b-_\bc_\bu_\bt_\bo_\bf_\bf statement sets the ending
time for all leases assigned dynamically to BOOTP clients.
- Because BOOTP clients do not have any way of renewing
- leases, and don't know that their leases could expire, by
+ Because BOOTP clients do not have any way of renewing
+ leases, and don't know that their leases could expire, by
default dhcpd assignes infinite leases to all BOOTP
clients. However, it may make sense in some situations to
- set a cutoff date for all BOOTP leases - for example, the
+ set a cutoff date for all BOOTP leases - for example, the
end of a school term, or the time at night when a facility
is closed and all machines are required to be powered off.
_\bD_\ba_\bt_\be should be the date on which all assigned BOOTP leases
- will end. The date is specified in the form:
- W YYYY/MM/DD HH:MM:SS
- W is the day of the week expressed as a number from zero
- (Sunday) to six (Saturday). YYYY is the year, including
- the century. MM is the month expressed as a number from 1
- to 12. DD is the day of the month, counting from 1. HH
- is the hour, from zero to 23. MM is the minute and SS is
- the second. The time is always in Greenwich Mean Time
- (GMT), not local time.
- T\bTh\bhe\be _\bd_\by_\bn_\ba_\bm_\bi_\bc_\b-_\bb_\bo_\bo_\bt_\bp_\b-_\bl_\be_\ba_\bs_\be_\b-_\bl_\be_\bn_\bg_\bt_\bh s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
+ 21
- d\bdy\byn\bna\bam\bmi\bic\bc-\b-b\bbo\boo\bot\btp\bp-\b-l\ble\bea\bas\bse\be-\b-l\ble\ben\bng\bgt\bth\bh _\bl_\be_\bn_\bg_\bt_\bh;\b;
- The _\bd_\by_\bn_\ba_\bm_\bi_\bc_\b-_\bb_\bo_\bo_\bt_\bp_\b-_\bl_\be_\ba_\bs_\be_\b-_\bl_\be_\bn_\bg_\bt_\bh statement is used to set
- the length of leases dynamically assigned to BOOTP
- clients. At some sites, it may be possible to assume
- that a lease is no longer in use if its holder has not
- used BOOTP or DHCP to get its address within a certain
- time period. The period is specified in _\bl_\be_\bn_\bg_\bt_\bh as a num
- ber of seconds. If a client reboots using BOOTP during
- the timeout period, the lease duration is reset to _\bl_\be_\bn_\bg_\bt_\bh,
- so a BOOTP client that boots frequently enough will never
- 19
+dhcpd.conf(5) dhcpd.conf(5)
+ will end. The date is specified in the form:
+ W YYYY/MM/DD HH:MM:SS
+ W is the day of the week expressed as a number from zero
+ (Sunday) to six (Saturday). YYYY is the year, including
+ the century. MM is the month expressed as a number from 1
+ to 12. DD is the day of the month, counting from 1. HH
+ is the hour, from zero to 23. MM is the minute and SS is
+ the second. The time is always in Greenwich Mean Time
+ (GMT), not local time.
-dhcpd.conf(5) dhcpd.conf(5)
+ T\bTh\bhe\be _\bd_\by_\bn_\ba_\bm_\bi_\bc_\b-_\bb_\bo_\bo_\bt_\bp_\b-_\bl_\be_\ba_\bs_\be_\b-_\bl_\be_\bn_\bg_\bt_\bh s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
+ d\bdy\byn\bna\bam\bmi\bic\bc-\b-b\bbo\boo\bot\btp\bp-\b-l\ble\bea\bas\bse\be-\b-l\ble\ben\bng\bgt\bth\bh _\bl_\be_\bn_\bg_\bt_\bh;\b;
+ The _\bd_\by_\bn_\ba_\bm_\bi_\bc_\b-_\bb_\bo_\bo_\bt_\bp_\b-_\bl_\be_\ba_\bs_\be_\b-_\bl_\be_\bn_\bg_\bt_\bh statement is used to set
+ the length of leases dynamically assigned to BOOTP
+ clients. At some sites, it may be possible to assume
+ that a lease is no longer in use if its holder has not
+ used BOOTP or DHCP to get its address within a certain
+ time period. The period is specified in _\bl_\be_\bn_\bg_\bt_\bh as a num
+ ber of seconds. If a client reboots using BOOTP during
+ the timeout period, the lease duration is reset to _\bl_\be_\bn_\bg_\bt_\bh,
+ so a BOOTP client that boots frequently enough will never
lose its lease. Needless to say, this parameter should be
adjusted with extreme caution.
g\bge\bet\bt-\b-l\ble\bea\bas\bse\be-\b-h\bho\bos\bst\btn\bna\bam\bme\bes\bs _\bf_\bl_\ba_\bg;\b;
- The _\bg_\be_\bt_\b-_\bl_\be_\ba_\bs_\be_\b-_\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be_\bs statement is used to tell dhcpd
+ The _\bg_\be_\bt_\b-_\bl_\be_\ba_\bs_\be_\b-_\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be_\bs statement is used to tell dhcpd
whether or not to look up the domain name corresponding to
- the IP address of each address in the lease pool and use
- that address for the DHCP _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be option. If _\bf_\bl_\ba_\bg is
- true, then this lookup is done for all addresses in the
- current scope. By default, or if _\bf_\bl_\ba_\bg is false, no
+ the IP address of each address in the lease pool and use
+ that address for the DHCP _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be option. If _\bf_\bl_\ba_\bg is
+ true, then this lookup is done for all addresses in the
+ current scope. By default, or if _\bf_\bl_\ba_\bg is false, no
lookups are done.
T\bTh\bhe\be _\bu_\bs_\be_\b-_\bh_\bo_\bs_\bt_\b-_\bd_\be_\bc_\bl_\b-_\bn_\ba_\bm_\be_\bs s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
u\bus\bse\be-\b-h\bho\bos\bst\bt-\b-d\bde\bec\bcl\bl-\b-n\bna\bam\bme\bes\bs _\bf_\bl_\ba_\bg;\b;
- If the _\bu_\bs_\be_\b-_\bh_\bo_\bs_\bt_\b-_\bd_\be_\bc_\bl_\b-_\bn_\ba_\bm_\be_\bs parameter is true in a given
- scope, then for every host declaration within that scope,
- the name provided for the host declaration will be sup
+ If the _\bu_\bs_\be_\b-_\bh_\bo_\bs_\bt_\b-_\bd_\be_\bc_\bl_\b-_\bn_\ba_\bm_\be_\bs parameter is true in a given
+ scope, then for every host declaration within that scope,
+ the name provided for the host declaration will be sup
plied to the client as its hostname. So, for example,
group {
host joe {
hardware ethernet 08:00:2b:4c:29:32;
+
+
+
+ 22
+
+
+
+
+
+dhcpd.conf(5) dhcpd.conf(5)
+
+
fixed-address joe.fugue.com;
}
}
option host-name "joe";
}
- An _\bo_\bp_\bt_\bi_\bo_\bn _\bh_\bo_\bs_\bt_\b-_\bn_\ba_\bm_\be statement within a host declaration
+ An _\bo_\bp_\bt_\bi_\bo_\bn _\bh_\bo_\bs_\bt_\b-_\bn_\ba_\bm_\be statement within a host declaration
will override the use of the name in the host declaration.
T\bTh\bhe\be _\ba_\bu_\bt_\bh_\bo_\br_\bi_\bt_\ba_\bt_\bi_\bv_\be s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
n\bno\bot\bt a\bau\but\bth\bho\bor\bri\bit\bta\bat\bti\biv\bve\be;\b;
- The DHCP server will normally assume that the configura
+ The DHCP server will normally assume that the configura
tion information about a given network segment is known to
be correct and is authoritative. So if a client requests
- an IP address on a given network segment that the server
-
-
-
- 20
-
-
-
-
-
-dhcpd.conf(5) dhcpd.conf(5)
-
-
- knows is not valid for that segment, the server will
+ an IP address on a given network segment that the server
+ knows is not valid for that segment, the server will
respond with a DHCPNAK message, causing the client to for
get its IP address and try to get a new one.
- If a DHCP server is being configured by somebody who is
- not the network administrator and who therefore does not
+ If a DHCP server is being configured by somebody who is
+ not the network administrator and who therefore does not
wish to assert this level of authority, then the statement
- "not authoritative" should be written in the appropriate
+ "not authoritative" should be written in the appropriate
scope in the configuration file.
- Usually, writing n\bno\bot\bt a\bau\but\bth\bho\bor\bri\bit\bta\bat\bti\biv\bve\be;\b; at the top level of
+ Usually, writing n\bno\bot\bt a\bau\but\bth\bho\bor\bri\bit\bta\bat\bti\biv\bve\be;\b; at the top level of
the file should be sufficient. However, if a DHCP server
- is to be set up so that it is aware of some networks for
- which it is authoritative and some networks for which it
+ is to be set up so that it is aware of some networks for
+ which it is authoritative and some networks for which it
is not, it may be more appropriate to declare authority on
a per-network-segment basis.
Note that the most specific scope for which the concept of
- authority makes any sense is the physical network segment
- - either a shared-network statement or a subnet statement
- that is not contained within a shared-network statement.
+ authority makes any sense is the physical network segment
+ - either a shared-network statement or a subnet statement
+ that is not contained within a shared-network statement.
It is not meaningful to specify that the server is author
- itative for some subnets within a shared network, but not
- authoritative for others, nor is it meaningful to specify
- that the server is authoritative for some host declara
+ itative for some subnets within a shared network, but not
+ authoritative for others, nor is it meaningful to specify
+ that the server is authoritative for some host declara
tions and not others.
T\bTh\bhe\be _\ba_\bl_\bw_\ba_\by_\bs_\b-_\br_\be_\bp_\bl_\by_\b-_\br_\bf_\bc_\b1_\b0_\b4_\b8 s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
- a\bal\blw\bwa\bay\bys\bs-\b-r\bre\bep\bpl\bly\by-\b-r\brf\bfc\bc1\b10\b04\b48\b8 _\bf_\bl_\ba_\bg;\b;
- Some BOOTP clients expect RFC1048-style responses, but do
- not follow RFC1048 when sending their requests. You can
- tell that a client is having this problem if it is not
- getting the options you have configured for it and if you
- see in the server log the message "(non-rfc1048)" printed
- with each BOOTREQUEST that is logged.
- If you want to send rfc1048 options to such a client, you
- can set the a\bal\blw\bwa\bay\bys\bs-\b-r\bre\bep\bpl\bly\by-\b-r\brf\bfc\bc1\b10\b04\b48\b8 option in that client's
- host declaration, and the DHCP server will respond with an
- RFC-1048-style vendor options field. This flag can be
- set in any scope, and will affect all clients covered by
- that scope.
- T\bTh\bhe\be _\ba_\bl_\bw_\ba_\by_\bs_\b-_\bb_\br_\bo_\ba_\bd_\bc_\ba_\bs_\bt s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
+ 23
- a\bal\blw\bwa\bay\bys\bs-\b-b\bbr\bro\boa\bad\bdc\bca\bas\bst\bt _\bf_\bl_\ba_\bg;\b;
- The DHCP and BOOTP protocols both require DHCP and BOOTP
- clients to set the broadcast bit in the flags field of the
- BOOTP message header. Unfortunately, some DHCP and BOOTP
- clients do not do this, and therefore may not receive
- responses from the DHCP server. The DHCP server can be
- 21
+dhcpd.conf(5) dhcpd.conf(5)
+ a\bal\blw\bwa\bay\bys\bs-\b-r\bre\bep\bpl\bly\by-\b-r\brf\bfc\bc1\b10\b04\b48\b8 _\bf_\bl_\ba_\bg;\b;
+ Some BOOTP clients expect RFC1048-style responses, but do
+ not follow RFC1048 when sending their requests. You can
+ tell that a client is having this problem if it is not
+ getting the options you have configured for it and if you
+ see in the server log the message "(non-rfc1048)" printed
+ with each BOOTREQUEST that is logged.
+ If you want to send rfc1048 options to such a client, you
+ can set the a\bal\blw\bwa\bay\bys\bs-\b-r\bre\bep\bpl\bly\by-\b-r\brf\bfc\bc1\b10\b04\b48\b8 option in that client's
+ host declaration, and the DHCP server will respond with an
+ RFC-1048-style vendor options field. This flag can be
+ set in any scope, and will affect all clients covered by
+ that scope.
-dhcpd.conf(5) dhcpd.conf(5)
+ T\bTh\bhe\be _\ba_\bl_\bw_\ba_\by_\bs_\b-_\bb_\br_\bo_\ba_\bd_\bc_\ba_\bs_\bt s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
+ a\bal\blw\bwa\bay\bys\bs-\b-b\bbr\bro\boa\bad\bdc\bca\bas\bst\bt _\bf_\bl_\ba_\bg;\b;
- made to always broadcast its responses to clients by set
- ting this flag to 'on' for the relevant scope. To avoid
+ The DHCP and BOOTP protocols both require DHCP and BOOTP
+ clients to set the broadcast bit in the flags field of the
+ BOOTP message header. Unfortunately, some DHCP and BOOTP
+ clients do not do this, and therefore may not receive
+ responses from the DHCP server. The DHCP server can be
+ made to always broadcast its responses to clients by set
+ ting this flag to 'on' for the relevant scope. To avoid
creating excess broadcast traffic on your network, we rec
- ommend that you restrict the use of this option to as few
- clients as possible. For example, the Microsoft DHCP
+ ommend that you restrict the use of this option to as few
+ clients as possible. For example, the Microsoft DHCP
client is known not to have this problem, as are the Open
Transport and ISC DHCP clients.
o\bon\bne\be-\b-l\ble\bea\bas\bse\be-\b-p\bpe\ber\br-\b-c\bcl\bli\bie\ben\bnt\bt _\bf_\bl_\ba_\bg;\b;
If this flag is enabled, whenever a client sends a DHCPRE
- QUEST for a particular lease, the server will automati
- cally free any other leases the client holds. This pre
- sumes that when the client sends a DHCPREQUEST, it has
- forgotten any lease not mentioned in the DHCPREQUEST -
- i.e., the client has only a single network interface _\ba_\bn_\bd
- it does not remember leases it's holding on networks to
- which it is not currently attached. Neither of these
+ QUEST for a particular lease, the server will automati
+ cally free any other leases the client holds. This pre
+ sumes that when the client sends a DHCPREQUEST, it has
+ forgotten any lease not mentioned in the DHCPREQUEST -
+ i.e., the client has only a single network interface _\ba_\bn_\bd
+ it does not remember leases it's holding on networks to
+ which it is not currently attached. Neither of these
assumptions are guaranteed or provable, so we urge caution
in the use of this statement.
u\bus\bse\be-\b-l\ble\bea\bas\bse\be-\b-a\bad\bdd\bdr\br-\b-f\bfo\bor\br-\b-d\bde\bef\bfa\bau\bul\blt\bt-\b-r\bro\bou\but\bte\be _\bf_\bl_\ba_\bg;\b;
- If the _\bu_\bs_\be_\b-_\bl_\be_\ba_\bs_\be_\b-_\ba_\bd_\bd_\br_\b-_\bf_\bo_\br_\b-_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b-_\br_\bo_\bu_\bt_\be parameter is true
- in a given scope, then instead of sending the value speci
- fied in the routers option (or sending no value at all),
- the IP address of the lease being assigned is sent to the
- client. This supposedly causes Win95 machines to ARP for
- all IP addresses, which can be helpful if your router is
- configured for proxy ARP.
+ If the _\bu_\bs_\be_\b-_\bl_\be_\ba_\bs_\be_\b-_\ba_\bd_\bd_\br_\b-_\bf_\bo_\br_\b-_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b-_\br_\bo_\bu_\bt_\be parameter is true
+ in a given scope, then instead of sending the value
- T\bTh\bhe\be _\bs_\be_\br_\bv_\be_\br_\b-_\bi_\bd_\be_\bn_\bt_\bi_\bf_\bi_\be_\br s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
- s\bse\ber\brv\bve\ber\br-\b-i\bid\bde\ben\bnt\bti\bif\bfi\bie\ber\br _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be;\b;
- The server-identifier statement can be used to define the
- value that is sent in the DHCP Server Identifier option
- for a given scope. The value specified m\bmu\bus\bst\bt be an IP
- address for the DHCP server, and must be reachable by all
- clients served by a particular scope.
+ 24
- The use of the server-identifier statement is not recom
- mended - the only reason to use it is to force a value
- other than the default value to be sent on occasions where
- the default value would be incorrect. The default value
- is the first IP address associated with the physical net
- work interface on which the request arrived.
- The usual case where the _\bs_\be_\br_\bv_\be_\br_\b-_\bi_\bd_\be_\bn_\bt_\bi_\bf_\bi_\be_\br statement needs
- to be sent is when a physical interface has more than one
- 22
+dhcpd.conf(5) dhcpd.conf(5)
+ specified in the routers option (or sending no value at
+ all), the IP address of the lease being assigned is sent
+ to the client. This supposedly causes Win95 machines to
+ ARP for all IP addresses, which can be helpful if your
+ router is configured for proxy ARP.
+ T\bTh\bhe\be _\bs_\be_\br_\bv_\be_\br_\b-_\bi_\bd_\be_\bn_\bt_\bi_\bf_\bi_\be_\br s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
+ s\bse\ber\brv\bve\ber\br-\b-i\bid\bde\ben\bnt\bti\bif\bfi\bie\ber\br _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be;\b;
-dhcpd.conf(5) dhcpd.conf(5)
+ The server-identifier statement can be used to define the
+ value that is sent in the DHCP Server Identifier option
+ for a given scope. The value specified m\bmu\bus\bst\bt be an IP
+ address for the DHCP server, and must be reachable by all
+ clients served by a particular scope.
+ The use of the server-identifier statement is not recom
+ mended - the only reason to use it is to force a value
+ other than the default value to be sent on occasions where
+ the default value would be incorrect. The default value
+ is the first IP address associated with the physical net
+ work interface on which the request arrived.
+ The usual case where the _\bs_\be_\br_\bv_\be_\br_\b-_\bi_\bd_\be_\bn_\bt_\bi_\bf_\bi_\be_\br statement needs
+ to be sent is when a physical interface has more than one
IP address, and the one being sent by default isn't appro
- priate for some or all clients served by that interface.
- Another common case is when an alias is defined for the
- purpose of having a consistent IP address for the DHCP
- server, and it is desired that the clients use this IP
+ priate for some or all clients served by that interface.
+ Another common case is when an alias is defined for the
+ purpose of having a consistent IP address for the DHCP
+ server, and it is desired that the clients use this IP
address when contacting the server.
Supplying a value for the dhcp-server-identifier option is
equivalent to using the server-identifier statement.
+ T\bTh\bhe\be _\bd_\bd_\bn_\bs_\b-_\bu_\bp_\bd_\ba_\bt_\be_\bs s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
+
+ d\bdd\bdn\bns\bs-\b-u\bup\bpd\bda\bat\bte\bes\bs _\bf_\bl_\ba_\bg;\b;
+
+ The _\bd_\bd_\bn_\bs_\b-_\bu_\bp_\bd_\ba_\bt_\be_\bs parameter controls whether or not the
+ server will attempt to do a ddns update when a lease is
+ confirmed. Set this to _\bo_\bf_\bf if the server should not
+ attempt to do updates within a certain scope. The _\bd_\bd_\bn_\bs_\b-
+ _\bu_\bp_\bd_\ba_\bt_\be_\bs parameter is on by default.
+
R\bRE\bEF\bFE\bER\bRE\bEN\bNC\bCE\bE:\b: O\bOP\bPT\bTI\bIO\bON\bN S\bST\bTA\bAT\bTE\bEM\bME\bEN\bNT\bTS\bS
- DHCP option statements are documented in the d\bdh\bhc\bcp\bp-\b-
+ DHCP option statements are documented in the d\bdh\bhc\bcp\bp-\b-
o\bop\bpt\bti\bio\bon\bns\bs(\b(5\b5)\b) manual page.
S\bSE\bEE\bE A\bAL\bLS\bSO\bO
A\bAU\bUT\bTH\bHO\bOR\bR
d\bdh\bhc\bcp\bpd\bd(\b(8\b8)\b) was written by Ted Lemon <mellon@vix.com> under a
- contract with Vixie Labs. Funding for this project was
+
+
+
+ 25
+
+
+
+
+
+dhcpd.conf(5) dhcpd.conf(5)
+
+
+ contract with Vixie Labs. Funding for this project was
provided by the Internet Software Consortium. Information
- about the Internet Software Consortium can be found at
+ about the Internet Software Consortium can be found at
h\bht\btt\btp\bp:\b:/\b//\b/w\bww\bww\bw.\b.i\bis\bsc\bc.\b.o\bor\brg\bg/\b/i\bis\bsc\bc.\b.
- 23
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 26
projects / thirdparty / dhcp.git / commitdiff
