2007-07-22
DHCP
Usually I build networks that do not use DHCP, instead I assign a static IP address to each piece of equipment. One reason for this is that I like things to stay where they are put (yes, I preferred DIP switches and jumper links to "Plug-n-Play"!) and I find static IP addresses convenient for port forwarding (e.g. forwarding HTTP or SSH connections from a site's public IP address to a box on the LAN). Last weekend Michael and I visited a long-neglected site and had to manually update the DNS numbers on each workstation. That might not have been necessary if each workstation requested its network configuration from a server via DHCP. What I should probably do is set up a DHCP server, but configure it to hand out predetermined IP addresses to each machine based on its MAC address. That may give us the best of both worlds.
Subscribe to:
Post Comments (Atom)
3 comments:
What I have done, because the router/switch I am using does not show the MAC address along side the DHCP IP address, is allow only the number of IP addresses that would be necessary for the number of devices I have, and give each device a unique name in the workgroup (because the router does allow me to see these names and IP addresses on the same screen) and I know which device it is by the name. For mostly geek reasons, I give the devices name that mean nothing to anyone except me.
DHCP I actualy quite good.
And its enough hard to configure isc-dhcpd (especialy netboot for a dec machine) to be geeky. :P
And I name my machines after poetic eddas. :)
I don't use DHCP unless I have to.
Post a Comment