Slashdot Mirror
Introducing DHCP on FreeBSD
BSDForums writes "On all but the smallest TCP/IP network, it's handy to configure network information for computers automatically. That's what DHCP does. It's easy to act as a DHCP client, but configuring a server is a little trickier. Dru Lavigne introduces DHCP and explains what you need to know to setup a simple DHCP server."
I had NOTHING to do with configuring a simple DHCP
server at all. It's only about dhclient and
dhcp terminology. Way to screen the story.
For every annoying gentoo user, are three even more annoying anti-gentoo crybabies. Take Yosh from #Gimp for example.
If you've ever had to admin a network with a few
nearly populated class c's or even a slightly filled
class b along with a parade of arrogant cock
contractors and traveling dignitaries coming and
going with their laptops with alarming frequency,
you'd understand how the benefits of DHCP far
outweigh some broadcast packets when you are already
severely understaffed.
For every annoying gentoo user, are three even more annoying anti-gentoo crybabies. Take Yosh from #Gimp for example.
*is speechless*
:P
Are you just concerned with job security or what man?? Thats a rediculous attitude. Sure, we have a spreadsheet for all our fixed IP systems (servers, email, firewalls, etc) but to have each client have a fixed IP is not realistic in an enterprise. Systems die, things change, and if you would rather spend valuable IT time solving IP conflicts be my guest, but I have TONS more important things to do.
No I didnt spell check this post...
Heh heh - you're a funny guy.
;)
So what if you want to change your default gateway, your WINS server address or completely change your addressing scheme because you're linking with another network or something?
I guess you're right - only a lazy sysadm wouldn't want to visit 3000 desktops and reconfigure them manually!
And with regard to broadcast - fire up Ethereal (www.ethereal.com) and see how little DHCP clags your network compared to Netbios! Oh, you can't cos you're running static IPs! Good for you and your protestant work ethic!
G4 Hackintosh
Rather than keep a spreadsheet with addresses somewhere, you use the DHCP server configuration file /etc/dhcpd.conf as your database itself. Whenever someone puts a computer on the network, here's the process:
- User plugs in
- User gets an IP address from the server for a 'bogus' network - not an IP on our actual subnetted class B.
- User usually complains to IT department (we love this part.)
- We check the dhcpd.leases file, which has a new entry like this:
- Once we're satisfied this box belongs on the network, edit
/etc/dhcpd.conf and add a static address in the 'valid' network section for this box:
- Add joeslaptop.internal.example.com to internal DNS
- Restart dhcpd
- Have user restart their computer.
Now it gets a static IP, with matching DNS entry, and we never even need to see the damned thing. When they take their laptop home, DHCP there will give them an address that works, they don't need to configure different profiles, etc.This provides the current (fake) IP address the machine is on, the client host name (usually something easy to identify). We can log into the machine and make any changes to match IT policy before we put it on our actual net, with an actual router address, etc.
All the benifits of static IP addresses, not nearly the same degree of hassle.
See now thats an excellent idea. I knew I was going to catch sh*t for this comment
-- Insert wisdom here:
For about 8 years there was DHCP support in *doze; *BSD and linux had support since I don't remember when. What's next, TCP/IP stack for openbsd ? Support for 486's in linux kernel ? How to use more than 640k ram in MS operating systems ?
I mod this a +1 Troll. :)
That's why you have a small block of DHCP addresses to serve out temporarily, and most of the boxes on your network assigned static IPs. It's not all one or the other way, you know...
I thought this article was interesting, if for no other reason than because it reminded me of how difficult it was to teach myself DHCP configuration with very little outside help. It seems like it would be a good article for someone starting out, however the title for this news post is somewhat ambiguous. Old hats can smile and remember the good old days. Newbies can learn to build a better server or client.
Go calculate something.
I can't speak to DHCP, BOOTP and DNS servers on linux, but I found the NT DHCP extremely simple to install/configure.
What I'd like to have is the convenience of DHCP for quickly adding new machines to a network, but still have an easy way to identify the machine involved in a security or policy violation (a firewall log shows that a student went to a bad web site, for instance). Ideas?
Well, the first thing you have to do is pick between Extended Memory or Expanded Memory. For conciseness, we term both types "Expended Memory".
2 dashes and a space, or just 2 dashes?
Of course it is.
I mean it's not like they just got a new version out is it (5.0), one that works with SMP and threads now, oh and had time to revamp the stable one, (4.8)
Of course it's dieing, and everyone is going to swith from Windows to Linux on the desktop this year too, every new device that comes on the market are going to provide linux drivers, and news just in, MS Office XP for Linux is going to be released.