Fascinating that they chose to use modulated board-to-board Ethernet instead of just running RGMII from MAC to MAC.
I know exactly what power-constrained application you have in mind, Oleg, and I like it.
This was great. I wish Starlink actually provided a dish+modem service exactly like this and real IPv4 not CGNAT nonsense. I think they do for business plans which are much more expensive though.
How did the author figure out the pin out for Ethernet? Wild stuff.
Also kudos for them using GRPC. Suggests that there are some competent folks around not rushing things.
Archived version: https://archive.ph/UTFTK
[flagged]
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?