Path: utzoo!utgpu!watserv1!watmath!att!news.cs.indiana.edu!sdd.hp.com!usc!ucsd!ucbvax!DUKEMC.BITNET!DMPM
From: DMPM@DUKEMC.BITNET (James Dryfoos- PostMaster)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Summary: Thin <-> Thick Ethernet
Message-ID: <F397E976CABF0000B8@dukemc>
Date: 6 Dec 90 13:49:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 15

I would like to comment on your thick to thin proposals.
I would suggest using a repeater.  The repeater will pass all
protocols.  You do not need a router.  The repeater also will protect
your thick wire network.  One problem with thin wire is it is easily disrupted.
Adding new connections requires breaking the cable, and simply sliding a pc
on the desk top can cause the thin wire to go down.  If you have a repeater
the repeater will segment the thin from the thick and allow the thick to
continue working while the thin is down.  This has been very important to
us as we find the thin not the most secure.  You can add a couple of extra
blank (not used) t connectors on the thin for future connections, but
if you add too many you also add interference on the wire which may cause
it to die.  The repeater is a MAC layer device and is therefore protocol
independant.

Jim Dryfoos