Overseas lessdisks dhcpdconf

2. Sample configuration file for ISC dhcpd for Debian
4. $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $

1. The ddns-updates-style parameter controls whether or not the server will
2. attempt to do a DNS update when a lease is confirmed. We default to the
3. behavior of the version 2 packages ('none', since DHCP v2 didn't
4. have support for DDNS.)

ddns-update-style none;

1. option definitions common to all supported networks...
2. option domain-name "example.org";
3. option domain-name-servers ns1.example.org, ns2.example.org;

default-lease-time 600; max-lease-time 7200;

1. If this DHCP server is the official DHCP server for the local
2. network, the authoritative directive should be uncommented.
3. authoritative;

1. Use this to send dhcp log messages to a different log file (you also
2. have to hack syslog.conf to complete the redirection).

log-facility local7;

1. No service will be given on this subnet, but declaring it helps the
2. DHCP server to understand the network topology.

subnet 10.10.1.0 netmask 255.255.255.0 {

 range dynamic-bootp 10.10.1.200 10.10.1.254;
 default-lease-time 600;
 max-lease-time 7200;
 option subnet-mask 255.255.255.0;
 option broadcast-address 10.10.1.255;
 option routers 10.10.1.254;
 option domain-name-servers 10.10.1.254;
 # option domain-name "somelan";
 # next-server is only needed if the dhcp and nfs servers are different machines
 #next-server 192.168.1.9;
 # tftp-server-name is needed in addition to (instead of?) next-server when using 
 # the kernel initrd method.  for some reason dhclient won't grab next-server...
 #option tftp-server-name 192.168.1.9;
 filename "/var/lib/lessdisks/boot/vmlinuz.nb";
 option root-path "/var/lib/lessdisks/";

 # these are options to allow for boot menus with etherboot
 # option-128 must be reproduced exactly- it is not a mac address
 #option option-128 e4:45:74:68:00:00;
 #option option-160 "timeout=10:default=193";
 #option option-184 "/etc/motd";
 #option option-192 "oldkernel:::/var/lib/lessdisks/boot/bzimage.ramfs.nb:::=old";
 #option option-193 "newkernel:::/var/lib/lessdisks/boot/vmlinuz-2.4.16ld.nb:::=new";

 #group {
 # options for terminals that use network-bootable grub

 #filename "/var/lib/lessdisks/boot/grub/nbgrub";
 # default grub menu
 #option option-150 "(nd)/var/lib/lessdisks/boot/grub/menu.lst";
 #host foo { hardware ethernet 00:90:27:9A:53:EF; }
 #host bar { hardware ethernet 00:02:b3:b7:b2:66; }
 #}
 #group {
   # alpha terminals
   # tftpd-hpa lets you specify filename relative to tftpd root path
   #filename "alpha-root/boot/vmlinuz.nb";
   #option root-path "/var/lib/lessdisks/alpha-root/";
   #host alphaterminal { hardware ethernet 08:00:2B:E5:27:E9; }
 #}

}

1. subnet 10.152.187.0 netmask 255.255.255.0 {
2. }

1. This is a very basic subnet declaration.

1. subnet 10.254.239.0 netmask 255.255.255.224 {
2. range 10.254.239.10 10.254.239.20;
3. option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
4. }

1. This declaration allows BOOTP clients to get dynamic addresses,
2. which we don't really recommend.

1. subnet 10.254.239.32 netmask 255.255.255.224 {
2. range dynamic-bootp 10.254.239.40 10.254.239.60;
3. option broadcast-address 10.254.239.31;
4. option routers rtr-239-32-1.example.org;
5. }

1. A slightly different configuration for an internal subnet.
2. subnet 10.5.5.0 netmask 255.255.255.224 {
3. range 10.5.5.26 10.5.5.30;
4. option domain-name-servers ns1.internal.example.org;
5. option domain-name "internal.example.org";
6. option routers 10.5.5.1;
7. option broadcast-address 10.5.5.31;
8. default-lease-time 600;
9. max-lease-time 7200;
10. }

1. Hosts which require special configuration options can be listed in
2. host statements. If no address is specified, the address will be
3. allocated dynamically (if possible), but the host-specific information
4. will still come from the host declaration.

1. host passacaglia {
2. hardware ethernet 0:0:c0:5d:bd:95;
3. filename "vmunix.passacaglia";
4. server-name "toccata.fugue.com";
5. }

1. Fixed IP addresses can also be specified for hosts. These addresses
2. should not also be listed as being available for dynamic assignment.
3. Hosts for which fixed IP addresses have been specified can boot using
4. BOOTP or DHCP. Hosts for which no fixed address is specified can only
5. be booted with DHCP, unless there is an address range on the subnet
6. to which a BOOTP client is connected which has the dynamic-bootp flag
7. set.
8. host fantasia {
9. hardware ethernet 08:00:07:26:c0:a5;
10. fixed-address fantasia.fugue.com;
11. }

1. You can declare a class of clients and then do address allocation
2. based on that. The example below shows a case where all clients
3. in a certain class get addresses on the 10.17.224/24 subnet, and all
4. other clients get addresses on the 10.0.29/24 subnet.

1. class "foo" {
2. match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
3. }

1. shared-network 224-29 {
2. subnet 10.17.224.0 netmask 255.255.255.0 {
3. option routers rtr-224.example.org;
4. }
5. subnet 10.0.29.0 netmask 255.255.255.0 {
6. option routers rtr-29.example.org;
7. }
8. pool {
9. allow members of "foo";
10. range 10.17.224.10 10.17.224.250;
11. }
12. pool {
13. deny members of "foo";
14. range 10.0.29.10 10.0.29.230;
15. }
16. }