Lines Matching full:be

16 .\"    of its contributors may be used to endorse or promote products derived
24 .\" CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
59 Comments may be placed anywhere within the file (except within quotes).
75 can be assigned to clients, or to apply a group of parameters to a
77 In any group of parameters and declarations, all parameters must be specified
78 before any declarations which depend on those parameters may be specified.
85 If clients on a subnet are to be assigned addresses dynamically, a
91 only known clients will be served, each such client must have a
94 If parameters are to be applied to a group of declarations which are not
97 declaration can be used.
99 For every subnet which will be served, and for every subnet
100 to which the dhcp server is connected, there must be one
107 declaration is required for each subnet even if no addresses will be
114 to the point where it has more than 254 nodes, it may be necessary to run
116 network can be added.
119 declarations for these two networks may be enclosed in a
124 subnet, but it may be desirable to offer those clients a uniform set
125 of parameters which are different than what would be offered to
127 For clients which will be declared explicitly with
129 declarations, these declarations can be enclosed in a
132 For clients whose addresses will be dynamically assigned, there is currently no
135 When a client is to be booted, its boot parameters are determined by
147 top-level parameters which may be specified outside of any declaration.
210 These might be things like the organization's domain name,
229 might be:
241 So for the first subnet, for example, there should be something like:
249 However, in many cases there may be only one hostname for all of a router's
250 IP addresses, and it would not be appropriate to use that name here.
292 and will be applied according to the scope in which the parameter appears.
297 One way to do this would be to have host declarations for each server
338 Any subnets in a shared network should be declared within a
343 statement will be used when booting clients on those subnets unless
352 should be the name of the shared network.
353 This name is used when printing debugging messages, so it should be
356 (although it will never be used as such), or it may be any arbitrary
371 It may also be used to provide subnet-specific parameters and to
372 specify what addresses may be dynamically allocated to clients booting
382 should be specified as numeric IP addresses.
386 Although a netmask must be given with every subnet declaration, it is
388 subnet-mask option statement be used in each subnet declaration to set
400 For any subnet on which addresses will be assigned dynamically, there
401 must be at least one
404 All IP addresses in the range should be in the subnet in which the
409 flag may be specified if addresses in the specified range may be dynamically
413 can be omitted.
415 There must be at least one
417 statement for every BOOTP client that is to be served:
426 statements may also be specified for DHCP clients, although this is
429 If it is desirable to be able to boot a DHCP or BOOTP
431 address may be specified in the
435 statement may be specified.
440 statements should be used.
442 If a client is to be booted using a fixed address if it's
443 possible, but should be allocated a dynamic address otherwise, then a
445 statement must be specified without a
449 should be a name identifying the host.
472 so the hardware address must be used for all clients that may boot using
486 It can be used to group hosts, shared networks, subnets, or even other groups.
492 statements can be used to control the behaviour of
532 then that client will not be able to get an address from the DHCP server.
538 in seconds that will be assigned to a lease
547 in seconds that will be assigned to a lease
555 BOOTP client to be recognized in a
562 must be the name of a hardware interface type.
574 should be a set of colon-separated hexadecimal octets (0-ff)
575 or a hostname that can be looked up in
580 statement may also be used for DHCP clients.
584 statement can be used to specify the name of the initial boot file which
585 is to be loaded by a client:
591 should be a filename recognizable to whatever file transfer protocol
592 the client can be expected to use to load the file.
596 statement can be used to inform the client of the name of the server
602 should be the name that will be provided to the client.
609 statement) is to be loaded:
614 should be a numeric IP address or a hostname.
628 If more than one address is supplied, then when the client boots, it will be
640 should be either an IP address or a hostname which resolves to one
644 and may therefore not be used with the
663 machines are required to be powered off.
666 should be the date on which all assigned BOOTP leases will end.
686 At some sites, it may be possible to assume that a lease is no longer in
696 Needless to say, this parameter should be adjusted with extreme caution.
719 that scope, the name provided for the host declaration will be supplied to
758 information about a given network segment is known to be correct and
769 should be written in the appropriate scope in the configuration file.
773 at the top level of the file should be sufficient.
774 However, if a DHCP server is to be set up so that it is aware of some
776 it may be more appropriate to declare authority on a per-network-segment basis.
799 which can be helpful if your router is configured for proxy ARP.
804 the routers option will be preferred.
808 Unfortunately, if the opposite happens to be true for your
829 This flag can be set in any scope, and will affect all clients covered
834 statement can be used to define the value that is sent in the
841 be an IP address for the DHCP server, and must be reachable by all
845 reason to use it is to force a value other than the default value to be
846 sent on occasions where the default value would be incorrect.
852 statement needs to be sent is when a physical interface has more than one
874 to be false.