Common settings

Mike Richardson mike.richardson at manchester.ac.uk
Wed Nov 30 08:30:35 UTC 2016


On Tue, Nov 29, 2016 at 05:11:28PM +0000, Niall O'Reilly wrote:
>   In the general case, there's no nice way to make one group of subnets
>   have the values for certain options in common, while another group has
>   a different set of common values for the same or another set of options.
>   Specifying the options repeatedly inside each '{' ... '}' block is all
>   that can be done.

Ok, thanks. My best bet then it probably a script which generates a suitable
file to be included in the main config.

>   That said, if you can match a common set of options to a particular
>   set of network devices by topology (shared-network) or by device
>   characteristics (class), you can specify the common options in the
>   corresponding shared-network or class definition.

I'd looked at using the class but, because of the precendence rules, that
meant I couldn't have one of the subnet definitions with a setting that
overrode the class one. I can see the logic of having the precedence the way
it us, it just doesn't happen to suit what I'd like to do.

An enhancement along the lines of 'force option blah' would be nice, which
takes precedent over other ones when its section matches a client.

Thanks,

Mike

-- 
Mike Richardson
Networks (network at manchester.ac.uk)
IT Services, University of Manchester
*Plain text only please - attachments stripped on arrival*


More information about the dhcp-users mailing list