Inhaltsverzeichnis

Verwante Seiten

Allgemeines zur Konfig

Grundsätzlich gilt, alles was vor dem ersten Subnetz eingetragen ist, gilt für alle. Spezielle Optionen, welche nur für ein bestimmtes Subnetz gelten, werden innerhalb den geschweiften Klammern angegeben.

Beispielkonfigs

'/etc/dhcp3/dhcpd.conf'

Datei für Shared-Network

class "sunws" {
  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 rt-224.example.org;
  }
  subnet 10.0.29.0 netmask 255.255.255.0 {
    option routers rt-29.example.org;
  }
  pool {
    allow members of "sunws";
    range 10.17.224.10 10.17.224.250;
  }
  pool {
    deny members of "sunws";
    range 10.0.29.10 10.0.29.230;
  }
}

Datei für 5 Subnetze mit Router

ddns-update-style none;

option domain-name "sys06";
option domain-name-servers 192.168.0.1;
option routers 192.168.0.1;
option routers 192.168.1.1;
option routers 192.168.2.1;
option routers 192.168.3.1;
option routers 192.168.4.1;

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 192.168.0.0 netmask 255.255.255.0 {
}
subnet 192.168.1.0 netmask 255.255.255.0 {
	range 192.168.1.50 192.168.1.100;
}
subnet 192.168.2.0 netmask 255.255.255.0 {
	range 192.168.2.50 192.168.2.100;
}
subnet 192.168.3.0 netmask 255.255.255.0 {
	range 192.168.3.50 192.168.3.100;
}
subnet 192.168.4.0 netmask 255.255.255.0 {
	range 192.168.4.50 192.168.4.100;
}

# All Routers, because the need fixed adresses. So the listing in here
# shouln't be needet because you should make this configuration on each router.
host router0 {
  hardware ethernet 08:00:07:26:c0:a5;
  fixed-address 192.168.0.1;
}
host router0 {
  hardware ethernet 08:00:07:26:c0:a5;
  fixed-address 192.168.0.1;
}
host router1 {
  hardware ethernet 08:00:07:26:c4:15;
  fixed-address 192.168.0.10;
}
host router2 {
  hardware ethernet 08:00:07:26:f0:cf;
  fixed-address 192.168.0.20;
}
host router3 {
  hardware ethernet 08:00:07:26:64:46;
  fixed-address 192.168.0.30;
}
host router4 {
  hardware ethernet 08:00:07:26:64:af;
  fixed-address 192.168.0.40;
}

'/etc/default/dhcp3-server'

# Defaults for dhcp initscript
# sourced by /etc/init.d/dhcp
# installed at /etc/default/dhcp3-server by the maintainer scripts

#
# This is a POSIX shell fragment
#

# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
#	Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACES="eth0"

Datei für 1 Subnetz

#
# 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 "vlan4.sys06";
option domain-name-servers 192.168.4.1;
option routers 192.168.4.1;

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 192.168.4.0 netmask 255.255.255.0 {
	range 192.168.4.50 192.168.4.100;
}

#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;
#  }
#}

'/etc/default/dhcp3-server'

# Defaults for dhcp initscript
# sourced by /etc/init.d/dhcp
# installed at /etc/default/dhcp3-server by the maintainer scripts

#
# This is a POSIX shell fragment
#

# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
#	Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACES="eth0"

Fehlerquellen

No subnet declaration for eth0

Wenn der Dienst einfach nicht starten will und im Syslog 'No subnet declaration for eth0' steht, heisst das meistens, dass das Interface, hier 'eth0' noch keine IP hat.

Darum muss man zuerst eine (fixe) IP für das Interface festlegen → Link