Re: anyone have an example CMU dhcpd.conf?

[Shane Turner <[e-mail]>]

Somewhere in the ether David M. Meyer 503/346-1747 said:
> 	Does anyone have an example CMU dhcpd.conf they would be
> 	willing to share? 
> 
> 	Thanks
> 
> 	Dave

Here's a sample copy of the one we are using at Dalhousie.
I'm still not too sure about some things, such as the  "roaming" tag for
a network.  I think that since we are not using dynamic bootp here, that
we could probably substitute "dhcp" for "both" but I haven't had a chance
to test it out.

Ciao,
	Shane
--- CUT HERE ---
# /etc/dhcpd.conf: configuration for dhcp part of dhcp/bootp server
#
# when this number of bindings is in the queue for saving to disk, force a flush
flushitems 15

# interval in seconds to flush bindings to disk
flushinterval 1800

# interval in seconds to garbage collect
#gcinterval 900

# We shortened the garbage collect interval to 5 minutes because it seemed
# that the server would still give a client the lease it had before, even
# if that lease had expired, if the garbage collection hadn't been done yet
gcinterval 300

# network <name> <network> <mask> <access> [<relay agent> <relay agent's mask>]
# Where access can be the following seperated by |'s:
# 	registered 
#   dhcp or bootp or both
#   roaming
#
# The set of ip addresses which are actually used for dynamic allocation, must
# be in the bootptab file and have the 'dy' flag set. e.g.
# suzie.net.cmu.edu:ip=128.2.10.8:sm=255.255.255.0:dy:tc=whatever:
# 
# Only machines with the 'ro' option can access dynamic ip's with 'roaming'
# access e.g.
# mylaptop.net.cmu.edu:ht=ethernet:ha=00AA00BB00CC:ro:tc=whatever

# I don't think that we are going to need dynamic addresses on .1
#network subnet001 129.173.1.0   255.255.255.0 registered|both
network subnet002 129.173.2.0   255.255.255.0 registered|both
network subnet030 129.173.30.0  255.255.255.0 registered|both
network subnet070 129.173.70.0  255.255.255.0 registered|both
network subnet072 129.173.72.0  255.255.255.0 registered|both
# Subnet 131 was being used for testing
#network subnet131 129.173.131.0 255.255.255.0 registered|both

# gateway <ip address> <mask> [<network name> <network name>.....]
# 	This statment defines a relay agent and the network connected to the relay
#   agent. 
#   Specifiying the pool of dynamic ip adddresses that can exist behind this
#   relay agent is optional

#gateway 128.2.10.254 255.255.255.128 subnet10-hi

# 128.2.5.61 is the ip address of the DHCP server which is reading this config
# file. We only want to respond to machines which belong to this network

gateway 129.173.1.10  255.255.255.0
gateway 129.173.2.1   255.255.255.0 subnet002
gateway 129.173.30.1  255.255.255.0 subnet030
gateway 129.173.70.1  255.255.255.0 subnet070
gateway 129.173.72.1  255.255.255.0 subnet072
#gateway 129.173.131.1 255.255.255.0 subnet131


-- 
Shane Turner - NOC Assistant - [e-mail] - 902-494-1873
Dalhousie University, Halifax, Nova Scotia, Canada