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

help-circle



  • My various servers, firewall and nas are relatively power optimized. Everything including switches (most with some 10g ports) and access points is 160 W or so combined. I can’t give you monthly usage, as I’ve got solar+battery so it’s frequently just 0 kWh for some days. It’s also rather hard to separate from the other power usage in the house when solar doesn’t fit cover it.


  • I will use it until it stops being viable. This used to mean “until the battery dies”, but I’ve also swapped batteries in phones not designed for it, and still had to get a new one as the batteries available weren’t OEM and so bad they basically didn’t work despite being new. Like phone always just turns off at like 40% charge. That isn’t “viable” in my eyes.

    Now I’ve got a Fairphone 5. It’s only been a few years, but I’m planning on 10+ years if I can make it happen. In theory some new feature could get me to buy one sooner, but I highly doubt it. Hasn’t happened in the past either.





  • Lemmy has relatively good search, usually if you remember bits of the title that works?

    In any case: Both n100/n150 and raspi are in the <10W range. Obviously raspi is lower, but also A LOT slower and much worse connectivity. As the price is roughly comparable, I’d go for the much more capable N100/N150. Only go the full ‘minipc’ route if you don’t mind the (probably) higher power usage, which can depend highly on model. Older (but cheap on eBay) models can be 25W on idle.

    Depending on what you actually need, I’d setup a Sync thing or NextCloud or something and go from there.


  • A VPS is like 5 bucks. Which isn’t nothing but when used as a redundancy or place to send (reasonably sized) backups, it’s cheaper than most alternatives. It’s also still a form of “self hosting”, at least for me.

    Exporting, maybe on a schedule, to a keepass to keep somewhere, also works of course. But when hosting the only/main instance at home you’ll have at least one single point of failure, most likely many. Internet connection, server, network/switches, …









  • Until very recently, I exclusively used the /56 prefix I get from my ISP exclusively. This is still relatively annoying in my case as this prefix changes at least daily for some reason. Clients get their IP via SLAAC.

    I’ve added ULA literally less than a week ago as I have a local reverse proxy I want to handle both local and external request, in both v6 and v4. Obviously more hosts should be accessible from local clients. But I can’t tell local clients apart except by IP, and since the prefix is unstable this would require some sort of hook to update the proxy with that new prefix (might be possible, but seems like a real hassle). So here we are.