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
+
+ a\bau\but\bth\bho\bor\bri\bit\bta\bat\bti\biv\bve\be;\b;
+
+ 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
+ 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
+ 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
+ wish to assert this level of authority, then the statement
+ "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
+ 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 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
+
+
+
+ 11
+
+
+
+
+
+dhcpd.conf(5) dhcpd.conf(5)
+
+
+ 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
+ tions and not others.
+
T\bTh\bhe\be _\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 s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
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
+ 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
+ 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
+ all IP addresses, which can be helpful if your router is
configured for proxy ARP.
If use-lease-addr-for-default-route is enabled and an
- option routers statement are both in scope, the routers
- option will be preferred. The rationale for this is that
- in situations where you want to use this feature, you
- probably want it enabled for a whole bunch of Windows 95
- machines, and you want to override it for a few other
- machines. Unfortunately, if the opposite happens to be
- true for you site, you are probably better off not trying
+ option routers statement are both in scope, the routers
+ option will be preferred. The rationale for this is that
+ in situations where you want to use this feature, you
+ probably want it enabled for a whole bunch of Windows 95
+ machines, and you want to override it for a few other
+ machines. Unfortunately, if the opposite happens to be
+ true for you site, you are probably better off not trying
to use this flag.
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
+ 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 appropri
+ ate for some or all clients served by that interface.
+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-
+ o\bop\bpt\bti\bio\bon\bns\bs(\b(5\b5)\b) manual page.
- 11
+ 12
-dhcpd.conf(5) dhcpd.conf(5)
- 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 appropri
- ate for some or all clients served by that interface.
+dhcpd.conf(5) dhcpd.conf(5)
-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-
- o\bop\bpt\bti\bio\bon\bns\bs(\b(5\b5)\b) manual page.
S\bSE\bEE\bE A\bAL\bLS\bSO\bO
dhcpd.conf(5), dhcpd.leases(5), RFC2132, RFC2131.
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
- provided by the Internet Software Corporation. Informa
- tion about the Internet Software Consortium can be found
+ contract with Vixie Labs. Funding for this project was
+ provided by the Internet Software Corporation. Informa
+ tion 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.
- 12
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 13
projects / thirdparty / dhcp.git / commitdiff
