The above is things you should do when you have 1gbps in order to actually get those speeds. I know people will argue citing 640k being enough for everyone and have some edge case that needs this but.... 25gbps is overkill.
There is actually a semi-reasonable case for there being a limit on useful bandwidth for most purposes. Exact numbers are hard to come by for many reasons both obvious and subtle but around 25gpbs you're getting to the point that with reasonable compression you can saturate a human's entire sensorium with retina-quality video, full audio, touch, proprioception, etc.
While there are use cases that exceed that, like running a search across the entire locally-stored output of the Large Hadron Collider, you're certainly getting to the point where the applications are getting more and more specialist relative to the average person sitting in their home, no matter how exotic the the requirements. I mean we're literally talking about having enough data bandwidth to stream your next-next-next-next-gen VR system a holodeck-like experience for you.
For 25Gbps? Or are you meaning for the 1gbps you have? If the former, of course, but otherwise Cat5e can handle 10GbE if you have good connections and the loop length isn’t too long.
Most hard drives will keep up with a full gigabit pipe, too, on a sequential write. I think the poster is exaggerating a bit.
Yes, for sure. 99% of the time, based on personal experience, the person either doesn’t realize the difference or is just incorrectly using the term Cat5 to mean Cat5e. It’s pretty rare you’ll find the former even in older homes (again, my experience based on living in the US). This is why I intentionally used the term Cat5e in my reply. Cat5 was deprecated by Cat5e back 20+ years ago, long before the average US home began getting wired with Ethernet. Further, many (majority?) of Cat5 cables older than 10 years old actually meet the 5e requirements, just weren’t certified specifically.
> Cat5 struggles with 1gbps.
Like with my original point, that depends on the length and the quality of the connections. Inaccurate blanket statements mislead or worse, so I encourage you to avoid it.
1000baseT requires plain old category 5 for distances of up to 100m.
Most plain category 5 out there will have no problem with 2.5gbase-T at 30m and less.
(And, of course, most "cat 5" is actually "cat 5e".
P.S. - a lot of your recent comments are showing as dead, might want to email HN mods and see what’s up.
It has a steep learning curve though, albeit it's extremely rewarding and powerful once you gwr over that curve. It should handle routing 1 gig with zero issues, and is under $200. You can do bonding, vlans, esoteric ip rules, and tons of "misc" functionality.
Do not go with ubiquiti, their hardware is very poor and their UI is very buggy and simply poorly designed, it's focused on people who know a bit above an average person about networking, which I suspect is not the case for most people here.
Once you start doing much esoteric the speed slows down, if you get off the fast path it can be pretty intense (thought they do sell bigger ones that can route more packets).
The main thing is that the CPU in it is 1.5ghz quad core. Before that I had a Linksys with a 800mhz a single core that literally couldn't route traffic fast enough.
Running opnsense on it, and it’s doing fine and saturates the line when I’m maxing out downloads. For comparison, the isp (Verizon) router was consistently around 100Mb/s less than this one.
Router has had no problem pushing 1Gb and the switch is rated for something like 44 Gb. Has enough of a firewall and other built in services, plus POE for home devices and SFP+ ports so in the event you need a faster link. Average current draw is < 5 W and it's quiet.
Although nearly any modern mini-PC running Opnsense or VyOS or whatever linux/bsd can trivially do gigabit routing as well. 25 Gb would be a bit harder of an ask :)