4 ms·
I'm seeing 2.5 and 5 popping up all over the place. My WiFi App has 2.5 with POE. The aggregate bandwidth of the AP exceeds 1G. Spectrum cable modems have 2.5G
by thedougd 5y ago
I'm seeing 2.5 and 5 popping up all over the place. My WiFi App has 2.5 with POE. The aggregate bandwidth of the AP exceeds 1G. Spectrum cable modems have 2.5G ports now and AT&T Fiber is shipping their garbage gateway with a 5G port.
Unfortunately, I'm finding switches with 2.5 to still be overpriced.
- zrail 5y agoI wanted to upgrade portions of my home network to multigig because Comcast is giving us 1.4Gbps and I wanted to use it. At least for me, 2.5 switches were way to expensive so I ended up with used Intel 10G cards connected with DACs to a cheap 5 port Mikrotik 10G switch. One 10GBase-T RJ45 SFP+ hooks into the modem.
- walrus01 5y ago"1.4Gbps" and probably 16Mbps upstream on DOCSIS3.1 channel bonding I'd rather have a 100Mbps home DIA circuit that was symmetric and seriously reliable, than the typical Comcast circuit.
- zrail 5y agoIt's generally around 35-40Mbps upstream and between 600 and 1.2Gbps observed downstream, depending on the time of day. I would also very much rather have a symmetric connection than what I have now. We are within range of a fiber tap for Comcast's 3Gbps symmetric ftth service but construction costs are too high right now for them to do it. I keep asking every six months regardless. There's no other game in town as far as I can tell. Comcast Business will run a 100Mbps symmetric fiber for ~$750/mo, maybe that would be a thing to do to get fiber in the door and then switch back to residential after the contract earns out.
- wolrah 5y agoAs I understand it 2.5 and 5G modes were originally primarily aimed at WiFi APs as real-world capacities started to scale past gigabit speeds but replacing existing wiring for an entire building worth of APs to support 10G or completely redesigning the power infrastructure to support fiber would have been impractical. Instead we run 10G signaling at half or quarter clock rates and get something that works on the majority of existing wiring. AFAIK the IEEE was initially resisting supporting this, but enough vendors were just doing it anyways that it was better to standardize.