ARCHIVE
LinuxMCE Forums
May 25, 2013, 12:07:32 am GMT-1 *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
 
   Home   Help Search Chat Login Register  
LinuxMCE Forums > LinuxMCE > Archive > Pluto Main Installation & IR codes > Dhcpd problem on new install .33
Pages: [1]
« previous next »
  Print  
Author Topic: Dhcpd problem on new install .33  (Read 1853 times)
archived
Hello, I'm new here

Posts: 0


View Profile
« on: December 01, 2005, 07:26:46 am »
Dhcpd will not start on a new install.  I have 2 nics and the dhcpd.conf is not modified from debian default.

**********************

eth0   inet addr:192.168.80.1  Bcast:192.168.80.255  Mask:255.255.255.0
 
eth1   inet addr:10.0.0.100  Bcast:10.255.255.255  Mask:255.255.255.0

**********************
syslog when starting dhcp3


Dec  1 01:10:46 dcerouter dhcpd: Internet Systems Consortium DHCP Server V3.0.1
Dec  1 01:10:46 dcerouter dhcpd: Copyright 2004 Internet Systems Consortium.
Dec  1 01:10:46 dcerouter dhcpd: All rights reserved.
Dec  1 01:10:46 dcerouter dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Dec  1 01:10:46 dcerouter dhcpd: Wrote 0 leases to leases file.
Dec  1 01:10:46 dcerouter dhcpd:
Dec  1 01:10:46 dcerouter dhcpd: No subnet declaration for eth0 (192.168.80.1).
Dec  1 01:10:46 dcerouter dhcpd: ** Ignoring requests on eth0.  If this is not what
Dec  1 01:10:46 dcerouter dhcpd:    you want, please write a subnet declaration
Dec  1 01:10:46 dcerouter dhcpd:    in your dhcpd.conf file for the network segment
Dec  1 01:10:46 dcerouter dhcpd:    to which interface eth0 is attached. **
Dec  1 01:10:46 dcerouter dhcpd:
Dec  1 01:10:46 dcerouter dhcpd:
Dec  1 01:10:46 dcerouter dhcpd: Not configured to listen on any interfaces!
dhcpd3 failed to start - check syslog for diagnostics.

*******************

dhcpd.conf


#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;
#  }
#}
#subnet 192.168.80.0 netmask 255.255.255.0 { }
dcerouter_3174:~$ cat /etc/dhcp3/dhcpd.conf
#
# Sample configuration file for ISC dhcpd for Debian
#
# $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $
#
 
# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;
 
# 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;
#  }
#}
Logged
archived
Hello, I'm new here

Posts: 0


View Profile
« Reply #1 on: December 02, 2005, 10:23:24 am »
we have 2 test systems both with 2 nics and dhcp is working fine, i can add more media directors, other devices.
on wizard, after you've been asked for password, rooms, did you press 'y' for dhcp?

Dan
Logged
archived
Hello, I'm new here

Posts: 0


View Profile
« Reply #2 on: December 02, 2005, 11:45:00 pm »
Yes i did.  I have reinstalled 4 times changing out diff brand nics. No go.  If I run /usr/pluto/bin/DHCP_config.sh it configs dhcpd.conf and everything runs great.    HuhHuh

Is there a way thru the admin to give specific ips to mac addesses(PCs)?
Logged
archived
Hello, I'm new here

Posts: 0


View Profile
« Reply #3 on: December 06, 2005, 06:23:56 pm »
That's because there's no default DHCP setting. If you add a diskless Media Director, the DHCP server will be set up correctly. This seems to be a logic flaw on my side (I wrote the script).
Logged
archived
Hello, I'm new here

Posts: 0


View Profile
« Reply #4 on: December 09, 2005, 12:22:22 am »
I've got a similar problem.  Could you clarify what you mean please as I don't understand your solution.  Do you mean set it up as a hybrid?

Rob
Logged
archived
Hello, I'm new here

Posts: 0


View Profile
« Reply #5 on: December 12, 2005, 11:50:03 am »
I mean the DHCP server won't start unless you add a diskless Media Director to it (even if you don't have a any around).
Logged
Pages: [1]
  Print  
« previous next »
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!
Pluto provided a snapshot of their forums with approximately 5,000 posts in February, 2007 when LinuxMCE branched off. Browse those forum posts in the Archive section. Those posts have been included in the search engine and can be found with keyword searches.