On Thu, Jul 26, 2012 at 12:44:20PM -0300, Fernando Cassia wrote:
DHCP gives "initial" convenience, for "long term hassle". (say you want to telnet-in to your ethernet enabled media player)
Like my tivo? host tivo { hardware ethernet 00:11:d9:0b:c3:a4; fixed-address 10.0.0.144; }
Or other appliance devices? host wii { hardware ethernet 00:1f:32:73:c6:a7; fixed-address 10.0.0.153; }
host printer { hardware ethernet 00:1b:a9:22:21:89; fixed-address 10.0.0.10; }
Personally I have my own config file: MACHINE 10.0.0.10 ; 00:1b:a9:22:21:89 ; printer ; Brother MFC-9120CN MACHINE 10.0.0.144 ;!00:11:d9:0b:c3:a4 ; tivo ; TiVo MACHINE 10.0.0.153 ;!00:1f:32:73:c6:a7 ; wii ;
From that I generate my dhcp, DNS, rDNS, IPv6 DNS (except where the MAC
begins with !) and IPv6 rDNS values.
% ping tivo PING tivo (10.0.0.144) 56(84) bytes of data. 64 bytes from tivo (10.0.0.144): icmp_seq=1 ttl=64 time=2.08 ms 64 bytes from tivo (10.0.0.144): icmp_seq=2 ttl=64 time=0.505 ms ^C
% ping6 printer PING printer(printer) 56 data bytes 64 bytes from printer: icmp_seq=1 ttl=64 time=1.09 ms 64 bytes from printer: icmp_seq=2 ttl=64 time=0.370 ms ^C
I use a CentOS machine as my dhcp server. The same can be done on most SOHO routers via the admin GUI.