I mean, the simplest answer is to lay a new cable, and that is definitely what I am going to do - that’s not my question.

But this is a long run, and it would be neat if I could salvage some of that cable. How can I discover where the cable is damaged?

One stupid solution would be to halve the cable and crimp each end, and then test each new cable. Repeat iteratively. I would end up with a few broken cables and a bunch of tested cables, but they might be short.

How do the pro’s do this? (Short of throwing the whole thing away!)

You are viewing a single thread.
View all comments
12 points
*

You can only do 100M runs max anyways, just replace the whole thing? 100M of CAT6 is pretty cheap if you already have a box for it.

Or is this an academic question?

permalink
report
reply
7 points

Actual, not academic. And I agree that a new cable is cheap, which is what I will do. My question is about avoiding throwing a mostly good cable in the trash.

permalink
report
parent
reply
3 points
*

Pull it, cut into quarters. Add jacks to each end and test the lines.

Nvm, I see you suggested this…

permalink
report
parent
reply
-4 points

What is an M? Miles? That doesn’t seem right.

permalink
report
parent
reply
0 points

M = meters. Mi = miles

permalink
report
parent
reply
4 points

m = meters. M = mega (x 1 000 000).

That’s why Km is 1 thousand meters and Mm is 1 million meters.

The actual unit is lower case, the multiplier is uppercase.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

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!

Community stats

  • 5K

    Monthly active users

  • 3.6K

    Posts

  • 81K

    Comments