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!)

@PlutoniumAcid@lemmy.world
creator
link
fedilink
English
41Y

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.

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
link
fedilink
11Y

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

@Haphazard9479@lemm.ee
link
fedilink
English
31Y

I assume the disco fever is all the pairs shorted together. Is this cable buried or run through the house? I would start by redoing your ends. Make sure they are crimped fully and both sides are identical.

@jrburkh@lemmy.world
link
fedilink
English
21Y

I agree. If that doesn’t work, I’d give the whole line a visual inspection for any more obvious signs of damage. If that doesn’t work there are other options to troubleshoot, but I’d probably just replace the line and attempt to recycle the old cord into shorter lines for device connections, patching, etc.

Create a 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!

  • 1 user online
  • 279 users / day
  • 589 users / week
  • 1.34K users / month
  • 4.55K users / 6 months
  • 1 subscriber
  • 3.5K Posts
  • 70K Comments
  • Modlog