Yeah, I installed a 461' link the other day and it runs at 1Gbps
fine and has solid SNRs (about 27.5). That's why I was curious about
there the 100 meter (328') limitation originated and, I suppose
separately, if it's even a valid distance limitation today on CAT5e
and higher cable.
Jesse DuPont
Network Architect
email: [email protected]
Celerity Networks LLC
Celerity Broadband LLC
Like us!
facebook.com/celeritynetworksllc
![]()
Like us!
facebook.com/celeritybroadband
![]()
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.
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?
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?
Sent: Monday, January 14, 2019 3:58
PM
Subject: [AFMUG] Ethernet 100M
Copper Limit
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
