Date: Tue, 19 Nov 1996 17:00:51 -0600 (CST) From: Joe Greco <jgreco@brasil.moneng.mei.com> To: root@bb.cc.wa.us (Chris Coleman) Subject: Re: Ipx to ip routing Message-ID: <199611200359.VAA06570@brasil.moneng.mei.com> In-Reply-To: <Pine.NEB.3.94.961119134756.404A-100000@aries.bb.cc.wa.us> from "Chris Coleman" at Nov 19, 96 01:53:18 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> And we want to eliminate the need for so many ip addresses so that we > can get rid of all the ip address conflicts that we can't seem to trace > down. > > Any one have a good method of finding an ip address conflict? Don't know about the rest, but typically I would suggest that the above suggests a certain lack of networking discipline. :-( Usually IP address conflicts arise when someone has created a network that is too large. I usually become uncomfortable somewhere around 8 or 16 nodes, but then I am a bit paranoid. :-) Ideally, in a school environment, each networked classroom or lab should be on its own subnet, or perhaps several subnets. When the machines are configured, use a labeler to note the machine's IP address on the front of the machine. Preferably devise some logical mechanism for numbering, such as sequential numbering, so that when students pull off the labels, it is still pretty easy to figure it out. If you do that and keep no more than, maybe, 16 machines on a network, then you only have 16 machines to check when a problem arises. If they are all in the same room, this is pretty easy. As far as your address space concerns, in your scenario I would probably consider using 10-net addresses, a proxy Web server, and a NAT device to provide continued access to Internet services. The 10-net thing works really nice even for a large school, because you can use the second octet to designate building, third octet to designate room, and fourth octet to designate machine number. ... JG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611200359.VAA06570>