Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.uoknor.edu!news.nodak.edu!netnews3.nwnet.net!netnews.nwnet.net!symiserver2.symantec.com!usenet From: tedm@agora.rdrop.com Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Any Info on NIS & Reverse Protocol Date: 12 Aug 1996 06:03:36 GMT Organization: Symantec Corporation Lines: 22 Message-ID: <4umhfo$ftl@symiserver2.symantec.com> References: <01bb84d2$a69064a0$6fc4abc7@glen> <320C1402.362C@www.play-hookey.com> Reply-To: tedm%toybox@agora.rdrop.com NNTP-Posting-Host: 198.6.34.2 X-Newsreader: IBM NewsReader/2 v1.2 In <320C1402.362C@www.play-hookey.com>, Ken Bigelow <kbigelow@www.play-hookey.com> writes: >glen wrote: [some deleted] >You may want to monitor the operation of the network, and thereby match >up specific machines to their assigned IP addresses, but what's the point >of going to the trouble of using dynamic techniques to assign a fixed >address to a specific node? I can see you have never managed large networks before. I do dynamic IP assignment as described above with static IP addresses on my networks. The reason is that every so often a user will blow away their system and reinstall. Of course they haven't saved their IP number or host name information which I neatly lettered out for them on a card when they asked for the IP number to begin with. :-) After I got tired of handing out the nth duplicate of the numbers I wised up and required DHCP on all the clients. Of course this is PC-LAN stuff but if the guy has a network of BSD machines used as client systems I can imagine why he wants to automate it.