Our network is comprised of mostly static IP addresses, but I do run a DHCP server, for about 8 or so IP addresses. I use static IP's mostly for security, and auditing reasons. It is much harder to audit someones actions on their PC, if their IP address keeps changing. Sure, you can mess around with the MAC address, but most TCP/IP apps work with IP addresses. Since I do allow DHCP, I run 'arpwatch' as a daemon, keeping me informed when a new machine gets an address from the network. It emails me the IP address that it is currently leasing, as well as the MAC address. This information helps me keep track of who and when. It will also inform me if the MAC address for a static IP changes. This way I can ask around and see if someone is doing something they shouldn't be. It would also alert me if someone was messing with their network setting, and changing their IP address to one of a gateway, or server.
'arpwatch' is also a useful administration tool. We recently purchased 7 HP print servers for some printers, and new offices. Since they initially get their IP address from a DHCP server, arpwatch emails me when I put a print server on the network. I can then telnet to the print sever, set up a static IP address, and save the settings. This is a lot easier than using the HP cdrom, and Windows software to manually configure each one with a static IP address.
Check out the manpage of arpwatch for other useful features.Copyright August 2003 Bruce Garlock All rights reserved
If you found something useful today, please consider a small donation.
Got something to add? Send me email.
More Articles by Bruce Garlock © 2009-11-07 Bruce Garlock
Anyone even peripherally involved with computers agrees that object-oriented programming (OOP) is the wave of the future. Maybe one in 50 of them has actually tried to use OOP – which has a lot to do with its popularity (Steve Steinberg)