228 lines
		
	
	
		
			6.3 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			228 lines
		
	
	
		
			6.3 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
| #
 | |
| # Sample configuration file for ISC dhcpd for Debian
 | |
| #
 | |
| #
 | |
| 
 | |
| # 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 subnet-mask 255.255.255.0;
 | |
| option broadcast-address 192.168.102.255;
 | |
| 
 | |
| 
 | |
| option domain-name "flr.netz";
 | |
| option domain-name-servers nscache.flr.netz;
 | |
| #option domain-name "example.org";
 | |
| #option domain-name-servers ns1.example.org, ns2.example.org;
 | |
| option routers gw-flr.flr.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;
 | |
| 
 | |
| # No service will be given on this subnet, but declaring it helps the 
 | |
| # DHCP server to understand the network topology.
 | |
| subnet 192.168.102.0 netmask 255.255.255.0 {
 | |
| 
 | |
|    # --- 192.168.102.160/27 ---
 | |
|    # network address....: 192.168.102.160
 | |
|    # Broadcast address..: 192.168.102.191
 | |
|    # netmask............: 255.255.255.224
 | |
|    # network range......: 192.168.102.160 - 192.168.102.191
 | |
|    # Usable range.......: 192.168.102.161 - 192.168.102.190
 | |
| 
 | |
|    range 192.168.102.161 192.168.102.190;
 | |
|    option domain-name "flr.netz";
 | |
|    option domain-name-servers nscache.flr.netz;
 | |
|    option subnet-mask 255.255.255.0;
 | |
|    option broadcast-address 192.168.102.255;
 | |
|    option routers gw-flr.flr.netz;
 | |
| 
 | |
| }
 | |
| 
 | |
| host file-flr {
 | |
|    hardware ethernet 00:25:90:0b:77:90;
 | |
|    fixed-address file-flr.flr.netz ;
 | |
| }
 | |
| 
 | |
| host file-ipmi {
 | |
|    hardware ethernet 00:25:90:0b:7f:3d;
 | |
|    fixed-address file-ipmi.flr.netz ;
 | |
| }
 | |
| 
 | |
| host mfc-9142cdn.flr.netz {
 | |
|    hardware ethernet 30:05:5c:74:6b:c0;
 | |
|    fixed-address mfc-9142cdn.flr.netz ;
 | |
| }
 | |
| 
 | |
| host pcbuero1 {
 | |
|    # - on chipset LAN
 | |
|    #hardware ethernet 00:1D:7D:E5:42:69;
 | |
|    # - Intel PRO/1000 GT
 | |
|    hardware ethernet 90:e2:ba:0c:bb:fb;
 | |
|    fixed-address pcbuero1.flr.netz ;
 | |
| }
 | |
| 
 | |
| host pcbuero2 {
 | |
|    # - on chipset LAN
 | |
|    #hardware ethernet 00:1d:7d:e5:3f:9f;
 | |
|    # - Intel PRO/1000 GT
 | |
|    hardware ethernet 90:e2:ba:0c:bc:0e;
 | |
|    fixed-address pcbuero2.flr.netz ;
 | |
| }
 | |
| 
 | |
| host pcbuero3 {
 | |
|    hardware ethernet 80:ee:73:b9:8a:d6;
 | |
|    fixed-address pcbuero3.flr.netz ;
 | |
| }
 | |
| 
 | |
| host ivana-Laptop {
 | |
|    # - on chipset WLAN
 | |
|    hardware ethernet 5c:51:4f:ff:dc:cd;
 | |
|    fixed-address ivana-laptop.flr.netz ;
 | |
| }
 | |
| 
 | |
| #host lisa-Laptop {
 | |
| #   # - on chipset WLAN
 | |
| #   hardware ethernet ;
 | |
| #   fixed-address lisa-laptop.flr.netz ;
 | |
| #}
 | |
| 
 | |
| host lisa-lan {
 | |
|    # - on chipset LAN
 | |
|    hardware ethernet 3c:97:0e:d5:f0:f7;
 | |
|    fixed-address lisa-lan.flr.netz ;
 | |
| }
 | |
| 
 | |
| host sabrina-Laptop {
 | |
|    # - on chipset LAN
 | |
|    hardware ethernet b4:6d:83:4a:ab:c3;
 | |
|    fixed-address sabrina-laptop.flr.netz ;
 | |
| }
 | |
| 
 | |
| host sabrina-lan {
 | |
|    # - on chipset LAN
 | |
|    hardware ethernet 50:7b:9d:29:50:2f;
 | |
|    fixed-address sabrina-lan.flr.netz ;
 | |
| }
 | |
| 
 | |
| host flr-1-lan {
 | |
|    # - on chipset LAN
 | |
|    hardware ethernet 1c:39:47:d8:75:ae;
 | |
|    fixed-address flr-1-lan.flr.netz ;
 | |
| }
 | |
| 
 | |
| 
 | |
| ## - wireless LAN
 | |
| subnet 192.168.103.0 netmask 255.255.255.0 {
 | |
| 
 | |
|    # --- 192.168.103.160/27 ---
 | |
|    # network address....: 192.168.103.160
 | |
|    # Broadcast address..: 192.168.103.191
 | |
|    # netmask............: 255.255.255.224
 | |
|    # network range......: 192.168.103.160 - 192.168.103.191
 | |
|    # Usable range.......: 192.168.103.161 - 192.168.103.190
 | |
| 
 | |
|    range 192.168.103.161 192.168.103.190;
 | |
|    option domain-name "flr.netz";
 | |
|    option domain-name-servers nscache.flr.netz;
 | |
|    option subnet-mask 255.255.255.0;
 | |
|    option broadcast-address 192.168.103.255;
 | |
|    option routers gw-flr-wlan.flr.netz;
 | |
| 
 | |
|    default-lease-time 86400;
 | |
|    max-lease-time 259200;
 | |
| }
 | |
| 
 | |
| #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;
 | |
| #  }
 | |
| #}
 |