Bug 7832 - Richtlinie für DHCP-Service führt zu Fehlern in DHCP-Pool
Richtlinie für DHCP-Service führt zu Fehlern in DHCP-Pool
Status: RESOLVED WORKSFORME
Product: UCS
Classification: Unclassified
Component: DHCP
UCS 1.3
All Linux
: P4 normal (vote)
: ---
Assigned To: Philipp Hahn
:
Depends on:
Blocks: 20222
  Show dependency treegraph
 
Reported: 2007-02-27 13:11 CET by Wolf Wiegand
Modified: 2013-11-08 16:29 CET (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
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 Wolf Wiegand univentionstaff 2007-02-27 13:11:28 CET
Siehe dazu auch #3595 und #5694:

Für einen DHCP-Service wird unter [Erlauben/Verbieten] "Duplikate: allow" gesetzt. Dies führt zu Fehlern bei DHCP-Pool-Definitionen (siehe http://forum.univention.de/viewtopic.php?p=416). Dies lässt sich jedoch nicht dadurch korrigieren, indem für das Pool- bzw. für das Subnetz-Objekt eine Richtlinie definiert wird, in dem das Attribut mit leerem Wert vererbt werden soll. In diesem Fall wird 'duplicates' ohne allow/deny in die Konfiguration geschrieben:

Jan  4 13:27:14 ugs-master150 dhcpd: Sending config line 'subnet 10.200.7.0 netmask 255.255.255.0 { filename "pxelinux.0"; option domain-name "hosts3.invalid"; option domain-nam
e-servers 10.200.7.150;  duplicates; '
Jan  4 13:27:14 ugs-master150 dhcpd: loop
Jan  4 13:27:14 ugs-master150 dhcpd: Found LDAP entry 'cn=pool,cn=10.200.7.0,cn=hosts3.invalid,cn=dhcp,dc=hosts3,dc=invalid'
Jan  4 13:27:14 ugs-master150 dhcpd: Sending config line 'pool { range 10.200.7.150 10.200.7.160; filename "pxelinux.0"; option domain-name "hosts3.invalid"; option domain-name-
servers 10.200.7.150;  duplicates; } } '
Jan  4 13:27:14 ugs-master150 dhcpd: LDAP line 11: semicolon expected.
Jan  4 13:27:14 ugs-master150 dhcpd: pool 
Jan  4 13:27:14 ugs-master150 dhcpd: ^
Jan  4 13:27:14 ugs-master150 dhcpd: LDAP line 17: expecting a parameter or declaration
Jan  4 13:27:14 ugs-master150 dhcpd: }
Jan  4 13:27:14 ugs-master150 dhcpd: ^
Jan  4 13:27:14 ugs-master150 dhcpd: loop
Jan  4 13:27:14 ugs-master150 dhcpd: Found LDAP entry 'cn=thinclient,cn=hosts3.invalid,cn=dhcp,dc=hosts3,dc=invalid'
Jan  4 13:27:14 ugs-master150 dhcpd: Skipping LDAP entry 'cn=thinclient,cn=hosts3.invalid,cn=dhcp,dc=hosts3,dc=invalid'
Jan  4 13:27:14 ugs-master150 dhcpd: loop
Jan  4 13:27:14 ugs-master150 dhcpd: LDAP line 18: unexpected end of file
Jan  4 13:27:14 ugs-master150 dhcpd: }
Jan  4 13:27:14 ugs-master150 dhcpd: ^
Jan  4 13:27:14 ugs-master150 dhcpd: loop
Jan  4 13:27:14 ugs-master150 dhcpd: Configuration file errors encountered -- exiting
Comment 1 Wolf Wiegand univentionstaff 2007-02-27 13:16:36 CET
Berichtet in Ticket 2007022310000145
Comment 2 Philipp Hahn univentionstaff 2013-11-08 16:29:26 CET

In isc-dhcp/3.1-0-0-ucs/4.1.1-P1-15+squeeze6/51_dhcp_policy.patch the function univention_parse_policies() filters out such illegal statements since UCS-3.1.

For CONTEXT_POOL univentionDhcpDuplicates has been disabled and is no longer sent.

During PT for UCS-3.2 no such error was encountered.

All other such cases will be handled through Bug #20222.