Modernize dhcpd.conf example

diff --git a/server/dhcpd.conf b/server/dhcpd.conf
index 6ef0a9ac7d6158eccada18e4d0687a1e86c3707c..6713d27b39901f2f18e8bd90bf46a2ee0c49d27f 100644 (file)
--- a/server/dhcpd.conf
+++ b/server/dhcpd.conf
@@ -4,36 +4,49 @@
 #
 
 # option definitions common to all supported networks...
-option domain-name "fugue.com";
-option domain-name-servers toccata.fugue.com;
+option domain-name "example.org";
+option domain-name-servers ns1.example.org, ns2.example.org;
 
-option subnet-mask 255.255.255.224;
 default-lease-time 600;
 max-lease-time 7200;
 
-subnet 204.152.187.0 netmask 255.255.255.0 {
+# 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 {
 }
 
-subnet 204.254.239.0 netmask 255.255.255.224 {
-  range 204.254.239.10 204.254.239.20;
-  option broadcast-address 204.254.239.31;
-  option routers prelude.fugue.com;
+# 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;
 }
 
-# The other subnet that shares this physical network
-subnet 204.254.239.32 netmask 255.255.255.224 {
-  range dynamic-bootp 204.254.239.40 204.254.239.60;
-  option broadcast-address 204.254.239.31;
-  option routers snarg.fugue.com;
+# 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;
 }
 
-subnet 192.5.5.0 netmask 255.255.255.224 {
-  range 192.5.5.26 192.5.5.30;
-  option domain-name-servers bb.home.vix.com, gw.home.vix.com;
-  option domain-name "vix.com";
-  option routers 192.5.5.1;
-  option subnet-mask 255.255.255.224;
-  option broadcast-address 192.5.5.31;
+# 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;
 }
@@ -61,3 +74,28 @@ host fantasia {
   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;
+  }
+}