vendor-encapsulated-options and Scope
David W. Hankins
David_Hankins at isc.org
Thu Dec 11 20:21:17 UTC 2008
On Thu, Dec 11, 2008 at 01:22:46PM -0600, Martin McCormick wrote:
> My thanks to all. I think I understand this better
> especially after seeing what happened yesterday. Every access
> point that fit the cryteria got hosed and it now makes perfect
> sense as to why. It's kind of easy to start thinking everything
> can be scoped and this was a great reminder that that is not
It's not your fault, the configuration syntax creates this expectation
and then fails to deliver on it.
It adds insult to injury when scoping such parameters causes them to
inherit the 'group' scoping of their parent; inheriting options from
contexts that are normally inappropriate.
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil? https://secure.isc.org/store/t-shirt/
David W. Hankins "If you don't do it right the first time,
Software Engineer you'll just have to do it again."
Internet Systems Consortium, Inc. -- Jack T. Hankins
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 194 bytes
Desc: not available
More information about the dhcp-users