[NCLUG] permanent IP addresses on a home LAN?
John L. Bass
jbass at dmsd.com
Wed Aug 1 08:22:00 MDT 2007
From: Chris Ernst <penguin-guy at comcast.net>
Or take it one step further. Let your Linux box take care of DHCP and
DNS using dynamic DNS. That way you never have to worry about who has
what address. All you need to remember is names.
I've found that just creates one more level of complexity, and another place for
things to break.
The std dhcpd allows locking IPs to MAC addresses, so that dynamic isn't required.
When you introduce a new machine or NIC into the system, it will get a lease from
the pool. When you feel like assigning that device it's own IP, you take a quick
look in the log file for it's MAC, and update dhcpd.conf and the zone file, and
forget about it after restarting the services.
I've managed a number of sites that way, and find it actually easier, even for
large clusters. Examples below.
Have fun!
John
host garfield {
hardware ethernet 00:0E:0C:67:F4:1E;
fixed-address garfield.dmsd.com;
option routers 192.92.99.254;
option domain-name "dmsd.com";
option domain-name-servers 192.92.99.1, 192.92.99.254;
}
group {
next-server 192.92.99.254;
option routers 192.92.99.254;
filename "linux-install/pxelinux.0";
option root-path "/raid/mpi-cluster/";
host mpi32-223 {
hardware ethernet 00:e0:81:23:b6:18;
fixed-address mpi32-223.dmsd.com;
option host-name "mpi32-223";
}
host mpi32-224 {
hardware ethernet 00:e0:81:24:3f:8e;
fixed-address mpi32-224.dmsd.com;
option host-name "mpi32-224";
}
host mpi32-225 {
hardware ethernet 00:e0:81:23:b7:7c;
fixed-address mpi32-225.dmsd.com;
option host-name "mpi32-225";
}
host mpi32-226 {
hardware ethernet 00:e0:81:26:d5:b2;
fixed-address mpi32-226.dmsd.com;
option host-name "mpi32-226";
}
host mpi32-227 {
hardware ethernet 00:e0:81:26:d5:de;
fixed-address mpi32-227.dmsd.com;
option host-name "mpi32-227";
}
}
More information about the NCLUG
mailing list