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. Re: How to sync a Linux secondary DHCP server? (Sten Carlsen)
2. Re: Multiple entries of DHCPv6 option with same code (jamesko)
3. Re: Multiple entries of DHCPv6 option with same code (jamesko)
----------------------------------------------------------------------
Message: 1
Date: Tue, 31 Jul 2018 16:46:13 +0200
From: Sten Carlsen <st...@s-carlsen.dk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>, Thomas Markwalder
<tm...@isc.org>
Subject: Re: How to sync a Linux secondary DHCP server?
Message-ID: <81515176-97c7-a13e-d547-5648f7464...@s-carlsen.dk>
Content-Type: text/plain; charset="utf-8"
Thanks, I did not know and I thought this should be part of the answer.
On 31/07/2018 16.44, Thomas Markwalder wrote:
> Hello Sten:
>
> Those would also have to be manually sync'd. The fail over protocol
> does not extend to reservations.?
>
> Regards,
>
> Thomas
>
> On 07/31/2018 10:21 AM, Sten Carlsen wrote:
>> Just to clarify, "host reservations" can be two things.
>>
>> Host statement, possibly with a fixed address statement -
>> synchronized via file transfer.
>>
>> Reservation in the leases file - how would these function in a fail
>> over pair?
>>
>>
>> On 31/07/2018 16.16, Thomas Markwalder wrote:
>>> Hello Sandra:
>>>
>>> Yes. Anything specified via configuration file must be sync'd
>>> outside of ISC DHCP.
>>> Fail over, in ISC DHCP, is based on draft RFC:
>>>
>>> https://tools.ietf.org/html/draft-ietf-dhc-failover-12
>>>
>>> It does not call for exchanging information beyond lease and server
>>> state information, and
>>> was written such that any two servers which adhere to it, should be
>>> inter operable.? At least
>>> that was the original intent.
>>>
>>> Host reservations are "a policy mechanism" and as such are not
>>> governed by RFCs. Thus they
>>> are entirely specific to DHCP server implementations.
>>>
>>> Regards,
>>>
>>> Thomas Markwalder
>>> ISC Software Engineering
>>>
>>> On 07/31/2018 10:00 AM, Sandra Schlichting wrote:
>>>>> One point of clarification,? Host reservations are not synchronized
>>>>> between servers via fail over.? Any host reservations you have in one
>>>>> configuration file,? you must include in the peer server's
>>>>> configuration
>>>>> file.? For dynamic reservations (i.e. those that do not include a
>>>>> fixed
>>>>> address), the leases allocated for each host will be synchronized
>>>>> (assuming they come from within a FO pool), but not the actual
>>>>> reservation specifications.
>>>> So for the reservation I would have to rsync/scp them over?
>>>> _______________________________________________
>>>> dhcp-users mailing list
>>>> dhcp-users@lists.isc.org
>>>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>>
>>> _______________________________________________
>>> dhcp-users mailing list
>>> dhcp-users@lists.isc.org
>>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>
>>
>>
>> _______________________________________________
>> dhcp-users mailing list
>> dhcp-users@lists.isc.org
>> https://lists.isc.org/mailman/listinfo/dhcp-users
>
>
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20180731/f1519e9a/attachment-0001.html>
------------------------------
Message: 2
Date: Tue, 31 Jul 2018 13:03:35 -0500 (CDT)
From: jamesko <jim.l...@hotmail.com>
To: dhcp-users@lists.isc.org
Subject: Re: Multiple entries of DHCPv6 option with same code
Message-ID: <1533060215456-0.p...@n4.nabble.com>
Content-Type: text/plain; charset=us-ascii
Below is a diff of the changes I made to support the append keyword in
dhcpd6.conf so multiple entries of the same option may be included in a
lease reply. This may not be the most efficient or correct way of handling
it but presented for discussion, review, and integration if possible.
Thanks,
James
--
Sent from: http://isc-dhcp-users.2343191.n4.nabble.com/
------------------------------
Message: 3
Date: Tue, 31 Jul 2018 13:13:11 -0500 (CDT)
From: jamesko <jim.l...@hotmail.com>
To: dhcp-users@lists.isc.org
Subject: Re: Multiple entries of DHCPv6 option with same code
Message-ID: <1533060791119-0.p...@n4.nabble.com>
Content-Type: text/plain; charset=us-ascii
Nabble seems to have deleted the raw diff even though it showed up in the
preview.
Here it is as an attachment.
006-dhcpv6-append-options.patch
<http://isc-dhcp-users.2343191.n4.nabble.com/file/t383/006-dhcpv6-append-options.patch>
--
Sent from: http://isc-dhcp-users.2343191.n4.nabble.com/
------------------------------
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 118, Issue 1
******************************************
