I tried creating a different class, but because hardware is the same, they fall under the first defined one. I tried adding the above inside the pool section but they still get the globally defined one. Am I missing something? Or would I need to assign the class or the above lines to every vlan and take it out of the global config?
_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
I tried creating a different class, but because
hardware is the same, they fall under the first defined
one. I tried adding the above inside the pool section but
they still get the globally defined one. Am I missing
something? Or would I need to assign the class or the
above lines to every vlan and take it out of the global
config?
_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
I tried creating a different class, but because
hardware is the same, they fall under the first defined
one. I tried adding the above inside the pool section but
they still get the globally defined one. Am I missing
something? Or would I need to assign the class or the
above lines to every vlan and take it out of the global
config?
_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
I tried creating a different class, but because
hardware is the same, they fall under the first defined
one. I tried adding the above inside the pool section but
they still get the globally defined one. Am I missing
something? Or would I need to assign the class or the
above lines to every vlan and take it out of the global
config?
_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
> 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.
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 =
"Nortel-i2004-A,10.2.0.10:4100,1,15;10.2.0.10:4100,1,15.";
]
regards,
-glenn
On 2020-09-03 23:41, Simon Hobson wrote:
> Ricardo Stella <[hidden email]> 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
> [hidden email] > https://lists.isc.org/mailman/listinfo/dhcp-users
_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.