From: Ted Lemon Date: Tue, 9 Feb 1999 04:58:44 +0000 (+0000) Subject: Regenerate X-Git-Tag: V2-BETA-1-PATCH-11~3 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=bc2f4f571d2a154bfc2376bbc46c629a602c7097;p=thirdparty%2Fdhcp.git Regenerate --- diff --git a/server/dhcpd.conf.cat5 b/server/dhcpd.conf.cat5 index c957b345c..e44da0ada 100644 --- a/server/dhcpd.conf.cat5 +++ b/server/dhcpd.conf.cat5 @@ -688,73 +688,122 @@ dhcpd.conf(5) dhcpd.conf(5) An _o_p_t_i_o_n _h_o_s_t_-_n_a_m_e statement within a host declaration will override the use of the name in the host declaration. + TThhee _a_u_t_h_o_r_i_t_a_t_i_v_e ssttaatteemmeenntt + + aauutthhoorriittaattiivvee;; + + nnoott aauutthhoorriittaattiivvee;; + + 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 nnoott aauutthhoorriittaattiivvee;; 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. + TThhee _u_s_e_-_l_e_a_s_e_-_a_d_d_r_-_f_o_r_-_d_e_f_a_u_l_t_-_r_o_u_t_e ssttaatteemmeenntt uussee--lleeaassee--aaddddrr--ffoorr--ddeeffaauulltt--rroouuttee _f_l_a_g;; - If the _u_s_e_-_l_e_a_s_e_-_a_d_d_r_-_f_o_r_-_d_e_f_a_u_l_t_-_r_o_u_t_e parameter is true + If the _u_s_e_-_l_e_a_s_e_-_a_d_d_r_-_f_o_r_-_d_e_f_a_u_l_t_-_r_o_u_t_e 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. TThhee _s_e_r_v_e_r_-_i_d_e_n_t_i_f_i_e_r ssttaatteemmeenntt sseerrvveerr--iiddeennttiiffiieerr _h_o_s_t_n_a_m_e;; - 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 mmuusstt 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 mmuusstt 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 _s_e_r_v_e_r_-_i_d_e_n_t_i_f_i_e_r 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. +RREEFFEERREENNCCEE:: OOPPTTIIOONN SSTTAATTEEMMEENNTTSS + DHCP option statements are documented in the ddhhccpp-- + ooppttiioonnss((55)) 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 _s_e_r_v_e_r_-_i_d_e_n_t_i_f_i_e_r 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) -RREEFFEERREENNCCEE:: OOPPTTIIOONN SSTTAATTEEMMEENNTTSS - DHCP option statements are documented in the ddhhccpp-- - ooppttiioonnss((55)) manual page. SSEEEE AALLSSOO dhcpd.conf(5), dhcpd.leases(5), RFC2132, RFC2131. AAUUTTHHOORR ddhhccppdd((88)) was written by Ted Lemon 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 hhttttpp::////wwwwww..iisscc..oorrgg//iisscc.. @@ -787,6 +836,23 @@ AAUUTTHHOORR - 12 + + + + + + + + + + + + + + + + + + 13