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? (Glenn Satchell)
2. Re: How to sync a Linux secondary DHCP server? (Thomas Markwalder)
3. Re: How to sync a Linux secondary DHCP server?
(Sandra Schlichting)
4. Re: How to sync a Linux secondary DHCP server? (perl-list)
5. Re: How to sync a Linux secondary DHCP server?
(Sandra Schlichting)
----------------------------------------------------------------------
Message: 1
Date: Wed, 1 Aug 2018 23:07:01 +1000
From: "Glenn Satchell" <glenn.satch...@uniq.com.au>
To: "Users of ISC DHCP" <dhcp-users@lists.isc.org>
Subject: Re: How to sync a Linux secondary DHCP server?
Message-ID:
<884eed65636102b3c616fc9616531a50.squir...@mail.uniq.com.au>
Content-Type: text/plain;charset=iso-8859-1
If, for example, you added fixed reservations using omapi, then you would
need to register these same configuration with both dhcp servers.
This is the only way to ensure there is consistent configuration on both
servers.
The leases files are different on the two servers, so you can't just copy
the leases file from one server to the other.
regards,
-glenn
On Wed, August 1, 2018 12:46 am, Sten Carlsen wrote:
> 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
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
------------------------------
Message: 2
Date: Wed, 1 Aug 2018 09:18:06 -0400
From: Thomas Markwalder <tm...@isc.org>
To: dhcp-users@lists.isc.org
Subject: Re: How to sync a Linux secondary DHCP server?
Message-ID: <dd9dc3d3-e783-d603-e786-0896a7682...@isc.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Good morning:
That's correct, Glen.? When added via omapi, the reservation is tacked
on to the lease-file, with the keyword "dynamic".? This tells the server
to preserve the reservation across reboots.? The only way to convey it
the peer server is to do so either through an omapi connection to that
server,
or by adding it through some other means to the peer's configuration file.
Thank you, Glen, for your steadfast presence on the user's list. You
routinely provide valuable insight to the many questions that arrive on
the list. Your attentiveness to it is very much appreciated.? From all
of us at ISC, thank you!
Cheers,
Thomas Markwalder
ISC Software Engineering
On 08/01/2018 09:07 AM, Glenn Satchell wrote:
> If, for example, you added fixed reservations using omapi, then you would
> need to register these same configuration with both dhcp servers.
>
> This is the only way to ensure there is consistent configuration on both
> servers.
>
> The leases files are different on the two servers, so you can't just copy
> the leases file from one server to the other.
>
> regards,
> -glenn
>
> On Wed, August 1, 2018 12:46 am, Sten Carlsen wrote:
>> 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
>> _______________________________________________
>> 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
------------------------------
Message: 3
Date: Wed, 1 Aug 2018 15:22:26 +0200
From: Sandra Schlichting <littlesandr...@gmail.com>
To: dhcp-users@lists.isc.org
Subject: Re: How to sync a Linux secondary DHCP server?
Message-ID:
<caelimbnuj03mgxzsk3-h4bnyoyqra0tjn8z7cs1h-x6nbc_...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
> If, for example, you added fixed reservations using omapi, then you would
> need to register these same configuration with both dhcp servers.
>
> This is the only way to ensure there is consistent configuration on both
> servers.
>
> The leases files are different on the two servers, so you can't just copy
> the leases file from one server to the other.
My thought were to have two standalone dhcp servers. No failover, no
omapi. I would then rsync/scp the reserverations to the other when I
make changes.
Of course this means, the leases on each would be different, and that
is my question. What would happen if two identical dhcp servers with
identical reservations offer the same IP's?
The motivation would be to get a simple two dhcp server setup without
using the builtin failover.
------------------------------
Message: 4
Date: Wed, 1 Aug 2018 09:32:02 -0400 (EDT)
From: perl-list <perl-l...@network1.net>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: How to sync a Linux secondary DHCP server?
Message-ID:
<144307081.565260.1533130322448.javamail.zim...@network1.net>
Content-Type: text/plain; charset="utf-8"
You could do that as long as there are no dynamic leases (ie: everyone has a
fixed-address or similar).
You would want to make sure that you didn't have:
authoritative;
in the config file as that would cause the servers to NAK each other's traffic
(I think it still would with fixed-address).
> From: "Sandra Schlichting" <littlesandr...@gmail.com>
> To: "Users of ISC DHCP" <dhcp-users@lists.isc.org>
> Sent: Wednesday, August 1, 2018 9:22:26 AM
> Subject: Re: How to sync a Linux secondary DHCP server?
> > If, for example, you added fixed reservations using omapi, then you would
> > need to register these same configuration with both dhcp servers.
> > This is the only way to ensure there is consistent configuration on both
> > servers.
> > The leases files are different on the two servers, so you can't just copy
> > the leases file from one server to the other.
> My thought were to have two standalone dhcp servers. No failover, no
> omapi. I would then rsync/scp the reserverations to the other when I
> make changes.
> Of course this means, the leases on each would be different, and that
> is my question. What would happen if two identical dhcp servers with
> identical reservations offer the same IP's?
> The motivation would be to get a simple two dhcp server setup without
> using the builtin failover.
> _______________________________________________
> 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/20180801/3af224bf/attachment-0001.html>
------------------------------
Message: 5
Date: Wed, 1 Aug 2018 15:36:01 +0200
From: Sandra Schlichting <littlesandr...@gmail.com>
To: dhcp-users@lists.isc.org
Subject: Re: How to sync a Linux secondary DHCP server?
Message-ID:
<CAELiMBMwKARc=36pyBYnf3cj+MX8Ddp7FLp=E=tncsbisya...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
> You could do that as long as there are no dynamic leases (ie: everyone has a
> fixed-address or similar).
>
> You would want to make sure that you didn't have:
>
> authoritative;
>
> in the config file as that would cause the servers to NAK each other's
> traffic (I think it still would with fixed-address).
So if I made sure that each dhcp server served dynamic leases in
different ranges, so no overlap, would it then be a good setup?
------------------------------
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 2
******************************************
