Bug 29578 – dhcpd is IPv4 only but accepts IPv6 addreses

Bug 29578 - dhcpd is IPv4 only but accepts IPv6 addreses


Summary:	dhcpd is IPv4 only but accepts IPv6 addreses

Status:	REOPENED

Product:	UCS
Classification:	Unclassified
Component:	UMC - DHCP
Version:	UCS 5.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2012-12-05 19:09 CET by Philipp Hahn
Modified:	2020-07-04 15:34 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.114
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	IPv6
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Philipp Hahn

2012-12-05 19:09:27 CET

Ich hatte testweise bei einem Member-Server sowohl eine IPv4- und eine IPv6-Adresse angegeben und über den Rechner-Wizard sowohl DNS- alsauch DHCP-Einträge anlegen lassen.

Anschließend meldet der dhcpd einen Syntaxfehler:

dhcpd: DHCPDISCOVER from 52:54:00:da:b2:ce via eth0: network 192.168.123.0/24: no free leases
dhcpd: LDAP-HOST line 3: semicolon expected.
dhcpd: fixed-address 192.168.123.10, 2001:
dhcpd:                                    ^

Wenn ich das richtig in Erinnerung habe, müsste für IPv6 sowieso ein 2. "dhcpd -6" auf anderen Ports gestartet werden.

Das wird derzeit von UCS aber nicht unterstützt, von daher sollte entweder 
1. das Anlegen von IPv6-Einträgen für DHCP unterbunden werden,
2. der DHCP-Server ungültige IPvX-Adressen ignorieren.

Comment 1 Philipp Hahn

2012-12-06 07:43:35 CET

IPv6-Adressen müssen als "fixed-address6" an den dhcpd übergeben werden; "fixed-address" akzeptiert laut Dokumentation und Quelltext nur IPv4 Adressen.

Der LDAP-Patch übernimmt in isc-dhcp/server/ldap.c:630 die Werte 1:1 von LDAP-Attributen univentionFixedAddress und ipHostNumber.

Unterstützung für die IPv6-Attribute im ISC-DHCP-LDAP-Patch fehlt derzeit vollständig, von daher sollte UMC und sein Gehilfe UDM derzeit auch keine IPv6-Adressen für DHCP ins LDAP schreiben.

Comment 2 Stefan Gohmann

2017-06-16 20:37:11 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 3 Ingo Steuwer

2020-07-03 20:53:32 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.

Comment 4 Philipp Hahn

2020-07-04 15:34:44 CEST

Still broken since 8 years:

Jul  4 15:27:07 m34 dhcpd[1627]: DHCPDISCOVER from 52:54:00:81:62:4b via eth0: network 10.200.17.0/24: no free leases
Jul  4 15:27:14 m34 dhcpd[1627]: LDAP-HOST line 1: semicolon expected.
Jul  4 15:27:14 m34 dhcpd[1627]: fixed-address 2001:
Jul  4 15:27:14 m34 dhcpd[1627]:                    ^

syntax.py dhcpEntry should only allow selecting IPv4 addresses (for now).
It also shown no entry if an IPv6 is selected, saved, closed and re-opened.
Also "From known-hosts pool" from IP_syntax.AddressListEmpty is never shown to be selected.