Niki Kovacs wrote:

How comes these machines never appear in dhcpd.leases ? Do the respective leases only find their way into /var/log/messages ?

I'd expect because the addresses are hard coded, there is no reason to keep track of them. the leases file from what I understand is used to determine which IPs are in use by what so dhcpd can opt to hand out IPs that are not in use. On top of that dhcpd pings the unused IPs to make sure it doesn't hand out IPs that may of been taken without authorization.

For hard coded addresses the dhcp response will be the same every time, and if you have duplicate MAC addresses on your layer 2 network you have bigger things to worry about.

nate

On 4/8/2010 9:59 AM, Niki Kovacs wrote:

Hi,

I'm running a DHCP server on my local network. I've noticed something that puzzles me. Leases are written to /var/lib/dhcpd/dhcpd.leases, but only - so it seems to me - if the address is not fixed in any way in dhcpd.conf.

Here's a few stanzas of my dhcpd.conf :

host babasse { hardware ethernet 00:0d:61:ae:6b:8f; fixed-address 192.168.1.1; option host-name "babasse"; }

host bernadette { hardware ethernet 00:0d:61:a6:e7:1e; fixed-address 192.168.1.2; option host-name "bernadette"; }

host raymonde { hardware ethernet 00:20:ed:b8:e8:ec; fixed-address 192.168.1.3; option host-name "raymonde"; }

host lifebook { hardware ethernet 00:0b:5d:46:f2:10; fixed-address 192.168.1.5; option host-name "lifebook"; }

How comes these machines never appear in dhcpd.leases ? Do the respective leases only find their way into /var/log/messages ?

fixed-addresses are permanently reserved. The leases file tracks the ones from the pool that are temporarily reserved until they expire.