|
|
12
|
|
Hallo,
our dhcpd.conf contains the following section:
subnet 10.91.120.0 netmask 255.255.255.0 {
option routers 10.91.120.254;
option domain-name-servers 8.8.8.8;
pool {
failover peer "dhcp-failover";
deny dynamic bootp clients;
range 10.91.120.94 10.91.120.94;
range 10.91.120.106 10.91.120.106;
range 10.91.120.108 10.91.120.108;
range 10.91.120.111 10.91.120.111;
range 10.91.120.113 10.91.120.114;
...
Unfortunately the ip address 10.91.120.7 is assigned to a client.
Any ideas?
Frank
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
Hi,
On Wed, 4 Jul 2018, Frank Ulherr wrote:
> our dhcpd.conf contains the following section:
>
> subnet 10.91.120.0 netmask 255.255.255.0 {
> option routers 10.91.120.254;
> option domain-name-servers 8.8.8.8;
> pool {
> failover peer "dhcp-failover";
> deny dynamic bootp clients;
> range 10.91.120.94 10.91.120.94;
> range 10.91.120.106 10.91.120.106;
> range 10.91.120.108 10.91.120.108;
> range 10.91.120.111 10.91.120.111;
> range 10.91.120.113 10.91.120.114;
> ...
>
> Unfortunately the ip address 10.91.120.7 is assigned to a client.
most propably you have a host reservation for 10.91.120.7 either in your configuration file or in the lease file.
Greetings
Christian
--
Christian Kratzer CK Software GmbH
Email: [hidden email] 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
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
On Wed, July 4, 2018 11:45 pm, Christian Kratzer wrote:
> Hi,
>
> On Wed, 4 Jul 2018, Frank Ulherr wrote:
>> our dhcpd.conf contains the following section:
>>
>> subnet 10.91.120.0 netmask 255.255.255.0 {
>> option routers 10.91.120.254;
>> option domain-name-servers 8.8.8.8;
>> pool {
>> failover peer "dhcp-failover";
>> deny dynamic bootp clients;
>> range 10.91.120.94 10.91.120.94;
>> range 10.91.120.106 10.91.120.106;
>> range 10.91.120.108 10.91.120.108;
>> range 10.91.120.111 10.91.120.111;
>> range 10.91.120.113 10.91.120.114;
>> ...
>>
>> Unfortunately the ip address 10.91.120.7 is assigned to a client.
>
> most propably you have a host reservation for 10.91.120.7 either in your
> configuration file or in the lease file.
>
> Greetings
> Christian
>
What is in the dhcp log files for this request? Does the client already
have the address and ask for an extension, or does it go through the
DHCPDISCOVER and get assigned the address?
regards,
-glenn
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
Hallo,
> Hi,
>
> On Wed, 4 Jul 2018, Frank Ulherr wrote:
> > our dhcpd.conf contains the following section:
> >
> > subnet 10.91.120.0 netmask 255.255.255.0 {
> > option routers 10.91.120.254;
> > option domain-name-servers 8.8.8.8;
> > pool {
> > failover peer "dhcp-failover";
> > deny dynamic bootp clients;
> > range 10.91.120.94 10.91.120.94;
> > range 10.91.120.106 10.91.120.106;
> > range 10.91.120.108 10.91.120.108;
> > range 10.91.120.111 10.91.120.111;
> > range 10.91.120.113 10.91.120.114;
> > ...
> >
> > Unfortunately the ip address 10.91.120.7 is assigned to a client.
>
> most propably you have a host reservation for 10.91.120.7 either in your configuration file or in the lease file.
There is a reservation for that ip address:
host a.lraroth.de-005056b22f2c {
hardware ethernet 00:50:56:b2:2f:2c;
fixed-address 10.91.120.7;
option host-name "a";
}
But the ip address is assigned to a different mac address.
Frank
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
Hallo,
Gesendet: Mittwoch, 04. Juli 2018 um 15:51 Uhr
Von: "Glenn Satchell" < [hidden email]>
An: "Users of ISC DHCP" < [hidden email]>
Betreff: Re: ISC dhcp assigns ip addresses outside dynamic range
On Wed, July 4, 2018 11:45 pm, Christian Kratzer wrote:
> Hi,
>
> On Wed, 4 Jul 2018, Frank Ulherr wrote:
>> our dhcpd.conf contains the following section:
>>
>> subnet 10.91.120.0 netmask 255.255.255.0 {
>> option routers 10.91.120.254;
>> option domain-name-servers 8.8.8.8;
>> pool {
>> failover peer "dhcp-failover";
>> deny dynamic bootp clients;
>> range 10.91.120.94 10.91.120.94;
>> range 10.91.120.106 10.91.120.106;
>> range 10.91.120.108 10.91.120.108;
>> range 10.91.120.111 10.91.120.111;
>> range 10.91.120.113 10.91.120.114;
>> ...
>>
>> Unfortunately the ip address 10.91.120.7 is assigned to a client.
>
> most propably you have a host reservation for 10.91.120.7 either in your
> configuration file or in the lease file.
>
> Greetings
> Christian
>
What is in the dhcp log files for this request? Does the client already
have the address and ask for an extension, or does it go through the
DHCPDISCOVER and get assigned the address?
It does a DHCPDISCOVER.
Frank
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
On Wed, Jul 04, 2018 at 03:54:15PM +0200, Frank Ulherr wrote:
> Hallo,
>
> > Hi,
> >
> > On Wed, 4 Jul 2018, Frank Ulherr wrote:
> > > our dhcpd.conf contains the following section:
> > >
> > > subnet 10.91.120.0 netmask 255.255.255.0 {
> > > option routers 10.91.120.254;
> > > option domain-name-servers 8.8.8.8;
> > > pool {
> > > failover peer "dhcp-failover";
> > > deny dynamic bootp clients;
> > > range 10.91.120.94 10.91.120.94;
> > > range 10.91.120.106 10.91.120.106;
> > > range 10.91.120.108 10.91.120.108;
> > > range 10.91.120.111 10.91.120.111;
> > > range 10.91.120.113 10.91.120.114;
> > > ...
> > >
> > > Unfortunately the ip address 10.91.120.7 is assigned to a client.
> >
> > most propably you have a host reservation for 10.91.120.7 either in your configuration file or in the lease file.
>
> There is a reservation for that ip address:
>
> host a.lraroth.de-005056b22f2c {
> hardware ethernet 00:50:56:b2:2f:2c;
> fixed-address 10.91.120.7;
> option host-name "a";
> }
>
> But the ip address is assigned to a different mac address.
Maybe the VM was cloned from an image that has the same MAC or client-id stored.
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
Hi!
> "Chuck Anderson" < [hidden email]>
> > There is a reservation for that ip address:
> >
> > host a.lraroth.de-005056b22f2c {
> >hardware ethernet 00:50:56:b2:2f:2c;
> > fixed-address 10.91.120.7;
> > option host-name "a";
> >}
>
> > But the ip address is assigned to a different mac address.
> Maybe the VM was cloned from an image that has the same MAC or client-id
No, that is not the case.
Frank
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
Hi!
What we are doung is the following:
First the subnet looks like that:
subnet 10.91.120.0 netmask 255.255.255.0 {
option routers 10.91.120.254;
option domain-name-servers 8.8.8.8;
pool {
failover peer "dhcp-failover";
deny dynamic bootp clients;
range 10.91.120.2 10.91.120.252
}
When we want t reserve an ip address, we add the host block:
host a.lraroth.de-005056b22f2c {
hardware ethernet 00:50:56:b2:2f:2c;
fixed-address 10.91.120.7;
}
...and change the range to:
subnet 10.91.120.0 netmask 255.255.255.0 {
option routers 10.91.120.254;
option domain-name-servers 8.8.8.8;
pool {
failover peer "dhcp-failover";
deny dynamic bootp clients;
range 10.91.120.2 10.91.120.6;
range 10.91.120.8 10.91.120.252;
}
Could that be a problem?
Frank
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
Hi,
On Wed, 4 Jul 2018, Frank Ulherr wrote:
> Hi!
>
>
> What we are doung is the following:
<snipp/>
> Could that be a problem?
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.
Greetings
Christian
--
Christian Kratzer CK Software GmbH
Email: [hidden email] 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
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
Hi!
* "Christian Kratzer" < [hidden email]> 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
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
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.
I'm not sure what is going on here.
Hi!
* "Christian Kratzer" <[hidden email]> 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
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
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" < [hidden email]>
>> To: [hidden email], "Users of ISC DHCP" < [hidden email]>
>> Sent: Thursday, July 5, 2018 8:10:22 AM
>> Subject: Aw: Re: Re: ISC dhcp assigns ip addresses outside dynamic range
>
>> Hi!
>
>> * "Christian Kratzer" < [hidden email]> 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
>> [hidden email]
>> https://lists.isc.org/mailman/listinfo/dhcp-users--
Christian Kratzer CK Software GmbH
Email: [hidden email] 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
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
Hi!
From: "Christian Kratzer" < [hidden email]>
> > 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;
> }
But if I restart the daemon, those changes are lost, aren't they? We have lots of reservations...
Regards,
Frank
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
Hi Frank,
On Fri, 6 Jul 2018, Frank Ulherr wrote:
>> 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;
>> }
>
> But if I restart the daemon, those changes are lost, aren't they? We have lots of reservations...
no. That is the purpose for them to be in the lease file so that they are not lost on restarts.
Greetings
Christian
--
Christian Kratzer CK Software GmbH
Email: [hidden email] 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
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
Hi!
from: "Christian Kratzer" < [hidden email]>
> You originally said that you are getting an ip out of the dynamic range for a host you have a reservatio for.
No, I said, I am getting an ip address, that is not in the dynamic range.
The ip address I am getting is reserved for a different host and is not overlapping with the dynamic range.
> Now you are saying that a different host is getting a static ip.
As said, a new host is getting a static ip. But that host does have a different mac address.
Regards
Frank
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
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" <[hidden email]>
To: "Users of ISC DHCP" <[hidden email]>
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" < [hidden email]> >> To: [hidden email], "Users of ISC DHCP" < [hidden email]> >> Sent: Thursday, July 5, 2018 8:10:22 AM >> Subject: Aw: Re: Re: ISC dhcp assigns ip addresses outside dynamic range > >> Hi! > >> * "Christian Kratzer" < [hidden email]> 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 >> [hidden email]>> https://lists.isc.org/mailman/listinfo/dhcp-users
--
Christian Kratzer CK Software GmbH
Email: [hidden email] 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
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
I just had a thought ... is it possible that dhcpd has not been restarted since the config file has been modified? Perhaps the running config is not the same as that on the disk and 10.91.120.80 is still part of a dynamic range?
From: "Frank Ulherr" <[hidden email]>
To: "ck" <[hidden email]>, "Users of ISC DHCP" <[hidden email]>
Sent: Friday, July 6, 2018 8:42:21 AM
Subject: Aw: Re: Re: Re: Re: Re: Re: ISC dhcp assigns ip addresses outside dynamic range
Hi!
from: "Christian Kratzer" <[hidden email]>
> You originally said that you are getting an ip out of the dynamic range for a host you have a reservatio for.
No, I said, I am getting an ip address, that is not in the dynamic range.
The ip address I am getting is reserved for a different host and is not overlapping with the dynamic range.
> Now you are saying that a different host is getting a static ip.
As said, a new host is getting a static ip. But that host does have a different mac address.
Regards
Frank
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
Hi! I just had a thought ... is it possible that dhcpd has not been restarted since the config file has been modified? Perhaps the running config is not the same as that on the disk and 10.91.120.80 is still part of a dynamic range?
No, we change the configuration the first server, restart it. Then we copy the configuration to the second server and restart it.
This problem did not occur the first time.
Regards, Frank _______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
Hi! 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.
The primary dhcp hands out an ip address, which is not in its dynamic range. Then it sends this information to the secondary dhcp, which complains. That is weird, because that is one of the primary purpose of a dhcp: Hand out ips correctly.
'Jul 5 13:14:35 a-rl-dhcp1 dhcpd[20145]: bind update on 10.91.120.80 from dhcp-failover rejected: unknown IP address'
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
In my experience, when an IP has been assigned by 'fixed-address' inside a host statement (OMAPI or dhcpd.conf) it does NOT keep a lease for it in dhcpd.leases. It does NOT inform the failover peer. If you attempt to release such address, the DHCP server will log that the lease is not found.
Thats what is telling me that this was handed out dynamically. Thats why i wondered about restarting after config change. Its like one of them has it included in the range and the other does not hence why it is saying "unknown IP address".
From: "Frank Ulherr" <[hidden email]>
To: "Users of ISC DHCP" <[hidden email]>
Sent: Friday, July 6, 2018 1:21:27 PM
Subject: Re: Aw: Re: Re: ISC dhcp assigns ip addresses outside dynamic range
Hi! 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.
The primary dhcp hands out an ip address, which is not in its dynamic range. Then it sends this information to the secondary dhcp, which complains. That is weird, because that is one of the primary purpose of a dhcp: Hand out ips correctly.
'Jul 5 13:14:35 a-rl-dhcp1 dhcpd[20145]: bind update on 10.91.120.80 from dhcp-failover rejected: unknown IP address'
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
12
|
Locked
dhcpd1.conf.txt (1K)