Aw: Re: Re: ISC dhcp assigns ip addresses outside dynamic range

[perl-list]

I realize that this is possible, but it won't be passed to the failover peer in such a case. You have to use OMAPI to add it to both servers. It seems that this lease was handed out dynamically due to the log line about difficulty passing it to the failover peer. 

' Jul 5 13:14:35 a-rl-dhcp1 dhcpd[20145]: bind update on 10.91.120.80 from dhcp-failover rejected: unknown IP address' 

> From: "Christian Kratzer" <ck-lists at cksoft.de>
> To: "Users of ISC DHCP" <dhcp-users at lists.isc.org>
> Sent: Friday, July 6, 2018 1:25:31 AM
> Subject: Re: Aw: Re: Re: ISC dhcp assigns ip addresses outside dynamic range

> Hi,

> On Thu, 5 Jul 2018, perl-list wrote:

> > This line:

>> Jul 5 13:14:35 a-rl-dhcp1 dhcpd[20145]: bind update on 10.91.120.80 from
> > dhcp-failover rejected: unknown IP address
>> Makes it seem like it was handed out dynamically. Static assignments with
>> fixed-address are not written to a lease file. They are also not sent to the
> > peer.

> There is no lease for a static reservation but you can provision static
> reservations to the lease file by omapi.

> You will find things like this in the lease file in those cases

> host foo {
> dynamic;
> host-identifier option agent.circuit-id "foo";
> fixed-address 192.0.2.100;
> }

> host bar {
> dynamic;
> hardware ethernet 00:50:00:00:00:01;
> fixed-address 192.0.2.101;
> }

> I have a patch that also allowes provisioning of hosts with host-identifier via
> omapi.

> Propably not the case here but I would still want to check.

> Greetings
> Christian


> > I'm not sure what is going on here.

> >> From: "Frank Ulherr" <dhcp at ulherr.eu>
> >> To: ck at cksoft.de, "Users of ISC DHCP" <dhcp-users at lists.isc.org>
> >> Sent: Thursday, July 5, 2018 8:10:22 AM
> >> Subject: Aw: Re: Re: ISC dhcp assigns ip addresses outside dynamic range

> >> Hi!

> >> * "Christian Kratzer" <ck-lists at cksoft.de> wrote:

> >>> oh now there is also redunancy involved so you have two config files and two
> >>> lease files.

> >>> If you want help please do as asked previously

> >>> 1. post logs of the transaction

> >>> 2. post both configs that were effective at time of the transaction

> >>> 3. check both lease files for the ip and the mac at the time of the transaction
> >>> for entries with the mac or the ip

> >>> The more you obfuscate the less anybody can help you.


> >> Attached the config and log files.

> >> 10.91.120.80 is reserved and is excludes from the dynamic range.
> >> dhcpd.conf is the same on the first and second server (dhcpd1.conf)
> >> The dhcpd.leases file an the second server does not contain the lease.

> >> Regards,
> >> Frank
> >> _______________________________________________
> >> dhcp-users mailing list
> >> dhcp-users at lists.isc.org
> >> https://lists.isc.org/mailman/listinfo/dhcp-users

> --
> Christian Kratzer CK Software GmbH
> Email: ck at cksoft.de Wildberger Weg 24/2
> Phone: +49 7032 893 997 - 0 D-71126 Gaeufelden
> Fax: +49 7032 893 997 - 9 HRB 245288, Amtsgericht Stuttgart
> Mobile: +49 171 1947 843 Geschaeftsfuehrer: Christian Kratzer
> Web: http://www.cksoft.de/
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at 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/20180706/754cce8e/attachment.html>