Comment by chatmasta
Comment by chatmasta 13 hours ago
I’m confused by the end. He implies that the “disablement codes” (geoblock, speed violation, etc.) are enforced by the user terminal, meaning they could be circumvented?
> The user terminal itself has no knowledge of service plans, countries, regional, or velocity restrictions – it simply follows commands received from the Starlink satellite
Surely this would be enforced at DHCP time? Or maybe not, since you could get an IP address then start going too fast… is this blog actually a ”wink wink nudge nudge” guide to bypassing Starlink policy restrictions?
I'm not that familiar with Starlink but it looks like the normal process is to use an app that can read off error and diagnostic codes from the terminal. If you are bypassing the built-in router and just using the terminal as a modem connected to an SBC, you won't have a smartphone connected to see these errors. You could write up a script to check the error codes and respond accordingly.
Like if you have a Starlink terminal attached to a drone, it could automatically change its location if service is interrupted, like a UAV could fly higher if an obstruction is detected. Or if a geofence is inadvertently crossed and service is disrupted, it could turn off the Starlink terminal and then turn on a backup comms system. Essentially, you could use those disablement codes as a sensor.