It’s running both PiHole and DAKBoard with no problem at all. CPU and memory are at around 50% at peak traffic.

Good tip! That’s the next part, optimizing the network. But for me, that’s the fun part TBH.

While I wait for my new hardware, I have since setup my Pi as a router/firewall behind my existing WiFi routers in AP mode, so I can at least monitor web traffic. It’s a bottleneck for sure but will at least help me better determine WTF is going on while I get the final solution setup.

I’ll follow up with what I find, if anything.

Because of my shit network (again, totally my fault) it was difficult to say what specifically was happening other than some device on the network went haywire. It could have been the router for all I know. It can happen if a device gets stuck in some sort of trying to update loop. They can hammer the network with requests. At least that’s my guess of what happened.

Good to know! I didn’t think the opener worked with the RAX120 chipset but it appears I was wrong. I guess I’ll keep that PoS around and at least play with it a bit. Thanks!