Article View: comp.dcom.modems.cable
Article #340Re: running network cable through windows and walls?
From: Kevin Oberman
Date: Wed, 02 Sep 1998 00:00
Date: Wed, 02 Sep 1998 00:00
43 lines
3144 bytes
3144 bytes
For_Email@ddress.see.below_plea.se (Philip J. Koenig) writes: > The reason that using correct cable is important are as follows: > > 1 - Terminators and NIC's are 75 ohm, if the cable is not, you end up > with reflections that play hell with the waveforms and thus, data > integrity. Terminators and NICs are 50 ohms for 10Base2 (Ethernet). > 2 - The reason distance is a factor (and why the IEEE specifies a > maximum length for 10base2 segments) is due to the rate of signal > propagation. Since 802.3 collision detection relies on a known rate > of propagation and maximum segment length (tailoring it's "collision > listen window" accordingly), if you run out-of-spec cabling you run > the risk that collision-detection no longer works correctly, which > causes a host of problems including runt packets, late-collisions, > etc. The reason for the limits on coax length is resistance. The time budget is real, but only applies to repeated (multi-segment) networks and fiber nets. Neither coax nor UTP lengths will allow for single segments approaching the Ethernet time budget. (Thin net (10Base2) is limited to 185 meters and thick net (10Base5) to 500 meters.) While Vp varies from medium to medium, it is pretty safe to say that time budget will allow for about a 2500 meter network diameter. If you really want to get into all of this, read up on transmission lines and see http://www.ots.utexas.edu/ethernet/. If you want to get deeper into it, I recommend Charles Spurgeon's book, "Practical Networking with Ethernet", ISBN: 1-85032-885-4. And if you plan to make a living on Ethernet, get a copy of IEEE 802.3, the actual standard. (You need to be serious about Ethernet to get that because it is NOT an easy read, assumes a fair amount of EE background, and costs about $200.) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest Orlando Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634
Technical Details
Message-ID:
<sren28ijnot.fsf@ptavv.es.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<6rcoho$284$1@nnrp1.dejanews.com> <35DB30FF.579C273E@edwardjones.com> <35DBABFD.15FB7483@nojunk.net.crap> <slrn6tp9oi.em3.danco@pebble.org> <35DD9B28.4FC620A7@edwardjones.com> <35e6319c.53011606@news.lakwod1.co.home.com> <35EACDBE.237D36B8@edwardjones.com> <01bdd698$fe212500$8028a8c0@jb.zedak.com> <MPG.10572b78acbc04c39896ca@ispnews.walltech.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1159e3,4e89f3904072fcfe X-Google-Attributes: gid1159e3,public X-Google-Thread: fa874,4e89f3904072fcfe X-Google-Attributes: gidfa874,public X-Google-Thread: 113850,4e89f3904072fcfe X-Google-Attributes: gid113850,public From: Kevin Oberman <oberman@es.net> Subject: Re: running network cable through windows and walls? Date: 1998/09/02 Message-ID: <sren28ijnot.fsf@ptavv.es.net> X-Deja-AN: 387236928 Sender: oberman@ptavv.es.net References: <6rcoho$284$1@nnrp1.dejanews.com> <35DB30FF.579C273E@edwardjones.com> <35DBABFD.15FB7483@nojunk.net.crap> <slrn6tp9oi.em3.danco@pebble.org> <35DD9B28.4FC620A7@edwardjones.com> <35e6319c.53011606@news.lakwod1.co.home.com> <35EACDBE.237D36B8@edwardjones.com> <01bdd698$fe212500$8028a8c0@jb.zedak.com> <MPG.10572b78acbc04c39896ca@ispnews.walltech.com> Content-Type: text/plain; charset=US-ASCII Organization: ** ESnet ** The Energy Sciences Network ** Mime-Version: 1.0 (generated by tm-edit 7.108) Newsgroups: comp.dcom.modems.cable,ba.internet,alt.home.repair