Once that was done, I added my pi user to the Docker group: sudo usermod -aG docker pi To prep my Pi, I had to make sure I had Docker installed, so I followed the steps: wget -O get-docker.sh So I started looking into it, and found someone already did it for me-I found the maxandersen/internet-monitoring project on GitHub, and used that (though I made a slightly modified fork that works better on Raspberry Pi). Internet Monitoring on the Piįor the first task, I had plans to build a Prometheus and Grafana-based dashboard for metrics on the Pi, and run everything inside Docker containers. So to make remote access possible, I would have to find a way to have the Pi reach out to one of my servers with a persistent connection, then I could 'tunnel' through that server from other locations to reach the Pi.

The wrinkle with a Starlink-based Internet connection, though, is that SpaceX is using Carrier-Grade NAT (CGNAT) on their network, so there won't be any kind of IPv4 address I could reach the Pi at, nor does SpaceX yet have IPv6 set up in their network. I know the Starlink app has its own monitoring, but I like to have my own fancy independent monitoring in place too. recently I acquired a Starlink 'Dishy', and I'm going to be installing it at a rural location near where I live, but since it's a bit of a drive to get to it, I wanted to set up a Raspberry Pi to monitor the Starlink connection quality over time.

Raspberry pi fritz box traffic monitor