The INI file looks like this:

[General]
SUBNETMASK=255.255.255.0
LEASETIME=32000000 ; approx. 1 year
ROUTER_1=192.168.10.1
DNS_1=192.168.10.1
[Settings]
IPBIND_1=192.168.10.1
IgnoreUnknownClients=1
[00-E0-00-1C-AB-68] ; Client 2
IPADDR=192.168.10.50
[00-E0-00-1C-AB-67] ; Client 1
IPADDR=192.168.10.11

Please note the line IgnoreUnknownClients=1. This option prevents the DHCP Server from sending answers to clients that are not configured in the INI file.

The INI file looks like this:

[General]
SUBNETMASK=255.255.255.0
ROUTER_1=192.168.10.1 
DNS_1=192.168.10.1 
[Settings]
AssociateBindsToPools=1
IPBIND_1=192.168.10.1
IPBIND_2=192.168.11.1
IPPOOL_1=192.168.10.2-49
IPPOOL_2=192.168.11.2-49

This manages the IP addresses 192.168.10.2 until 192.168.10.49 for Ethernet 1 and 192.168.11.2 until 192.168.11.49 for Ethernet 2. Please note the line AssociateBindsToPools=1. This option associates the IP Pools with the corresponding IP Binds. Without that option the DHCP Server would view all IPPOOL_x as one big IP pool independent of the subnet.

The INI file looks like this:

[General]
SUBNETMASK=255.255.255.0
ROUTER_1=192.168.10.1 
DNS_1=192.168.10.1 
[Settings]
IPBIND_1=192.168.10.1
IPPOOL_1=192.168.10.2-49 

This manages the IP addresses 192.168.10.2 until 192.168.10.49. The DHCP Server binds only to one NIC with the IP address 192.168.10.1. The other NIC (Ethernet 2) is not touched by the DHCP Server. This is very useful if Ethernet 2 is your company LAN and you don’t want to interfere with it.

This is a very simple example and the INI file looks like this:

[General]
SUBNETMASK=255.255.255.0
ROUTER_1=192.168.10.1 
DNS_1=192.168.10.1 
[Settings]
IPPOOL_1=192.168.10.2-49

This manages the IP addresses 192.168.10.2 until 192.168.10.49. But be aware that all clients connected to the subnet 192.168.10.X get IP addresses assigned. Please make sure that you don’t get in conflict with other DHCP Servers.