Cipafilter Documentation - DHCP
Posted by Jim Giseburt, Last modified by Jim Giseburt on 11 April 2017 04:44 PM
The filter may act as a DHCP server for clients on the network, providing leases dynamically or statically via MAC address; this functionality is configured here.
The DHCP server functionality can be enabled or disabled (on a per-interface basis) via the Basic Configuration tab. Checking the Activate box in the table at the top of the page will enable DHCP on the corresponding interface. The Start IP field indicates the beginning of the dynamic lease range, while the End IP field indicates the end of the range. To aid in identification, the primary IP address of each interface is also listed here.
If your network already has a DHCP server you'd like to use — particularly one on a different network segment from your clients — the Cipafilter can act as a relay server. When in relay mode, the Cipafilter will capture DHCP traffic on its interfaces and forward it to/from the specified Relay Target IP.
Note: The DHCP Relay feature applies to all interfaces configured on the filter, and is incompatible with the normal DHCP Server function.
Static IP reservations can be provided here. Each IP address entered here will be excluded from the dynamic lease range specified above, and will instead be reserved for the client with the specified MAC address. Which interface assigns the IP address is determined by the subnet it is a part of. The Machine Name and Comment fields are mostly for reference.
By default, the filter provides to its clients a lease time of 864,000 seconds (10 days), and other sane configuration details derived primarily from those set on the IP Settings page. If these values are not suitable, they can be overridden here.
Active DHCP Leases
The Active Leases tab displays information about clients with active leases, as well as recently freed leases. Please note that static reservations are not treated like dynamic leases by the underlying server, and are therefore not tracked in the lease table.