alt Hacker NewsI’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?
Replies
He’s saying the sat sends the code to the terminal because the terminal doesn’t even know it’s blocked. This is so you as a user can see why your internet isn’t working.
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.
If they actually figured out which disablement codes can be tricked or circumvented, they wouldn’t share that. I guess it would all depend on how strict Starlink checks and enforces for unauthorised usage. For a US company operating on this scale I wouldn’t be surprised if it’s between very strict to just the basics or on demand.
A commentator here mentioned that Starlink also works in Russia, which it shouldn’t? Maybe some devices delivered to Ukraine can be used in Russia too.
That's not my impression at all, if the terminal does not maintain information on service plans or restrictions then it's maintained higher up. We don't have enough information from this blog post to know if the terminal could be configured to ignore limitations but I would expect just ignoring "disablementCode"s wouldn't be sufficient.
Probably it works like all other ISPs and terminal is in a VLAN?
It sounds more like a result-code shared to the terminal to inform it that i.e. "ACCOUNT_DISABLED - The Starlink account has been suspended or permanently disabled" or "UNLICENSED_COUNTRY – The terminal is located in a country where Starlink lacks regulatory approval."
I doubt that the decision to act upon that is left to the terminal instead of the Starlink network.