As an example, I was setting up SnapCast on a Debian LXC. It is supposed to stream whatever goes into a named pipe in the /tmp directory. However, recent versions of Debian do NOT allow other processes to write to named pipes in /tmp.

It took just a little searching to find this out after quite a bit of fussing about changing permissions and sudoing to try to funnel random noise into this named pipe. After that, a bit of time to find the config files and change it to someplace that would work.

Setting up the RPi clients with a PirateAudio DAC and SnapCast client also took some fiddling. Once I had it figured out on the first one, I could use the history stack to follow the same steps on the second and third clients. None of this stuff was documented anywhere, even though I would think that a top use of an RPi Zero with that DAC would be for SnapCast.

The point is that it seems like every single service has these little undocumented quirks that you just have to figure out for yourself. I have 35 years of experience as an “IT Guy”, although mostly as a programmer. But I remember working HP-UX 9.0 systems, so I’ve been doing this for a while.

I really don’t know how people without a similar level of experience can even begin to cope.

Why is Bunsen Honeydew running the simulation?

I have an HP T740 running Opnsense and it works just fine. You can pick them up for about $100 USD, and they seem to come mostly with 8GB RAM, and a 64GB SSD. That seems to be more than enough for Opnsense, even running VPN’s.

These are just a tad larger than my Lenovo M910Q Tiny servers, but they have a PCI slot, so you can put a second ethernet port (or 2, or 4) of whatever speed you like in it.