uname -a:
Linux ap-m-controller 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) i686 GNU/Linuxifconfig:
eth0 Link encap:Ethernet HWaddr 00:1b:fc:0c:bc:ee
inet addr:192.168.9.2 Bcast:192.168.9.255 Mask:255.255.255.0
inet6 addr: fe80::21b:fcff:fe0c:bcee/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1672 errors:0 dropped:0 overruns:0 frame:0
TX packets:1476 errors:0 dropped:0 overruns:0 carrier:2
collisions:0 txqueuelen:1000
RX bytes:434663 (424.4 KiB) TX bytes:544566 (531.8 KiB)
Memory:dffc0000-e0000000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:2604 errors:0 dropped:0 overruns:0 frame:0
TX packets:2604 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:712457 (695.7 KiB) TX bytes:712457 (695.7 KiB)
Конфиг dhcpd:
ddns-update-style none;
log-facility local7;
subnet 192.168.9.0 netmask 255.255.255.0 {
authoritative;
range 192.168.9.50 192.168.9.254;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.9.255;
option routers 192.168.9.1;
option domain-name-servers 192.168.9.1;
default-lease-time 7200;
max-lease-time 28800;
}
В /etc/default/isc-dhcp-server:
INTERFACES="eth0"
При перезагрузке dhcpd не стартует, валит в syslog:
Mar 2 12:49:49 ap-m-controller dhcpd: No subnet declaration for eth0 (no IPv4 addresses).
Mar 2 12:49:49 ap-m-controller dhcpd: ** Ignoring requests on eth0. If this is not what
Mar 2 12:49:49 ap-m-controller dhcpd: you want, please write a subnet declaration
Mar 2 12:49:49 ap-m-controller dhcpd: in your dhcpd.conf file for the network segment
Mar 2 12:49:49 ap-m-controller dhcpd: to which interface eth0 is attached. **
Mar 2 12:49:49 ap-m-controller dhcpd:
Mar 2 12:49:49 ap-m-controller dhcpd:
Mar 2 12:49:49 ap-m-controller dhcpd: Not configured to listen on any interfaces!
Mar 2 12:49:49 ap-m-controller dhcpd:
Mar 2 12:49:49 ap-m-controller dhcpd: If you think you have received this message due to a bug rather
Mar 2 12:49:49 ap-m-controller dhcpd: than a configuration issue please read the section on submitting
Mar 2 12:49:49 ap-m-controller dhcpd: bugs on either our web page at www.isc.org or in the README file
Mar 2 12:49:49 ap-m-controller dhcpd: before submitting a bug. These pages explain the proper
Mar 2 12:49:49 ap-m-controller dhcpd: process and the information we find helpful for debugging..
Mar 2 12:49:49 ap-m-controller dhcpd:
Mar 2 12:49:49 ap-m-controller dhcpd: exiting.
Mar 2 12:49:51 ap-m-controller isc-dhcp-server[448]: Starting ISC DHCP server: dhcpdcheck syslog for diagnostics. ... failed!
Mar 2 12:49:51 ap-m-controller isc-dhcp-server[448]: failed!
Mar 2 12:49:51 ap-m-controller systemd[1]: isc-dhcp-server.service: control process exited, code=exited status=1
Mar 2 12:49:51 ap-m-controller systemd[1]: Unit isc-dhcp-server.service entered failed state.
Если запустить руками через # service isc-dhcp-server start - запускается прекрасно без ругани в логах.
На аналогичной машине с аналогичным конфигом и теми же версиями ОС, всего софта и dhcpd все работает штатно.
