Different hardware options based on subnet

glenn.satchell at uniq.com.au glenn.satchell at uniq.com.au
Thu Sep 3 23:24:18 UTC 2020

Hi Ricardo,

How about omitting the allow class option in the specific pool, and add 
all the required info? eg something like this?

pool {
   # allow members of "i2004-clients";
   range ... ;
   option nortel-specific-info = 


On 2020-09-03 23:41, Simon Hobson wrote:
> Ricardo Stella <stella at rider.edu> wrote:
>> Is the problem that the definition in the global section of the config 
>> trumps whatever is defined inside a subnet?
> Normally, definitions in a lower scope (e.g. in a subnet) override
> options made at a higher level (e.g. at the global level). So (for
> example) you can set your DNS servers globally and override them for
> specific subnets or pools.
> However, class definitions and host definitions are always global even
> if declared within a lower scope. This is one that can catch people
> out.
> As classes are "special" in this respect, I could imagine there being
> similar oddities with option inheritance in cases like yours. But I
> don't recall this particular setup being asked before, and I'm not
> familiar with implementation details - I guess if you can read code (I
> assume it's in C) then you could spend the time (possibly a lot of it)
> working out how this particular scenario works.
> Simon
> _______________________________________________
> ISC funds the development of this software with paid support
> subscriptions. Contact us at https://www.isc.org/contact/ for more
> information.
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users

More information about the dhcp-users mailing list