I had a ~450ft 1Gbps link using Cat5e work just fine. We had run both fiber and ethernet. One day, the fiber just died. The link auto-magically switched over to ethernet and ran just fine until we could fix the fiber.
On Mon, Jan 14, 2019 at 6:13 PM Jesse DuPont <[email protected]> wrote: > Well, I meant Ethernet generically. Regardless of 4-wire vs 8-wire, in > general, the purported safe distance for an Ethernet over copper (as > opposed to fiber) connection is 100 meters. What drives this safe distance > limitation spec? > > *Jesse DuPont* > > Network Architect > email: [email protected] > Celerity Networks LLC > > Celerity Broadband LLC > Like us! facebook.com/celeritynetworksllc > > Like us! facebook.com/celeritybroadband > > On 1/14/19 4:03 PM, [email protected] wrote: > > I presume you are talking about 4 wire Ethernet because we do GigE all the > time on copper. > GigE uses all 8 wires and has data flowing both directions. > > 100 Mbps E uses 4 wires (2 pair) with TX on one pair and RX on the other > pair. > GigE uses advanced modulation methods as well. > > Does that help? > > *From:* Jesse DuPont > *Sent:* Monday, January 14, 2019 3:58 PM > *To:* AnimalFarm Microwave Users Group > *Subject:* [AFMUG] Ethernet 100M Copper Limit > > I figured this was the best place to ask this question: > > What is the primary reason for the 100M limit on copper Ethernet links? Is > it related to bit errors/SNR or is there a timing element involved? > Something else? > > Thanks! > -- > > *Jesse DuPont* > > Network Architect > email: [email protected] > Celerity Networks LLC > > Celerity Broadband LLC > Like us! facebook.com/celeritynetworksllc > > Like us! facebook.com/celeritybroadband > > ------------------------------ > -- > AF mailing list > [email protected] > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > > -- > AF mailing list > [email protected] > http://af.afmug.com/mailman/listinfo/af_af.afmug.com >
-- AF mailing list [email protected] http://af.afmug.com/mailman/listinfo/af_af.afmug.com
