Case study
starlink-rs: Starlink dish gRPC definitions and client
starlink-rs reconstructs Protobuf definitions exposed through a Starlink user terminal's gRPC server reflection and implements a Rust client for the dish. Its examples exercise request and response handling and bidirectional streaming over the local HTTP/2 endpoint.
- Targets
- Protocol
- Category
- Independent reconstruction cases
- Relationship
- Independent reconstruction project
- Sources reviewed
- Stars
- 46
- Last commit
- 2023-12-14
- Language
- Rust
- License (GitHub)
- Apache-2.0
GitHub data as of 2026-11-09
Requirements & limits
- Prerequisites: Access to a Starlink dish's local gRPC endpoint at 192.168.100.1:9200.
- Limits: The author describes the recovered Protobuf definitions as probably still flawed.
- License: Licensed under MIT or Apache-2.0, at the user's option.
Cite
BibTeX
@misc{starlink-rs-case,
title = {{starlink-rs: Starlink dish gRPC definitions and client}},
howpublished = {\url{https://github.com/ewilken/starlink-rs}},
url = {https://github.com/ewilken/starlink-rs},
urldate = {2026-11-06},
note = {Awesome REA entry: \url{https://awesomerea.org/resources/starlink-rs-case/}}
}Plain text
starlink-rs: Starlink dish gRPC definitions and client. https://github.com/ewilken/starlink-rs (accessed 2026-11-06). Awesome REA entry: https://awesomerea.org/resources/starlink-rs-case/
Useful? Star Awesome REA on GitHub2.4k
About this entry
The description was reviewed against primary sources.
Primary sources
- README.md GitHub · ewilken/starlink-rs · Revision 7fb3fbd
- codegen/static/README.md GitHub · ewilken/starlink-rs · Revision 7fb3fbd
More in Protocols
- Acurite 00592TX Decoder: decoding wireless sensor messages · Case study
- Mazda MX-5 CAN DBC: inferred HS-CAN and MS-CAN signals · Case study
- DavisRFM69: receiving the reverse-engineered Davis ISS radio protocol · Case study
- CarHack: mapping 2010 Nissan Sentra CAN messages · Case study
- HU-058D WiFi clock: reconstructing its LED display interface · Case study
- A-OK: reconstructing a 433.92 MHz remote-control protocol · Case study