subnet-specific class

[Operator]

----- Original Message ----- 
From: "David W. Hankins" <David_Hankins at isc.org>
To: <dhcp-users at isc.org>
Sent: Thursday, April 12, 2007 9:04 PM
Subject: Re: subnet-specific class


> On Thu, Apr 12, 2007 at 12:33:49PM -0400, Chuck Anderson wrote:
>> match if subnet = 130.215.v.0/255.255.255.0
>
> class "nortel" {
>  match if substring(option vendor-class-identifier, 0, 14)
> = "Nortel-i2004-A";
>  vendor-option-space Nortel;
> }
>
> option Nortel.i2004-server-info "global value";
>
> group {
>  option Nortel.i2004-server-info "group specific value";
>
>  shared-network {
>    option Nortel.i2004-server-info "shared broadcast domain specific 
> value";
>
>    group {
>      option Nortel.i2004-server-info "yet another group specific value";
>
>      subnet 130.215.a.0 netmask 255.255.255.0 {
> option Nortel.i2004-server-info "subnet specific value";
> pool {
>   option Nortel.i2004-server-info "pool specific value";
> }
>      }
>    }
>  }
> }
>
>
> I should change the vendor-option-space example in the manpages.  It's
> misleading to show that the config value 'should' be specified in the
> same scope as the vendor space selection.
>
>> Another approach would be to support subnet-specific classes with the
>> class defined inside the subnet block.
>
> I don't think this is a good reason to replicate the existing option
> cache mechanisms to find configuration caches that are relevant to
> the client's context.
>
> But there are possibly other reasons for this sort of thing,
> particularly when dealing with billing classes.
>
> -- 
> ISC Training!  http://www.isc.org/training/  training at isc.org
> Washington DC area, April 16-20 2007.  DNS & BIND, DDNS & DHCP.
> -- 
> 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
>
>