On Sat, Jul 27, 2002 at 02:36:44PM +0800, Elmer C. Claveria Jr. wrote:
> I would like to ask if there?s anyone here who can send me a template
> for dhcpd.conf and related files. I want to setup dhcp in my box as
> soon as possible.
First a number of basics are due. These are intentionally put before the
more substantial portion of my message so you'll be forced to read them.
1. I think you should be asking on the PH Linux Newbie list[1] instead.
Your question seems to be fairly newbie in nature, and that's the list
for this type of questions.
[1] http://lists.free.net.ph/mailman/listinfo/ph-linux-newbie
2. Next time, please use a more substantial subject line. Your initial
subject, '[PLUG]' was aside from being noticeably similar to the
standard list subject prefix '[plug]' which the list server generates
did very little in allowing us to get a glimpse of what your message was
all about by scanning the message headers in the folder indices.
Now to answer your question:
Your dhcp server package should have come with a sample configuration
file together with comprehensive documentation on how to set it up in at
least the dhcpd.conf(5) manual page. Aside from it being very "slavey"
of us if we whipped up a dhcpd.conf for your configuration, it would be
pretty difficult for us to figure out what your needs would be given the
brevity of your message. It's also a generally good idea for you to know
the configurations that you work out on your box.
That being said I am attaching a fairly small file, which is the example
dhcpd.conf file on the dhcp3-server Debian package. I'm sure you can
figure things out with the help of the dhcpd.conf(5) manual page. If
there's a particular part you can't figure out, please feel free to ask
specific questions on the PH Linux Newbie list, so we can help you out
there.
--> Jijo
--
Federico Sevilla III : <http://jijo.free.net.ph/>
Network Administrator : The Leather Collection, Inc.
GnuPG Key ID : 0x93B746BE
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#
# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;
default-lease-time 600;
max-lease-time 7200;
# 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.fugue.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.fugue.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;
}
}
