On Sun, Nov 8, 2015 at 3:35 PM, Jeremy <open...@smartpoint.co.nz> wrote:
> No I only have one instance running.
>
> # ps aux | grep dhcp
> _dhcp 7784 0.0 0.1 756 1340 ?? Ss 9:00AM 0:00.00
> /usr/sbin/dhcpd em0
Interesting a bit that the log shows two different PID's - it changes
between 08:25:34 and 08:25:46.
=========================================
Nov 6 08:25:34 janus dhcpd[11758]: DHCPACK on 192.168.7.36 to
b4:ae:2b:2f:b6:bf via em0
Nov 6 08:25:46 janus dhcpd[24427]: Can't open f: No such file or directory
=========================================
Not sure of the "Can't open f:", besides the config file there's the
/var/db/dhcpd.leases file.
And I believe that the reserved address pool should be outside the
dynamic range.
Your:
host DocuCentre {
fixed-address 192.168.7.100;
}
Is inside the dynamic range:
range 192.168.7.32 192.168.7.127;
And for a little clean up you may want to place reservations in their
own group. Example:
===================================
subnet 192.168.7.0 netmask 255.255.255.0 {
option routers 192.168.7.1;
range 192.168.7.32 192.168.7.127;
allow-unknown-clients;
}
group {
deny unknown-clients;
default-lease-time 360000;
host DocuCentre {
fixed-address 192.168.7.200;
}
}
===================================
Notice that with the new address the DocuCentre's IP address is
outside the dynamic lease range. Plus you give those "static" devices
longer lease times.
And for an added heads up - if you're really using the 192.168.1.0/24
subnet I highly suggest changing it, as conflicts may eventually arise
with phones, tablets, laptops, etc joining your network and creating a
temporary duplicate IP issue due to the fact that subnet, and a few
others, are the default subnets on a multitude of home routers. Had
one case where a worker would take the server offline the minute she
pulled into the parking lot as her cell phone had the same IP address
as the server when it initially connected to the wifi.
Chris
