• 1 Post
  • 24 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle
  • Here’s my messy-cabled 9u rack.

    Image

    It has:

    • Fiber gateway out of view on top of the rack.
    • Switch, which also powers 2 Ruckus APs and 2 other switches.
    • Mikrotik RB5009 router.
    • Raspberry Pi x3 all running Debian Bookworm. I have too many pis right now, running Home Assistant, LibreNMS, Log collection, and a read-only NUT server that orchestrates shutdowns and startups on power loss. I need to consolidate these.
    • 1L PCs. One is on Debian serving media and files. The other is a test server where I’m trying out Immich on openSUSE. I’m considering moving to that and rootless podman for services. To that end I have another of these 1L boxes on my desk trying other options (MicroOS, Fedora IoT, maybe others).
    • HDs. These are backup drives for the 1L server. I keep them powered off except when needed.
    • UPS and a managed, switched PDU.

    Everything is set up for low energy consumption (~90w), remote admin, and recovery from power loss.



  • If you’re buying new cameras they’ll be 802.3af PoE. Passive is becoming much less common. So that model router I linked would work great.

    I think if you’re a moderately technically inclined person you would be happy with that solution. If you are intimidated at the idea of writing or adapting some scripts, I would probably recommend a router on one of the other platforms plus a PoE switch.


  • The easiest part of your requirements are the custom DNS records. All of the platforms recommended so far can do this. OpenWRT has the advantage of WiFi capabilities. If you want the router to also be your WiFi access point then it may be your best option. But it sounds like you only need it to be a wired router, which is good.

    As far as the ad blocking, I have done this with pi-hole, and with the built-in DNS and block capabilities of OpenWRT, Mikrotik and OPNSense. They are all fine. The router ones don’t have the fancy web UI like pi-hole. So if you use that a lot you will be disappointed. Mikrotik’s is the most basic and a new feature for them, but they are actively developing it. Plus their current routers can run containers, so you can run pi-hole on the router as a container if you want.

    PoE ports as a requirement is what narrows your options considerably I think. You could get that from a separate switch. If you want that in the router itself then you have very few options.

    Mikrotik has a lot of routers with PoE out. Their newest model in the RB5009 series can do either passive or 802.3af/at PoE out. Many of their older routers have passive PoE only. Make sure you know what your cameras need.

    I had similar requirements as you and got this: https://mikrotik.com/product/rb5009upr_s_in

    It has PoE out available on all 8 Ethernet ports. The default 48v power supply works with 802.3af/at PoE. It is a 96 watt supply, and can support ~76 watts of PoE downstream. If you need passive PoE then you would need to change to a 24v power supply.

    Mikrotik RouterOS requires some learning to use its advanced features, but their quick setup defaults are good. And the platform is super reliable and flexible.

    For DNS you would use their Adlist functionality along with a script similar to the one from BartoszP in this thread to enable DNS name resolution for lan hosts: https://forum.mikrotik.com/viewtopic.php?t=181640. That script is added to the DHCP server config to run when each client gets an address lease. And then you would add static name records in IP / DNS / Static for the other host.domain names you want your lan devices to connect to by name which can’t be resolved via your upstream DNS server.


  • Darktable is fantastic, but the learning curve is steep for great results. It took us months to get comfortable with it after using Capture One, Lightroom, Photoshop/ACR. It’s different. Our first efforts looked like crap.

    For someone processing just a few files I think RawTherapee is probably easier and likely to give better results with limited effort.



  • Yeah, I get what you’re saying. Definitely. It’s not complicated for one pair of speakers in one room. For one music source. For one person controlling it.

    There just haven’t been any better cost-effective solutions with multi-room, control from your any phone convenience. And that’s a big plus for how we listen to music. Today there are a few contenders, but many of them are also cloud dependent. Really the small number of good options in this space is proof of how good Sonos was for a long time. Well and also of Spotify causing people ditch the idea of a offline digital music library.

    Edit: And to be clear, aside from the “any computer networks” part, this is what the original Sonos device did. It could work without a home network, but worked best with a shared music library on a PC. Didn’t need cloud anything, internet connection, account, etc. You just hooked your normal speakers to it and it played music.



  • That SATA port is what you need. You can use that to connect an external eSATA drive enclosure (external jbod).

    For a clean install, get a SATA to eSATA adapter - the kind with an expansion slot plate. Something like a STCESATAPLT1LP. Unscrew the eSATA end from the plate, cut a matching hole in the PC case and mount the port to the hole. This is better than going straight from the internal port in my opinion.

    It looks like you have a mini-PCIe slot as well, probably intended for WiFi. That may work with an mSATA to SATA adapter to give you a second port. Or it may work with an mSATA SSD. I would test with something cheap or get confirmation it works from other users of this PC before investing in an expensive SSD.


  • VPN + DDNS is what I do. You may be thinking about the perf hit of putting all your home connections through a VPN. That’s not the idea here. For self hosted services you would set up a wireguard “server” at your house. Then you connect your phone back to it to access your services.

    With Wireguard it’s pretty easy to do a split tunnel, so that the VPN connection is only used for traffic to your home servers. Nothing else is affected, and you have access to your house all the time.

    This is better for security than DDNS + open ports, because you only need a single open UDP port. Port scanners won’t see that you are hosting services and you wouldn’t need to build mitigations for service-specific attacks.

    As far as podman, I am migrating to it from a mix of native and docker services. I agree with others that getting things set up with Docker first will be easier. But having podman as an end goal is good. Daemonless and rootless are big benefits. As are being able to manage it as systemd units via quadlets.