For the record it turned out to be because I hadn’t set write permissions to the hardware for my user because ChatGPT told me I only needed read permissions to be set up. This must be the first time since its conception that AI’s made a mistake.

Not rootless but I can see the device, and even in privileged mode it doesn’t work. I’m currently trying to find a docker image I can run as root and prove the Coral is working.

I’ve been trying to get Frigate working, on and off, for about eight months now. I’ve got a Debian server but it just won’t detect my Coral TPU inside my Podman container. Since you need such an old version of Python to test the TOU I can’t prove it’s working in the host so I don’t know if the problem’s with the drivers of either my container setup. I vowed to get it working over the Christmas break but it’s still not there.

How’d you get Haswell working? I run vainfo and it complains that it can’t recognise the chip but I’ve followed everything on the Debian wiki. When I google the error all I get is people complaining about it being the result of a bug and the responses are usually from developers promising to look into it.

I don’t know half that software you’re talking about running but I don’t find home servers really need to be that powerful. Companies like Dell and Lenovo have historically done cash back offers on small tower servers. I’m still running a Dell T20 I got like 10 years ago. Maybe keep an eye out for something like that if you’re not in a rush. I only ended up paying about £100 for mine.

What was wrong with Joplin? I was thinking about giving it a try.

This can’t feasibly be done over the internet. An IP address must be unique as that’s how it finds it out of billions of other devices. There are situations where the same IP can route to different locations but that’s regional and way beyond what you’re trying to achieve here. It’s how something like 8.8.8.8 works without sending all the requests to a single location.

If your server is sending out traffic as 1.2.3.4 and then tries to send the encrypted traffic to the client at 1.2.3.4 the traffic would either be routed back to itself or the client would receive the plaintext traffic meant for the server.