mir/isc-dhcp
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/dhcp synced 2025-09-01 14:55:30 +00:00
Code Issues Releases Wiki Activity

- Fix up the blurb that talks about how scoping works.

Browse Source 
- Correct erroneous class example.
This commit is contained in:
Ted Lemon
2000-01-05 18:20:30 +00:00
parent 9e9b2261b1
commit 49f6028f64
1 changed files with 13 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
server/dhcpd.conf.5
View File

@@ -78,17 +78,21 @@ clients from other departments on the same subnet. For clients which
will be declared explicitly with \fIhost\fR declarations, these will be declared explicitly with \fIhost\fR declarations, these
declarations can be enclosed in a \fIgroup\fR declaration along with declarations can be enclosed in a \fIgroup\fR declaration along with
the parameters which are common to that department. For clients the parameters which are common to that department. For clients
whose addresses will be dynamically assigned, there is currently no whose addresses will be dynamically assigned, class declarations and
way to group parameter assignments other than by network topology. conditional declarations may be used to group parameter assignments
based on information the client sends.
.PP .PP
When a client is to be booted, its boot parameters are determined by When a client is to be booted, its boot parameters are determined by
first consulting that client's \fIhost\fR declaration (if any), then consulting that client's \fIhost\fR declaration (if any), and then
consulting the \fIgroup\fR declaration (if any) which enclosed that consulting the any \fIclass\fR declarations matching the client,
\fIhost\fR declaration, then consulting the \fIsubnet\fR declaration followed by the \fIpool\fR, \fIsubnet\fR and \fIshared-network\fR
for the subnet on which the client is booting, then consulting the declarations for the IP address assigned to the client. Each of
\fIshared-network\fR declaration (if any) containing that subnet, and these declarations itself appears within a lexical scope, and all
finally consulting the top-level parameters which may be specified declarations at less specific lexical scopes are also consulted for
outside of any declaration. client option declarations as well. Scopes are never considered
twice, and if parameters are declared in more than one scope, the
parameter declared in the most specific scope is the one that is
used.
.PP .PP
When dhcpd tries to find a \fIhost\fR declaration for a client, it When dhcpd tries to find a \fIhost\fR declaration for a client, it
first looks for a \fIhost\fR declaration which has a first looks for a \fIhost\fR declaration which has a
@@ -497,7 +501,6 @@ of this, you can write a class declaration as follows:
.PP .PP
.nf .nf
class "customer" { class "customer" {
match if exists agent.circuit-id;
spawn with option agent.circuit-id; spawn with option agent.circuit-id;
lease limit 4; lease limit 4;
} }