Univention Bugzilla – Bug 37149
dhcpd fails to start: subnet & netmask != network
Last modified: 2018-04-13 13:40:08 CEST
I accidentally created a subnet 10.200.36.0/16, where # ipcalc 10.200.36.0/16 Address: 10.200.36.0 00001010.11001000. 00100100.00000000 Netmask: 255.255.0.0 = 16 11111111.11111111. 00000000.00000000 Wildcard: 0.0.255.255 00000000.00000000. 11111111.11111111 => Network: 10.200.0.0/16 00001010.11001000. 00000000.00000000 HostMin: 10.200.0.1 00001010.11001000. 00000000.00000001 HostMax: 10.200.255.254 00001010.11001000. 11111111.11111110 Broadcast: 10.200.255.255 00001010.11001000. 11111111.11111111 Hosts/Net: 65534 Class A, Private Internet dhcpd fails to start: # tail /var/log/daemon.log Dec 2 15:25:18 test35 dhcpd: subnet 10.200.36.0 netmask 255.255.0.0 Dec 2 15:25:18 test35 dhcpd: ^ Dec 2 15:25:18 test35 dhcpd: LDAP: cannot parse dhcpService entry 'cn=phahn.qa,cn=dhcp,dc=phahn,dc=qa' Dec 2 15:25:18 test35 dhcpd: Configuration file errors encountered -- exiting This happens because of subnet & netasmk != subnet. Changing /16 to /24 allows the server to start again. UMC should detect this mis-configuration and prevent generating such an invalid configuration.
(In reply to Philipp Hahn from comment #0) > UMC should detect this mis-configuration and prevent generating such an > invalid configuration. yes! we should also fix Bug #32995.
*** This bug has been marked as a duplicate of bug 44135 ***