this post was submitted on 09 Aug 2024
141 points (83.4% liked)

Selfhosted

40219 readers
1150 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

After seeing that my wireless speeds were much faster than the speeds I was getting over Ethernet, I decided to invest in some new cables. I didn't know it before, but I saw while I was changing them out that my current cables were Cat 5e. While putting my network together, I had just been grabbing whatever cables I could find in my scrap drawers. Now I have Cat 8 cables and my speeds jumped from 7MB/s to an average of over 40MB/s. It's a much bigger improvement than I expected, especially for such a small investment.

you are viewing a single comment's thread
view the rest of the comments
[–] IsoKiero@sopuli.xyz 30 points 3 months ago (2 children)

Yep. I'm running 1/1Gbps wan connection over cat5e just fine. Even on very noisy environment at work with a longish run (70+ meters) we ran pretty damn stable 1/1Gbps over good quality cat7.

[–] LastoftheDinosaurs@reddthat.com 6 points 3 months ago (1 children)

I tried running a 1/1Gbps connection over Cat5e at home too, but for some reason, I couldn’t get it to connect properly. Ended up switching to Cat6, and it finally stabilized. I’m still scratching my head over why the Cat5e didn’t work as expected.

[–] IsoKiero@sopuli.xyz 6 points 3 months ago

At work where cable runs are usually made by maintenance people the most common problem is poor termination. They often just crimp a connector instead of using patch panels/sockets and unwind too much of the cable before connector which causes all kinds of problems. With proper termination problems usually go away.

But it can be a ton of other stuff too. Good cable tester is pretty much essential to figure out what's going on. I'm using 1st gen version of Pocketethernet and it's been pretty handy, but there's a ton of those available, just get something a bit better than a simple indicator with blinking leds which can only indicate if the cable isn't completely broken.

[–] mjhelto@lemm.ee 1 points 3 months ago (1 children)

Wonder if the cables replaced by OP were user-made, not commercial cables, that were our together incorrectly.

[–] anonymouse2@sh.itjust.works 4 points 3 months ago (1 children)

They had been collected from various ISP provided modems and routers I've purchased over the years.

[–] IsoKiero@sopuli.xyz 11 points 3 months ago

At least in here some of the older modems, specially from ADSL-era, only had two pairs in them, so they were only good up to 100Base-T, which is roughly 7MB/s. So maybe check if that's the case and throw those into recycling bin.