dhcpd

#
# 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 "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;

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

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

#subnet 182.18.0.0 netmask 255.255.192.0 {
#	interface enp3s0;
#	range 182.18.0.0 182.18.0.8;
#	default-lease-time 600;
#	max-lease-time 7200;
#}

#subnet 182.19.0.0 netmask 255.255.192.0 {
#	interface enx00e04c534458;
#	range 182.19.0.0 182.19.0.8;
#	default-lease-time 600;
#	max-lease-time 7200;
#}

# A slightly different configuration for an internal subnet.
subnet 182.18.0.0 netmask 255.255.0.0 {
	interface enp3s0;
 	range 182.18.0.2 182.18.0.9;
	default-lease-time 600;
  	max-lease-time 7200;
  	option subnet-mask 255.255.192.0;
  	option routers 182.18.0.1;
  	option broadcast-address 182.18.63.255;
  
}

subnet 182.19.0.0 netmask 255.255.0.0 {
	interface enx00e04c534458;
 	range 182.19.0.2 182.19.0.9;
	default-lease-time 600;
  	max-lease-time 7200;
  	option subnet-mask 255.255.192.0;
  	option routers 182.19.0.1;
  	option broadcast-address 182.19.63.255;
  
}

host client1
{
	hardware ethernet 08:00:27:91:44:86;
	fixed-address 182.18.0.6;
}

host client2
{
	#hardware ethernet 00:e0:4c:53:44:58;
	#akuhardware ethernet 2c:56:dc:04:8b:65;
	hardware ethernet 28:d2:44:6b:14:be;
	fixed-address 182.19.0.4;
}



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


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

interfaces

auto lo
iface lo inet loopback

allow-hotplug enp3s0
#auto enp3s0
iface enp3s0 inet static
address 182.18.0.1
netmask 255.255.192.0
network 182.18.0.0
gateway 182.18.0.1

allow-hotplug enx00e04c534458
#auto enx00e04c534458
iface enx00e04c534458 inet static
address 182.19.0.1
netmask 255.255.192.0
network 182.19.0.0
gateway 182.19.0.1

isc

# Defaults for isc-dhcp-server initscript
# sourced by /etc/init.d/isc-dhcp-server
# installed at /etc/default/isc-dhcp-server by the maintainer scripts

#
# This is a POSIX shell fragment
#

# Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
#DHCPD_CONF=/etc/dhcp/dhcpd.conf

# Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
#DHCPD_PID=/var/run/dhcpd.pid

# Additional options to start dhcpd with.
#	Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
#OPTIONS=""

# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
#	Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACES="enp3s0 enx00e04c534458"