39

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 comment's thread
view the rest of the comments
[-] Haphazard9479@lemm.ee 3 points 1 year ago

How do you know the cable is damaged? If you have a toner you can hook the generator to the damaged pair and listen along the length of the cable to where the tone changes. It's not as fool-proof as a tester, but much cheaper.

[-] PlutoniumAcid@lemmy.world 4 points 1 year ago

I wanted to post a photo of my network tester but Lemmy gives me a JSON error.

Anyway, the tester is supposed to light up each strand one at a time, but what I get is disco fever.

[-] jake_jake_jake_@lemmy.world 2 points 1 year ago

short between pairs probably. tdr (time domain reflectometer) cable tester should help locate fault. might be pinched somewhere or something else

there are "casts" you can get to repair buried cable. usually used in copper telephone plant, i wouldn't trust it to certify to a gig but you could use it for a backup link or if you play with pots at some point. or "temporary repair"

[-] Bristlerock@kbin.social 1 points 1 year ago

Searched "tdr" before replying, and was inexplicably happy. :)

load more comments (2 replies)
load more comments (2 replies)
this post was submitted on 01 Sep 2023
39 points (97.6% liked)

Selfhosted

39677 readers
734 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