#
# Sample configuration file for ISC dhcpd for Debian
#
# Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
# configuration file instead of this file.
#
#

# 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 "risefmdk.lan";
#option domain-name-servers 192.168.0.200, 192.168.0.250, 192.168.0.1;
option domain-name-servers 192.168.0.190, 192.168.0.250;

default-lease-time 21600;
max-lease-time 43200;

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

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


# declaration block for the failover peer
failover peer "failover-partner" {
     primary;
     address 192.168.0.190;
     port 519;
     peer address 192.168.0.250;
     peer port 520;
     max-response-delay 60;
     max-unacked-updates 10;
     mclt 3600;
     split 128;
     load balance max seconds 3;
}

# OMAPI
omapi-port 7911;
omapi-key omapi_key;

key omapi_key {
     algorithm hmac-md5;
     secret 6Kuys3J+4oCOOymrYCjWWlyyWTdGX+HV7nnzm6LsJ7ob698mjG0pB9AaxbJH75NcjD+ofgNL2qSkCgezn1Idqg==;
}

# A slightly different configuration for an internal subnet.
subnet 192.168.0.0 netmask 255.255.255.0 {
#  option domain-name-servers 192.168.0.200, 192.168.0.250, 192.168.0.1;
  option domain-name-servers 192.168.0.190, 192.168.0.250;
#  option domain-name "risefmdk.lan";
  option subnet-mask 255.255.255.0;
  option routers 192.168.0.1;
  option broadcast-address 192.168.0.255;
  default-lease-time 21600;
  max-lease-time 43200;
  pool {
  failover peer "failover-partner";
  range 192.168.0.10 192.168.0.119;
  }
}

# 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 zion {
  hardware ethernet 70:10:6F:CA:60:C6;
  fixed-address 192.168.0.200;
}
host matrix {
  hardware ethernet 64:00:6A:62:5A:4B;
  fixed-address 192.168.0.250;
}
host streamer {
  hardware ethernet 98:DE:D0:02:6D:AB;
  fixed-address 192.168.0.180;
}
host manheimr {
  hardware ethernet 44:8A:5B:A2:17:87;
  fixed-address 192.168.0.190;
}
#Rolf PC
host tjalfe {
  hardware ethernet 30:9C:23:A4:34:FE;
  fixed-address 192.168.0.150;
}
host vidar {
  hardware ethernet 5C:F9:DD:DC:EE:43;
  fixed-address 192.168.0.160;
}
#Switch
host vegvisir {
  hardware ethernet DC:2C:6E:33:9F:CF;
  fixed-address 192.168.0.120;
}
#Nikolaj PC
host balder {
  hardware ethernet D8:5E:D3:20:FE:5D;
  fixed-address 192.168.0.141;
}
#Magnus PC
host toke {
  hardware ethernet D8:5E:D3:2F:5C:17;
  fixed-address 192.168.0.145;
}
#Magnus xbox
host xboxone {
  hardware ethernet B4:AE:2B:BC:7B:41;
  fixed-address 192.168.0.146;
}

#host ps3 {
#  hardware ethernet 00:24:8D:5A:68:FA;
#  fixed-address 192.168.0.110;
#}

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