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: failover (Glenn Satchell)
   2. Re: failover (richard lucassen)


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

Message: 1
Date: Sun, 30 Jan 2022 16:41:57 +1100
From: Glenn Satchell <glenn.satch...@uniq.com.au>
To: dhcp-users@lists.isc.org
Subject: Re: failover
Message-ID: <cece5a19173c67131cc04c3d5ab47...@uniq.com.au>
Content-Type: text/plain; charset=US-ASCII; format=flowed

Hi Richard,

That makes sense. The dh client will request the last IP address it had, 
and the DHCP server should try to allow this if possible. Without an 
existing lease file, the server now sees identical requests from either 
server, so can give them back the same address.

Now the dhclient.eth2.leases file will have the same IP address on both 
servers.

regards,
Glenn

On 2022-01-29 00:55, richard lucassen wrote:
> On Fri, 28 Jan 2022 14:44:24 +0100
> richard lucassen <mailingli...@lucassen.org> wrote:
> 
>> Why is the dhcp server providing two different addresses?
> 
> Apparently it was the client side /var/lib/dhcp/dhclient.eth2.leases
> file. I threw these away and now it works :)


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

Message: 2
Date: Sun, 30 Jan 2022 10:48:38 +0100
From: richard lucassen <mailingli...@lucassen.org>
To: dhcp-users@lists.isc.org
Subject: Re: failover
Message-ID: <20220130104838.4829d0248624c98c6d389...@lucassen.org>
Content-Type: text/plain; charset=US-ASCII

On Sun, 30 Jan 2022 16:41:57 +1100
Glenn Satchell <glenn.satch...@uniq.com.au> wrote:

Indeed, it works like a charm now :-)

> Hi Richard,
> 
> That makes sense. The dh client will request the last IP address it
> had, and the DHCP server should try to allow this if possible.
> Without an existing lease file, the server now sees identical
> requests from either server, so can give them back the same address.
> 
> Now the dhclient.eth2.leases file will have the same IP address on
> both servers.
> 
> regards,
> Glenn
> 
> On 2022-01-29 00:55, richard lucassen wrote:
> > On Fri, 28 Jan 2022 14:44:24 +0100
> > richard lucassen <mailingli...@lucassen.org> wrote:
> > 
> >> Why is the dhcp server providing two different addresses?
> > 
> > Apparently it was the client side /var/lib/dhcp/dhclient.eth2.leases
> > file. I threw these away and now it works :)
> _______________________________________________
> 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
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users


-- 
richard lucassen
http://contact.xaq.nl/


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

Subject: Digest Footer

_______________________________________________
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
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users


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

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

Reply via email to