On Sun, 08 Sep 2002 22:01:46 +1200
Vik Olliver <[EMAIL PROTECTED]> wrote:
> I'm truing to run the DHCP daemon dhcpcd on my RH7.3 box. I have two
Have you told dhcpd about both of your network interfaces ?
> ntework cards. When I run dhcpcd it kills off the eth0 device as if
> I'd done an "ifdown eth0"
>
> Any one know what causes this and how I might fix it?
All I know is that dhcpd likes to know about all the interfaces on a
machine, even if you only want it to listen on one interface.
Regs,
Andrew.
p.s. I'm typing this on a multi-homed box, it runs dhcpd fine
here is my edited dhcpd.conf file, it's for dynamic DNS/DHCP
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#
# option definitions common to all supported networks...
option domain-name "andrew.kemmy";
#option domain-name-servers ns1.example.org, ns2.example.org;
ddns-update-style interim;
ddns-domainname "andrew.kemmy";
#ddns-rev-domainname "100.168.192.in-addr.arpa";
#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 192.168.100.0 netmask 255.255.255.0 {
range 192.168.100.230 192.168.100.235;
option domain-name-servers 192.168.100.2;
option domain-name "andrew.kemmy";
option routers 192.168.100.3;
option broadcast-address 192.168.100.0;
default-lease-time 60;
max-lease-time 720;
}
# 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;
# }
#}
#key transactionkey1 {
# algorithm hmac-md5;
# secret "1transactionkey*****************";
# };
#key transactionkey2 {
# algorithm hmac-md5;
# secret "2transactionkey***************************";
# };
#acl key_tsig {key transactionkey1; key transactionkey2;
#};
key rndc_key {
algorithm hmac-md5;
secret
"J5lVcpt+rdSonBcpbgaIO564SztFxubsfBqdu+oTgfL***************************
***************************
==";
};
zone andrew.kemmy. {
primary 127.0.0.1;
key rndc_key;
}
zone 100.168.192.in-addr.arpa. {
primary 127.0.0.1;
key rndc_key;
}
--
