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.
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.
LibreNMS hasn’t been mentioned yet, and it’s very good. It does take some setting up, but its use of SNMP for data collection means that it’s easy to collect data from a wide range of network hardware as well. A wide range of alerting is available.
The WiFi icon with good connection+ exclamation on Android means the connection to the access point is good, but you don’t have a path to the internet. I would start by connecting a PC, wired, directly to your router. Make sure that’s working. If not, get some specifics on what’s failing and troubleshoot.
Then connect to the switch. Repeat. Then connect to an app, repeat.
Looks custom. It seems unlikely that Lenovo would offer this.
Run your fingernail across the transition in each direction. Is the carbon fiber part higher than the rubber coating, or lower?
I like LibreOffice Draw for this.
I use LibreNMS, which is a fork of Observium. It is primarily SNMP polling, so if you haven’t worked with SNMP before there can be a bit of a learning curve to get it set up. Once you get the basics working it’s pretty easy to add service monitoring, syslog collection, alerting and more. And since it’s SNMP you can monitor network hardware pretty easily as well as servers.
The dashboards aren’t as beautiful as some other options but there is lot to work with.
Monit works for me. Good basic monitoring solution that can also restart a service/interface.
I also use LibreNMS to do alerting for a variety of conditions (syslog events, sensor conditions, outages and services via nagios). But this is more work to get set up.
I tried draw.io, but ended up liking LibreOffice Draw better for hand-drawing.
If you want to get a live map of the connections on your network you may want to check out netdisco.org or librenms.org. Both are open source network management tools that have mapping.
Keep the tv dumb. Don’t connect it to the internet.
I like to check rtings.com for model specs and comparisons. Like, some panel types work well in a bright room, some work better than others when you are watching with a bright light source behind you. The warehouse clubs (Costco, BJ’s, Sam’s) tend to have good deals on midrange tvs.
Then pair it with a streaming stick of your choice. A generic Android TV stick/box would work.
Monit for simple stuff and daemon restart on failure. LibreNMS for SNMP polling, graphing, logging, & alerting.
Went through a lot of playback apps over the years, and Plexamp is definitely the best of them all. Reliable downloads, good quality, eq settings.
That and the shrinking ability to grant access to device storage. If that becomes an option only on rooted phones (which seems like the directly Google is heading) it will make the audience for such an app much smaller.