• slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    22
    arrow-down
    3
    ·
    7 months ago

    It was only a particular kind of RJ45 boot that caused the issue, so if you are sensible and don’t use a cable boot you never ran into the issue.

    • dfyxA
      link
      fedilink
      arrow-up
      25
      arrow-down
      1
      ·
      7 months ago

      Just saying, this is not the fault of a single engineer but of a whole company that didn’t think “try all common cable types” should be a required testing step before a network switch goes into mass production.

    • Empricorn@feddit.nl
      link
      fedilink
      English
      arrow-up
      9
      ·
      edit-2
      7 months ago

      if you are sensible and don’t use a cable boot you never ran into the issue.

      Uh… huh? What, you’re anti-boot?

    • yuri@pawb.social
      link
      fedilink
      arrow-up
      5
      ·
      7 months ago

      i choose to believe this particular engineer saw the potential for this issue, but just hated those cables with a burning passion.

    • Rob Bos@lemmy.ca
      link
      fedilink
      English
      arrow-up
      4
      ·
      7 months ago

      I could see it also being a problem if you’re trying to remove a cable with a stuck latch. Wiggle it around a bit, accidentally hold down the button… oops