tychosmoose

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.

Ha! I was looking and didn't find him at first.

Kinda biased with only field players though. What about Schmeichel? Or Becker, who scored a winning goal? Or Tim Howard - a double threat with 1 goal and 3 assists. They should have some dots down near the intersection of x and y! 😂

8bitclassics.com seems to have some.

Or if you are feeling adventurous: https://retrocomputing.stackexchange.com/questions/13319/how-can-i-make-an-external-psu-for-an-apple-iic

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.

Fascinating

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.

Cca != CCA

The Cca standard relates to the flammability and toxicity of the materials used to jacket the cable. You can read about it here: https://cabling.crxconec.com/en/crx-blog/CRX-Blog-02.html

CCA stands for Copper Clad Aluminum. The actual conductors (each wire) is made from aluminum that has been given a thin coating of copper. This is what you want to avoid since it can be less durable and likely to have more voltage drop for PoE. It's unrelated to the Cca standard.

So assuming you are running this wire for a fixed installation, you should be looking for Cca + solid copper (not stranded). The one you linked to looks good.

Get shielding if it will be run near strong interference sources, and only if the shielding will be grounded.

Do you like birds? BirdNet-Pi might be interesting. https://github.com/alexbelgium/hassio-addons/blob/master/birdnet-pi/README.md

Mine has a Copy and a Share buttons like lemonmelon's. They both work in Chrome on Android, but only Copy seems to work on Firefox.

Same here

Interesting that the score recomputes as others play the day's game. My score improved when I went back to the page.

Word Grid #43
🟪🟪🟪
🟪🟪🟪
🟪🦄🟪
Rarity: 1.2
wordgrid.clevergoat.com 🐐