basiluk
Posts: 3
Joined: Wed Dec 12, 2018 10:22 pm

ISC-DHCP-Server Reservations issue

Tue Jun 11, 2019 9:52 pm

Well my ISC-DHCP-Server is up and running fine, but reservations are not working. Reservations do not work, the MAC addresses are double checked, and the clients with these Mac addresses are getting dynamic addresses. Service has been stopped and restarted every time / no errors reported. I have no idea what to try next! Here is my DHCPD.conf file (Mac addresses changed).

(Wired network, Model 3 B+, no WiFi, not running any other apps)

# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#

# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers 212.159.13.49, 212.159.13.50

default-lease-time 3600;
max-lease-time 7200;

# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
authoritative;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
#log-facility local7;

# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.

#subnet 10.152.187.0 netmask 255.255.255.0 {
#}

# This is a very basic subnet declaration.

#subnet 10.254.239.0 netmask 255.255.255.224 {
# range 10.254.239.10 10.254.239.20;
# option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
#}

# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.

#subnet 10.254.239.32 netmask 255.255.255.224 {
# range dynamic-bootp 10.254.239.40 10.254.239.60;
# option broadcast-address 10.254.239.31;
# option routers rtr-239-32-1.example.org;
#}

# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
# range 10.5.5.26 10.5.5.30;
# option domain-name-servers ns1.internal.example.org;
# option domain-name "internal.example.org";
# option routers 10.5.5.1;
# option broadcast-address 10.5.5.31;
# default-lease-time 600;
# max-lease-time 7200;
#}

# Hosts which require special configuration options can be listed in
# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.

#host passacaglia {
# hardware ethernet 0:0:c0:5d:bd:95;
# filename "vmunix.passacaglia";
# server-name "toccata.example.com";
#}

# Fixed IP addresses can also be specified for hosts. These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP. Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
# hardware ethernet 08:00:07:26:c0:a5;
# fixed-address fantasia.example.com;
#}

# You can declare a class of clients and then do address allocation
# based on that. The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.

#class "foo" {
# match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
#}

#shared-network 224-29 {
# subnet 10.17.224.0 netmask 255.255.255.0 {
# option routers rtr-224.example.org;
# }
# subnet 10.0.29.0 netmask 255.255.255.0 {
# option routers rtr-29.example.org;
# }
# pool {
# allow members of "foo";
# range 10.17.224.10 10.17.224.250;
# }
# pool {
# deny members of "foo";
# range 10.0.29.10 10.0.29.230;
# }
#}

subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.205 192.168.0.244;
option subnet-mask 255.255.255.0;
option domain-name-servers 212.159.13.49, 212.159.13.50;
option routers 192.168.0.1;

host smarthings { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.210; }
host warmupshowerroom { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.211; }
host warmupbathroom { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.212; }
host nestlanding { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.235; }
host nestdownloft { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.236; }
host nestbedroom { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.237; }
host nestbreakfast { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.238; }
host nestutility { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.239; }
host nestoffice { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.240; }
host nesthall { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.241; }
host nestuploft { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.242; }
host nestlounge { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.243; }
}

dwbunger78
Posts: 3
Joined: Tue Jun 18, 2019 4:12 pm

Re: ISC-DHCP-Server Reservations issue

Wed Jun 19, 2019 3:10 pm

The only thing that I see as a potential problem is at your subnet declaration. You've got your host fixed address declarations included in the subnet declaration statement.
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.205 192.168.0.244;
option subnet-mask 255.255.255.0;
option domain-name-servers 212.159.13.49, 212.159.13.50;
option routers 192.168.0.1;

host smarthings { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.210; }
host warmupshowerroom { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.211; }
host warmupbathroom { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.212; }
host nestlanding { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.235; }
host nestdownloft { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.236; }
host nestbedroom { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.237; }
host nestbreakfast { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.238; }
host nestutility { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.239; }
host nestoffice { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.240; }
host nesthall { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.241; }
host nestuploft { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.242; }
host nestlounge { hardware ethernet 0:0:0:0:0:0; fixed-address 192.168.0.243; }
}


See on the last line you have a close bracket and no close bracket at the end of your subnet declaration? You're including all your host declarations along with your subnet declaration by doing this way. The daemon may not like that syntax. Try moving the close bracket on the very last line I have quoted to the line just under this "option routers 192.168.0.1;" then add a space in between your host declaration block.

basiluk
Posts: 3
Joined: Wed Dec 12, 2018 10:22 pm

Re: ISC-DHCP-Server Reservations issue

Thu Jun 20, 2019 2:36 pm

Thanks for that. I thought hat you could place static lease statements within a subnet but will give this a try.

Return to “General discussion”