• 0 Posts
  • 7 Comments
Joined 3 years ago
cake
Cake day: June 18th, 2023

help-circle


  • Hardware routers can be killed for many reasons. Age and an inability to upgrade them to suit current needs is the biggest one. OEM’s do this fairly quickly as they build devices with the resources to work for today and maybe tomorrow. After their product is no longer made they want it to be obsolete not long after so they can claim they can support is no longer viable. Then you but another router and they make money.

    OpenWRT tries to augment and support devices for as long as possible but at the same time the hardware limitations still exist and often the storage will no longer support the latest version due to the size of the new version.

    As far as when that will happen depends on multiple factors that have the ability to change at any time. There viable be a massive flaw in a portion of the software that requires a huge rewrite and the addition of code that will make the software too large to fit.

    Sometimes someone will create a version with less used features available so that it can still be used but it’s a losing battle

    If you want true longevity repurpose an old computer into a router. OpnSense is what I use and recommend. Add in something like a TP-Link EAP650 or two and you have a rock solid platform that can handle a lot more and last much longer. Add Power Over Ethernet (POE) along with an Omada controller and you can position the AP in a place where it will work the best for your use. You can have enough access points to have a full signal anywhere even if your place is the size of the Louvre. When new technology comes out you can upgrade the AP’s as needed when needed and upgrade the router as well in a similar fashion.


  • It’s something I’ve wanted to do for a while. Honestly I want to host a Lemmy instance and my own peertube instance.

    Two things are stopping me. I don’t understand certain points of how things interact in the software or how to set it up properly to self host and be comfortable in it’s security. I barely understand docker and some other stuff. It sucks because I understood how to use DOS at an around 14 by reading the manual. I also don’t have the funding to do so in a way that I would feel comfortable at this point. I don’t fully trust co-mingling my home services with web services due to the security risks.




  • The cable connections don’t mean anything. SAS is multichannel and with expanders (expanders work like ethernet switches) one controller can interface with hundreds of drives.

    The cable you have pictured is called a breakout cable that dedicates one of the cards individual channels to a drive. If you plug one drive into the cable and spin it up no big deal, add another later on same thing, move a dive from one cable to the other it’s all good. The cables are just electrical data connections to the controller. With ZFS you can even migrate compatible drives from SAS to SATA controllers (SAS only work on SAS, but sata works on either) in the system and they will still function just fine in a pool. For that matter I’ve heard of people mixing SAS, SATA, and USB drives in the same vDev (not generally recommended) and things worked.