Cable Forum - View Single Post - Confused

Ignitionnet · 29-04-2011, 23:31

A couple of points to bear in mind are that if the ethernet controller is largely software based there can be bottlenecks there, be it in terms of bus speeds, using CPU instead of on-board processing, whatever. Indeed there can be huge differences between speeds when using on-board GigE between the two points, not uncommon to find one that isn't that far away from GigE while the other port is sharing resources with other devices and doesn't do much over 100Mbps.

If you have 2 Ethernet ports try them both.

There is absolutely no requirement to use Cat5e - most Cat5 is fine for GigE. At least that's what me and IEEE standard 802.3ab - 1000BASE-T over copper wiring think. YMMV.

Sucky cable is sucky cable whether it has an e at the end or not, poor quality Cat5e just gets to suck right the way up to 350MHz.

29-04-2011, 23:31	#11
Ignitionnet Inactive Join Date: Jun 2008 Location: Leeds, West Yorkshire Age: 47 Posts: 13,995	Re: Confused - gigabit ethernet speed & Superhub A couple of points to bear in mind are that if the ethernet controller is largely software based there can be bottlenecks there, be it in terms of bus speeds, using CPU instead of on-board processing, whatever. Indeed there can be huge differences between speeds when using on-board GigE between the two points, not uncommon to find one that isn't that far away from GigE while the other port is sharing resources with other devices and doesn't do much over 100Mbps. If you have 2 Ethernet ports try them both. There is absolutely no requirement to use Cat5e - most Cat5 is fine for GigE. At least that's what me and IEEE standard 802.3ab - 1000BASE-T over copper wiring think. YMMV. Sucky cable is sucky cable whether it has an e at the end or not, poor quality Cat5e just gets to suck right the way up to 350MHz.