Univention Bugzilla – Bug 23402
Einstellung im UDM führt zu DHCPD Fehlermeldung
Last modified: 2018-04-13 13:28:16 CEST
Aufgefallen an Ticket#: 2011080910002901 Authorative=Yes am DHCP-Service Es ist möglich, durch bspw. eine Richtlinie am DHCP Container im UDM Werte zu setzen, die zu Fehlermeldungen des DHCP Dienstes führen. Aug 18 06:30:53 qamaster dhcpd: Searching for Host dhcpHWAddress=ethernet 52:54:00:10:5c:63 in LDAP tree cn=dhcp,dc=univention,dc=qa Aug 18 06:30:53 qamaster dhcpd: DHCPDISCOVER from 52:54:00:10:5c:63 via eth0: network univshared: no free leases Aug 18 06:30:54 qamaster dhcpd: Searching for Host dhcpHWAddress=ethernet 52:54:00:0f:43:c2 in LDAP tree cn=dhcp,dc=univention,dc=qa Aug 18 06:30:54 qamaster dhcpd: Found Host: LDAP entry is cn=testgo,cn=univention.qa,cn=dhcp,dc=univention,dc=qa Aug 18 06:30:54 qamaster dhcpd: Sending the following options: 'filename "pxelinux.0"; option domain-name "univention.qa"; option domain-name-servers 10.200.14.20; authoritative; boot-unknown-clients false; fixed-address 10.200.16.40; ' Aug 18 06:30:54 qamaster dhcpd: LDAP-HOST line 4: authority makes no sense here. Aug 18 06:30:54 qamaster dhcpd: authoritative; Aug 18 06:30:54 qamaster dhcpd: ^ Aug 18 06:30:54 qamaster dhcpd: DHCPDISCOVER from 52:54:00:0f:43:c2 via eth0 Aug 18 06:30:54 qamaster dhcpd: DHCPOFFER on 10.200.16.40 to 52:54:00:0f:43:c2 via eth0 Aug 18 06:30:57 qamaster dhcpd: Searching for Host dhcpHWAddress=ethernet 52:54:00:0f:43:c2 in LDAP tree cn=dhcp,dc=univention,dc=qa Aug 18 06:30:57 qamaster dhcpd: Found Host: LDAP entry is cn=testgo,cn=univention.qa,cn=dhcp,dc=univention,dc=qa Aug 18 06:30:57 qamaster dhcpd: Sending the following options: 'filename "pxelinux.0"; option domain-name "univention.qa"; option domain-name-servers 10.200.14.20; authoritative; boot-unknown-clients false; fixed-address 10.200.16.40; ' Aug 18 06:30:57 qamaster dhcpd: LDAP-HOST line 4: authority makes no sense here. Aug 18 06:30:57 qamaster dhcpd: authoritative; Aug 18 06:30:57 qamaster dhcpd: ^ Aug 18 06:30:57 qamaster dhcpd: DHCPREQUEST for 10.200.16.40 (10.200.14.20) from 52:54:00:0f:43:c2 via eth0 Aug 18 06:30:57 qamaster dhcpd: DHCPACK on 10.200.16.40 to 52:54:00:0f:43:c2 via eth0 Aug 18 06:30:57 qamaster in.tftpd[7072]: connect from 10.200.16.40 (10.200.16.40) Folgende Richtlinie ist gesetzt: root@qamaster:~$ udm policies/dhcp_statements list DN: cn=univention.qa,cn=statements,cn=dhcp,cn=policies,dc=univention,dc=qa ARG: None serverIdentifier: None name: univention.qa emptyAttributes: None authoritative: yes boot-unknown-clients: false prohibitedObjectClasses: None requiredObjectClasses: None filler: None _view_referencing_objects: None pingCheck: None fixedAttributes: None serverName: None getLeaseHostnames: None
Das kann ich auch mit UCS@school 3.0-2 nachstellen.
30_policy.quilt: 376 + if (context & (CONTEXT_SHARED_NETWORK | CONTEXT_SUBNET | CONTEXT_SERVICE)) 377 + univention_parse_policy(phandle, "univentionDhcpAuthoritative", "authoritative", "not", 0, STATEMENT_INSERTIFNO_REVERSE, buf, bufsize); *** This bug has been marked as a duplicate of bug 20222 ***