Send dhcp-users mailing list submissions to
        dhcp-users@lists.isc.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
        dhcp-users-requ...@lists.isc.org

You can reach the person managing the list at
        dhcp-users-ow...@lists.isc.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."


Today's Topics:

   1. Prefix Delegation patch for isc-dhcp-4.3.6 (Mike)
   2. Re: Conditional File Include (Norman Elton)


----------------------------------------------------------------------

Message: 1
Date: Tue, 8 Aug 2017 10:06:56 -0400
From: Mike <the.li...@mgm51.com>
To: dhcp-users@lists.isc.org
Subject: Prefix Delegation patch for isc-dhcp-4.3.6
Message-ID: <f216ef65-c85f-b8a9-5171-df797882e...@mgm51.com>
Content-Type: text/plain; charset=windows-1252




This patch allows for a prefix length to specified when requesting a
prefix delegation.

Updated for version 4.3.6

https://archive.mgm51.com/sources/pd-pref.html

_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users



------------------------------

Message: 2
Date: Tue, 8 Aug 2017 15:17:22 -0400
From: Norman Elton <normel...@gmail.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Conditional File Include
Message-ID:
        <capcnwuewpkbwfpab0lybao9cbwrsh+-j8xue1reopcwd5-v...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

Yes, the goal is to keep all the configuration centralized. And a
templating mechanism would work, but adds a bit of complexity that
we've, so far, managed to avoid. Perhaps it's inevitable.

>> Just put all identical configuration to single included file
>> and include it to two distinct dhcpd.conf's each having own "failover peer"
>> statements and, perhaps, something other like "subnet".

Each system only has one /etc/dhcpd.conf, which is where I'd like to
include a host-specific file that defines the failover configuration.
But that single top-level file would need to be stored in the
repository.

Perhaps the /etc/init.d/dhcpd startup script could be modified to
point to a host-specific main config file
(/etc/dhcpd-<hostname>.conf). That's an option. Again, it's a
balancing act of introducing complexity in one place to avoid
complexity in another.

Thanks all for the ideas,

Norman





On Tue, Aug 8, 2017 at 3:56 AM, Eugene Grosbein <eu...@grosbein.net> wrote:
> 08.08.2017 3:23, Simon Hobson wrote:
>
>> Eugene Grosbein <eu...@grosbein.net> wrote:
>>
>>> Just put all identical configuration to single included file
>>> and include it to two distinct dhcpd.conf's each having own "failover peer"
>>> statements and, perhaps, something other like "subnet".
>>
>> I suspect the reason is that it moves some of the config outside of the 
>> management process.
>
> I don't see how that would occur.
>
>> While it works, it means that the config is now split in 3 places -
>> while the aim was to keep it in one place (with tracking of changes etc).
>
> One cannot keep failover configs in one place without some kind of 
> preprocessing.
>
> And every part of config is still kept in one of 3 single places,
> either in common part or in one of individual parts.
>
> It just works.
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users


------------------------------

Subject: Digest Footer

_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users

------------------------------

End of dhcp-users Digest, Vol 106, Issue 7
******************************************

Reply via email to