# dhcpd.conf
#
# Simple sample configuration file for ISC dhcpd
#
# the documentation contains a more sophisticated example
#

# option definitions common to all supported networks...

# ============================================================================ #
# This dhcpd.conf file is designed to work with the private network 192.168.1. #
# in the training lab at Sysdat/MDS Cologne.                                   #
# ============================================================================ #

# The domain in this lab is artificially designated as turbolinux.koln.

option domain-name "turbolinux.koln";

# Our DNS option is commented out as we are not using DNS, but instead hosts,
# in this sample lab setup.

#option domain-name-servers nameserver.thatisanexample.com;

# More global parameters. Our subnet mask, lease time, and maximum lease time
# that the client may request.

option subnet-mask 255.255.255.0;
default-lease-time 600;
max-lease-time 7200;

# For clients that make a dhcp request we give out the following parameters, and
# the ip addresses in the 192.168.1.2 to 192.168.1.100 and 192.168.1.200 to
# 192.168.1.253. Even though we don't have a router we've reserved 192.168.1.1 
# for this purpose in case we setup a firewall at this address.

subnet 192.168.1.0 netmask 255.255.255.0 {
  range 192.168.1.2 192.168.1.100;
  range 192.168.1.200 192.168.1.253
  option broadcast-address 192.168.1.255;
  option routers 192.168.1.1;
}

# 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.

# Note that if we had moved the options "broadcast-address" and "routers" out
# to our global settings, then these would not need to be set here. But, this
# is a contrived example. For instance, in this case we can change the "routers"
# parameter, re-issue our dhcp request on workstation "platz05", and then see
# this information change on the client machine.

host platz05 {
  hardware ethernet 08:00:07:26:c0:a5;
  fixed-address 192.168.1.101;
  option broadcast-address 192.168.1.255;
  option routers 192.168.1.1;
}

# ============================================================================== #
# NOTE: On Turbolinux clients (and others) if your file /etc/dhclient.conf has   #
# any "required" fields that we do not pass back - like domain-name-servers,     #
# then you will need to change this requested parameter to be "request" vs.      #
# "required" in /etc/dhclient.conf.                                              #
# ============================================================================== #