Bug 44130 - univention-dhcp XOR dhclient
univention-dhcp XOR dhclient
Status: NEW
Product: UCS
Classification: Unclassified
Component: DHCP
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on: 27926
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-29 14:28 CEST by Philipp Hahn
Modified: 2021-04-27 11:16 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.034
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2017-03-29 14:28:24 CEST
If the server uses DHCP itself to find its IP address, it MUST NOT be a dhcp server itself. We should warn when "univention-dhcp" is installed and if interfaces any interface is configured to use DHCP. We definitely should block running the join script then.

It might be okay to get one interface configured by DHCP and to serve DHCP on some other interface (docker, VMs), but that is probably unusual, so adding an option to "--do-it-as-I-know-what-I-am-doing' or UCRV might be an option.

The scenario from Bug #27926 with two DHCP servers providing the IP address for the other is invalid, as the DHCP server MUST know its own address beforehand: It fails horribly if you turn off both servers and then try to boot both in parallel (previous lease expired).
Comment 1 Philipp Hahn univentionstaff 2021-04-27 11:16:20 CEST
Still valid with UCS 5.0-0