DHCP Server Open Source Freeware Windows/Linux. MultiSubnet DHCP Server supports Dynamic, Static Leases, Relay Agents, BOOTP, PXEBOOT. Global, Range and Client Specific Options. Supports filtering of ranges on Mac Address, Vendor and User Class.
- Support all Industry Standard Feaures
- Dynamic and Static Leases
- Options can be Client Specific, Range Specific or Global
- Multisubnet supports Relay Agents and PXE Boot
- Lease Status in auto refreshing html page
- Supports Duplicated Replicated Operation
- Very simple to install and use, even by person not having DHCP concepts
- Very low memory and cpu use
This is an excellent utility, highly recommended for all network administrators that need a fast, stable, easy-to-use and versatile DHCP server. My ISP-provided modem/router (Orange Live Box) had very little configurable options in terms of DHCP which was proving to be quite a headache in an environment of mixed setups (static and dynamic hosts). Open DHCP Server proved to be everything I ever needed. Having not used it before, it only took me about 10 minutes to have it up and running (mostly spent skimming through the user manual) without any glitches at the very first run!
The server run perfectly on my W7 system. I use it for Arduino Yun, in order to know the IP address. Thanks!
thank you for wonderful share..
It's a good high-performance DHCP server. I've been reading through the code and the code could have been written better by using variable and structure names that make logical sense. It uses Data1, Data2, etc for almost all the data structures which is very ambiguous or cryptic. Structs are used instead of objects and most of the code is ANSI C, not C++. The constant variables are well laid out though, I will give it that. It uses some legacy Windows API calls from Win95/98, and nearly the entire program is written in one C++ file (over 5,000 lines of code). It lacks a true PXE server's functionality (aka Proxy DHCP) as laid out by the PXE 2.1 specification. Many of the numbers are fixed such as the number of MAC filters that you can specify. I believe this was done to maximize performance. It could be increased to a much larger number of filters by using objects instead of fixed numbers but at the expense of very little performance. I'm reading the code to write in the Proxy DHCP server functionality, because I just need a DHCP server that co-works with an already existing DHCP server to handout PXE information.