*** From dhcp-server -- To unsubscribe, see the end of this message. ***
> Is there a document somewhere that describes what the conf relationships
> are between groups, pools, subnets, hosts and shared networks?
The manual page is the best that's currently available, although there
will be an explanation in Ralph Droms' and my upcoming book, "The DHCP
Handbook." (That's the working title, anyway). Unfortunately, it's
not out yet.
Briefly, scoping is lexical - that is, it's just as you write it.
Clients can appear in as many as four kinds of root scopes at the same
time: class scopes, host declaration scopes, subnet declaration scopes
and pool declaration scopes. The scopes a client appears in depend on
what it matches - if it's going to get an address, it'll always match
some subnet scope. If it's got a host declaration, it matches that
host declaration's scope. If it's matches any class declarations,
it's in the scope of all those class declarations. If its address
comes from a pool, it matches that pool's scope as well.
The most specific scope wins if there's a conflict between parameter
or option definitions in different scopes. The scopes that apply to
any given client are the scopes outer from its pool declaration, its
subnet declaration, its class declarations (if it matches any) and
it's host declarations, if it matches any. Host declarations are more
specific than classes, which are more specific than pools.
Let's say that a client matches a host declaration, a class
declaration, and gets its lease from a pool. The way scoping is going
to work is that scopes are considered in reverse order of priority,
and the last definition of a particular value always wins. So the
server will first start from the pool scope (if the lease came from a
pool - fixed-address leases don't have a pool scope) and work its way
out to the global scope. Then it will start from the subnet scope of
the declaration for the subnet that contains that lease and work its
way out until it comes to a scope that is the same as a scope outer
from the pool scope - usually this is the shared-network scope. Then
it will start from the class scope and work its way out, stopping
again when it comes to a scope it's already seen. Finally it will
start from the host scope and work its way out, again stopping when it
comes to a scope it's already seen.
Does that help at all, or have I just completely muddied the waters?
:'}
_MelloN_
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
Archives for this mailing list are available at
http://www.webnology.com/list-archives/dhcp/dhcp-server
------------------------------------------------------------------------------
