Bug 47398 - Misconfigured dhcp entry of a computer client
Misconfigured dhcp entry of a computer client
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Computers
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-25 12:38 CEST by Christina Scheinig
Modified: 2020-07-03 20:51 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.023
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017092121000212
Bug group (optional):
Max CVSS v3 score:


Attachments
possible misconfiguration (22.05 KB, image/png)
2018-07-25 12:38 CEST, Christina Scheinig
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christina Scheinig univentionstaff 2018-07-25 12:38:07 CEST
Created attachment 9611 [details]
possible misconfiguration

A possible misconfiguration of the computer client object leads to the following error  message in the syslog:

Jul 25 12:06:21 slave dhcpd[5646]: DHCPDISCOVER from 52:54:00:42:4d:af (Sun1) via ens3
Jul 25 12:06:21 slave dhcpd[5646]: DHCPOFFER on 10.200.42.67 to 52:54:00:42:4d:af (Sun1) via ens3
Jul 25 12:06:21 slave dhcpd[5646]: LDAP-HOST line 1: , (44): expecting IP address or hostname
Jul 25 12:06:21 slave dhcpd[5646]: fixed-address ,
Jul 25 12:06:21 slave dhcpd[5646]:                ^
Jul 25 12:06:21 slave dhcpd[5646]: LDAP-HOST line 1: , (44): expecting IP address or hostname
Jul 25 12:06:21 slave dhcpd[5646]: fixed-address ,
Jul 25 12:06:21 slave dhcpd[5646]:                ^
Jul 25 12:06:21 slave dhcpd[5646]: DHCPREQUEST for 10.200.42.67 (10.200.42.62) from 52:54:00:42:4d:af (Sun1) via ens3
Jul 25 12:06:21 slave dhcpd[5646]: DHCPACK on 10.200.42.67 to 52:54:00:42:4d:af (Sun1) via ens3

This can happen, if a client is located to two different locations of company and the customer wants to give the client in one company a fixed IP address via dhcp and a dynamic one via dhcp pool in the other company. It is possible to set an empty record via UMC which causes the error message
Comment 1 Philipp Hahn univentionstaff 2018-07-30 11:36:56 CEST
(In reply to Christina Scheinig from comment #0)
> This can happen, if a client is located to two different locations of
> company and the customer wants to give the client in one company a fixed IP
> address via dhcp and a dynamic one via dhcp pool in the other company.

AFAIK this is not supported by ISC-DHCPD: Either all static or all dynamic, but no mixture.
Comment 2 Christina Scheinig univentionstaff 2018-07-30 15:20:52 CEST
(In reply to Philipp Hahn from comment #1)
> (In reply to Christina Scheinig from comment #0)
> > This can happen, if a client is located to two different locations of
> > company and the customer wants to give the client in one company a fixed IP
> > address via dhcp and a dynamic one via dhcp pool in the other company.
> 
> AFAIK this is not supported by ISC-DHCPD: Either all static or all dynamic,
> but no mixture.

In the customer environment the configuration which is working looks like this:
root@master:~# less /var/log/dhcp-ldap-startup.log 

#DHCP Service
 subnet 10.200.42.0 netmask 255.255.255.0 {
option routers 10.200.42.1;
option domain-name "schein.ig";
option domain-name-servers 10.200.42.62;
allow unknown-clients;
pool {
range 10.200.42.66 10.200.42.69;
allow known clients;
deny unknown clients;
option routers 10.200.42.1;
option domain-name "schein.ig";
option domain-name-servers 10.200.42.62;
allow unknown-clients;
}
}
subnet 10.200.43.0 netmask 255.255.255.0 {
option routers 10.200.43.1;
option domain-name "schein.ig";
option domain-name-servers 10.200.43.60;
pool {
range 10.200.43.65 10.200.43.75;
allow known clients;
deny unknown clients;
option routers 10.200.43.1;
option domain-name "schein.ig";
option domain-name-servers 10.200.43.60;
}
}
subnet 10.202.43.0 netmask 255.255.255.0 {
pool {
range 10.202.43.5 10.202.43.9;
}
}
Comment 3 Ingo Steuwer univentionstaff 2020-07-03 20:51:50 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.