227 lines
		
	
	
		
			6.1 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			227 lines
		
	
	
		
			6.1 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
| #
 | |
| # Configuration file for ISC dhcpd for Debian
 | |
| #
 | |
| #
 | |
| 
 | |
| 
 | |
| # ==========
 | |
| # - Global  statements
 | |
| # ==========
 | |
| 
 | |
| # option definitions common to all supported networks...
 | |
| option subnet-mask 255.255.255.0;
 | |
| option broadcast-address 192.168.100.255;
 | |
| 
 | |
| option domain-name "kanzlei-kiel.netz";
 | |
| option domain-name-servers nscache.kanzlei-kiel.netz;
 | |
| 
 | |
| default-lease-time 86400;
 | |
| max-lease-time 259200;
 | |
| 
 | |
| # 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;
 | |
| 
 | |
| # 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;
 | |
| 
 | |
| # - DHCP failover primary
 | |
| # -
 | |
| failover peer "dhcp-failover" {
 | |
|    primary; # declare this to be the primary server
 | |
|    address 192.168.100.254;
 | |
|    port 647;
 | |
|    peer address 192.168.100.10;
 | |
|    peer port 647;
 | |
|    max-response-delay 30;
 | |
|    max-unacked-updates 10;
 | |
|    mclt 360;
 | |
|    split 128;
 | |
|    load balance max seconds 3;
 | |
| }
 | |
| 
 | |
| 
 | |
| ## - DHCP failover secondary
 | |
| ## -
 | |
| #failover peer "dhcp-failover" {
 | |
| #   secondary; # declare this to be the secondary server
 | |
| #   address 192.168.100.10;
 | |
| #   port 647;
 | |
| #   peer address 192.168.100.254;
 | |
| #   peer port 647;
 | |
| #   max-response-delay 30;
 | |
| #   max-unacked-updates 10;
 | |
| #   load balance max seconds 3;
 | |
| #}
 | |
| 
 | |
| 
 | |
| shared-network lan {
 | |
| 
 | |
|    subnet 192.168.100.0 netmask 255.255.255.0 {
 | |
| 
 | |
|       # --- 192.168.100.128/26 ---
 | |
|       # network address....: 192.168.100.128
 | |
|       # Broadcast address..: 192.168.100.191
 | |
|       # netmask............: 255.255.255.192
 | |
|       # network range......: 192.168.100.129 - 192.168.100.191
 | |
|       # Usable range.......: 192.168.100.128 - 192.168.100.190
 | |
| 
 | |
|       option domain-name "kanzlei-kiel.netz";
 | |
|       option subnet-mask 255.255.255.0;
 | |
|       option broadcast-address 192.168.100.255;
 | |
|       option domain-name-servers 192.168.100.1;
 | |
|       option routers 192.168.100.254;
 | |
|       default-lease-time 86400;
 | |
|       max-lease-time 259200;
 | |
|       pool {
 | |
|          failover peer "dhcp-failover";
 | |
|          range 192.168.100.129 192.168.100.190;
 | |
|       }
 | |
|    }
 | |
| 
 | |
|    # - No dynamic range for network 172.16.101.0
 | |
|    subnet 172.16.101.0 netmask 255.255.255.0 {
 | |
|       option domain-name "kanzlei-kiel.netz";
 | |
|       option subnet-mask 255.255.255.0;
 | |
|       option broadcast-address 172.16.101.255;
 | |
|       option domain-name-servers 172.16.101.254;
 | |
|       option routers 172.16.101.254;
 | |
|       default-lease-time 86400;
 | |
|       max-lease-time 259200;
 | |
|    }
 | |
| 
 | |
| }
 | |
| 
 | |
| 
 | |
| subnet 192.168.101.0 netmask 255.255.255.0 {
 | |
| 
 | |
|    # --- 192.168.100.128/26 ---
 | |
|    # network address....: 192.168.101.128
 | |
|    # Broadcast address..: 192.168.101.191
 | |
|    # netmask............: 255.255.255.192
 | |
|    # network range......: 192.168.101.129 - 192.168.101.191
 | |
|    # Usable range.......: 192.168.101.128 - 192.168.101.190
 | |
| 
 | |
|    range 192.168.101.129 192.168.101.190;
 | |
|    option domain-name "kanzlei-kiel.netz";
 | |
|    option subnet-mask 255.255.255.0;
 | |
|    option broadcast-address 192.168.101.255;
 | |
|    option domain-name-servers 192.168.100.1;
 | |
|    option routers 192.168.101.254;
 | |
|    default-lease-time 86400;
 | |
|    max-lease-time 259200;
 | |
| 
 | |
| }
 | |
| 
 | |
| 
 | |
| # No service will be given on this subnet, but declaring it helps the 
 | |
| # DHCP server to understand the network topology.
 | |
| 
 | |
| # - No DHCP service on network 172.16.101.0
 | |
| subnet 172.16.100.0 netmask 255.255.255.0 {
 | |
| }
 | |
| 
 | |
| # ==========
 | |
| # - Hosts statements
 | |
| # ==========
 | |
| 
 | |
| # ---
 | |
| # - LAN
 | |
| # ---
 | |
| 
 | |
| include "/etc/dhcp/hosts.lan.conf";
 | |
| 
 | |
| 
 | |
| # ---
 | |
| # - W-LAN
 | |
| # ---
 | |
| 
 | |
| include "/etc/dhcp/hosts.w-lan.conf";
 | |
| 
 | |
| 
 | |
| #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;
 | |
| #  }
 | |
| #}
 |