Comment: Building a DHCP server....
I'm sure there are some really talented members here, but, has anyone built a DHCP server ? I don't mean using DNSMasq either. I have "THE" book on DHCP,
"The DHCP Handbook" by Droms & Lemon, one of the actual innovators of DHCP.
Regardless, there are a lot of 'little' things one needs to know and be aware of in order to build a working DHCP server. I used OpenBSD, and things finally worked fine after a little trial and error (thank goodness for WireShark).
There are many Linux distributions, namely Ubuntu, that lets one implement a DHCP server in no time at all; however, what does one learn ?
As previously stated, this may be trivial to some; it took a little time and work on my part !
I built our original corporate DHCP servers years ago
"building" is too grand of a term, it was more just turning on software, and options to match what we needed. what are you looking to accomplish?
shdesignsPowered By Infinite Improbabilty DrivePremiumReviews:
Stone Mountain, GA
|reply to G00SE |
Any linux or *BSD distribution can be used. It is just a matter of configuring the server and enabling it.
I use pfsense for my DHCP server, router, firewall and access point. Probably one of the fastest to get going and runs on a 512 meg CF flash card.
BinkVillains... knock off all that evilReviews:
Castle Rock, CO
|reply to G00SE |
DHCP is rather simple. I use this regularly and in various forms, but tend to deploy these mostly in Windows environments (in conjunction with DNS and AD). That said, Im a fan of OpenBSD and am quite comfortable with its dhcpd (the included dhcpd.conf is fairly well commented and readily useable with some changes in small environments).
Saint Paul, MN
|reply to G00SE |
Setting up a DHCP server is the easy part. Managing your IP addresses is the work part. You need to come up with best practices for your environment. Some of the things I believe are important are:
1. Set up an address structure. Section your network so that specific equipment will be in a specific range. Leave room for expansion. For example: Network equipment 192.168.1.1 - 192.168.1.20, Servers 192.168.1.21 - 192.168.1.40, Printers 192.168.1.41 - 192.168.1.60, Clients 192.168.1.100 - 192.168.1.225
2. Set reservations for static equipment, servers and printers. You may also want to set the IP address on the actual hardware, but this will keep your network up and running after a power outage if the device loses its manually set IP address.
3. Keep your reservations up to date. When you remove equipment, remove the reservation.
4. Set the longest DHCP address lease that makes sense in your environment. Shorter leases cause more network traffic. Longer leases can result in no IP address being available for new clients. Find the happy medium for your site.
I'm sure there are more, but those are what I have found to be the biggest helps.
"Progress isn't made by early risers. It's made by lazy men trying to find easier ways to do something." - Robert A. Heinlein
'Sorry for the late reply, and yes, DHCP in concept is quite simple. However, there are a lot of "little" things one needs to keep in mind, especially if setting up an OpenBSD DHCP server to work with any Windows OS. Does 255.255.255.255 ring any bells ? Does ICMP ? Yes, for some of you, this is trivial, but just starting essentially from scratch, only knowing the basics of networking and DHCP ? It wasn't a week of frustration or the like, but it did take a little trial and error over about half a day. Mostly, I made really silly mistakes, like getting the gateway wrong, or the like, but there's still a careful path, which most of you seem to have gone down many times, that needs to be closely and carefully followed. Re the addressing, yes, I can relate to that too, as it makes a big diff over the lifetime of the system, and is very important. Thanks for the great replies.
AnavSarcastic Llama? Naw, Just AcerbicPremium
What your describing is learning many topics required to implement a DHCP server because its really the study of networking that is involved. DHPC server is but one small subset of knowledge that needs to be put in context.
You're so right Anav ! I majored in computer science, way back, and there was a lot to learn then. Now, one could easily major in a tiny subset of the virtually unlimited amount of information regarding networking, languages, etc, etc......