Date: Sun, 20 Jan 2002 17:30:47 +1100 From: "Danny" <dannyho@bigpond.net.au> To: <questions@freebsd.org> Subject: isc-dhcp 3 query Message-ID: <000a01c1a17b$ff0d36f0$c601a8c0@win2000>
next in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
Hi, I am trying to setup a DHCP server.
- My network settings are as follows:
Machine 1
OS: Windows 2000 server
IP Address: 192.168.1.198
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.196
Desktop
Machine 2
OS: FreeBSD 4.3
IP Address: 192.168.1.196
Subnet Mask: 255.255.255.0
IP Masquaring
Machine 3
OS: FreeBSD 4.3
IP Address 192.168.1.195
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.196
Samba and DHCP server
- I installed sucessflully isc-dhcp 3 from /usr/ports/net/isc-dhcp3
- Then I typed in Type: route add -host 255.255.255.255 192.168.1.196 eth0
- Then modified the /usr/local/etc/dhcpd.conf that I have add to the
attachment
- Typed in touch /var/db/dhcpd.leases
- I tried to start dhcpd my issuing the following command: "dhcpd ed0"
- Then I got the following output on the screen:
Jan 20 14:53:06 backup dhcpd: If you intend to request help from the
dhcp-server@isc.org
Jan 20 14:53:06 backup dhcpd: mailing list, please read the section on the
README about
Jan 20 14:53:06 backup dhcpd: submitting bug reports and requests for help.
Jan 20 14:53:06 backup dhcpd:
Jan 20 14:53:06 backup dhcpd: Please do not under any circumstances send
requests for
Jan 20 14:53:06 backup dhcpd: help directly to the authors of this
software - please
Jan 20 14:53:06 backup dhcpd: send them to the appropriate mailing list as
described in
Jan 20 14:53:06 backup dhcpd: the README file.
Jan 20 14:53:06 backup dhcpd:
Jan 20 14:53:06 backup dhcpd: exiting.
- But dhcpd hasnt started as seen in the
backup# ps -gax |grep dhcpd
8571 p1 S+ 0:00.01 grep dhcpd
Please help me point out what I am doing incorrectly in my dhcpd.conf file.
[-- Attachment #2 --]
# 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;
}
# Sample /etc/dhcpd.conf
# (add your comments here)
default-lease-time 600;
max-lease-time 7200;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.255;
option routers 192.168.1.196;
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.197 192.168.1.199;
}
}
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000a01c1a17b$ff0d36f0$c601a8c0>