home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip
- Path: sparky!uunet!cs.utexas.edu!torn!watserv2.uwaterloo.ca!watserv1!sunee.uwaterloo.ca!erick
- From: erick@sunee.uwaterloo.ca (Erick Engelke)
- Subject: Re: PCS WITH DUPLICATE TCP ADDRESSES
- Message-ID: <BzoJ13.738@watserv1.uwaterloo.ca>
- Sender: news@watserv1.uwaterloo.ca
- Organization: University of Waterloo
- References: <1992Dec19.135454.548@fallst> <1992Dec20.094107.1@kean.ucs.mun.ca> <1992Dec22.191907.23824@mmm.serc.3m.com>
- Date: Tue, 22 Dec 1992 21:15:02 GMT
- Lines: 25
-
- > ccg@tcdsp1.mmm.com ("Charles Ganzhorn") writes:
- >BOOTP is major bad idea. You have to configure your routers to pass the
- >silly stuff 'cuz you won't necessarily have a load host in all subnets.
-
- Yes, like that silly DNS idea where we had to add nameservers just
- to support names. Here we have to add one configuration parameter
- to a router for each network. What a large price to pay for
- automatic configuration of all the machines on that subnet.
-
- >Also, if your BOOTP logs all requests, a station whose download doesn't
- >get satisfied typically requests every five seconds and ends up filling
- >up the logs on systems.
-
- So your error logs, if turned on, will show a broken system. That is
- a problem because it makes it so much harder to ignore a system
- which is unable to boot up.
-
- Get with the program, and Merry Christmas.
-
- Erick
-
- --
- ----------------------------------------------------------------------------
- Erick Engelke WATTCP Architect
- erick@development.uwaterloo.ca TCP/IP was easy but i still can't work VI
-