Set up a DHCP server to manage IP addresses
An anonymous reader writes "The second in a three-part series on how to leverage Linux to get the most from your network, this tutorial shows how to set up a Dynamic Host Configuration Protocol (DHCP) server with Internet Systems Consortium (ISC) DHCP. Sample code and configuration files are provided throughout to aid understanding."
http://www.bugmenot.com/view.php?url=www.ibm.com
For small networks, I recommend using dnsmasq. It's a combined DHCP server and DNS server/proxy intended for use on a masquerading gateway that can run nearly without any configuration. Add your mac addresses to /etc/ethers for fixed IP adresses, add your hostnames to /etc/hosts, finito. There is no need to fiddle with to big servers (bind and ISC dhcpd). I use it on my (heavily modified) WRT54G with about 10 to 20 systems without any problems.
Tux2000
Denken hilft.
I have a DHCP Server enabled on my Router, so why would I need to do this? Maybe for a large-network business application, but for the majority of network applications (read home and small business) what's the point other than an academic lesson?
(OK, so I didn't actually read the article because of the requried registration...)
My mom always said, "Jim, you're 1 in a million." Given the current population, there are 7000 of me. God help us all!
Is Slashdot posting Howto's now?
:|
Or did an editor slip up (never!) and hit the "post this" button instead of the "delete" button?
I hate being this confused on a Monday morning...
Anyway my suggestion is if you want better control, what you do is to have your DHCP server assign unknown machines to IP addresses in a quarantine network that possibly runs something like nocatauth to tell new users to contact the admin - phone num etc. Heck maybe put each of them in their own /30 network or something.
Once they call you and you've identified the previously unknown machine and the user and everything is OK (scan for viruses, detect worms etc), you can reassign this machine to its own reserved IP - and possibly reconfigure the relevant switch's port to take it out of the special mode that only allows it to talk to one server and not each other (not all switches support this feature).
This could help prevent unknown machines from spreading worms, or automatically getting access to your network.
This is nice and all, but how about a comprehensive resource for setting up an internal network running IPv6. When adoption of IPv6 is always on the "Coming soon..." list (in North America at least), it would be nice to see an article, HOWTO, or something dealing the current setup and pitfalls.
Knowing that the tools (RADVD or DHCPv6, 6to4 gateways, DNS "AAAA" records, etc.) are out there is one thing, knowing how to get them to fit together and pull it off is another. If anybody knows how to setup an internal IPv6-only network where systems are accessible from "the outside", info would be appreciated.
There's good how-tos on www.6bone.net and www.tldp.org ;)
I never got passed the 'subscribe to 6bone' stage, was too much to read and I thought IPv6 means more bits for my dear ol' mowdem to cope with.
Why UNIX?
is there a functioning Linux distribution that DOESN'T come with a fully functioning DHCP server preinstalled, that you have to kill if you have more than one box on your network?? I don't think so..
at least, after installing three Fedora boxes and a Debian box on my network, I had a hell of a time getting my networking to work on the systems, until I realised that without asking me, all of them installed a function DHCP client and server..
(Linux distribution install programs suck)
"Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
I'm setting up a router at my home (1st time I ever did that) and the DHCP server is really the easiest part.
Only 2 things to watch out for:
-Don't kill DHCPCD instead of DHCPD (while working remote it can have quite harmfull effects)
-Run DHCPD without the '-q' parmeter the 1st time to check if your config file is correct.
Some tips on getting dhcpd and bind to "play nicely together" would be useful. It's not rocket science, but it's not exactly obvious, either.
Would it be possible for a small router box (such as one running Linux) to also supply a local tiny DNS?
/etc/hosts table does work, however.
My cheapo commercial router/firewall seems to know the "name" of each machine, as it shows that name along with the MAC and IP address in it's web page (admittedly Linux makes it a pain in the ass to locate and change this name, why can't it match the hostname automatically?). However if I do "ping " it does not work. Adding the name and IP address to my
So a couple questions:
1. Would it be possible for the router to do DNS such that any attempt to name a machine that is on the local net produces the local net address.
2. If this is possible, why isn't it done? (ie on a commercial Linux-based router)