A bias tee module added inside the Starlink terminal, connected to the pads where a GPS antenna used to be wired

GPS Antenna Mods Make Starlink Terminal Immune To Jammers

The Starlink receivers need positioning and precise timing information to function, and currently the best way to get that information is to use a global navigation satellite system (GNSS) such as GPS. Unfortunately, the antenna used for this secondary satellite connection leaves something to be desired. Of course, when it comes to solving Starlink problems, there’s no one best than [Oleg Kutkov], whose duty is to fix and improve upon Starlink terminals used in Ukraine — and when the specific problem is GPS bands getting jammed by the invading military, you better believe that a fix is due.

[Oleg] sets the scene, walking us through the evolution of GPS circuitry on the Starlink terminals. Then he shows us the simplest mods you can do, like soldering an improved passive antenna in place of the chip antenna currently being used. Then, he takes it up a notch, and shows us how you could attach an active antenna by using a bias tee module, a mod that would surely work wonders on more than just this device! Then, he brings out the test result tables — and the differences are impressive, in that the Starlink terminals with active antenna mods were able to get GPS signal in areas with active jamming going on, while the unmodified ones could not.

The post is exceptionally accessible, and a must read for anyone wondering about GPS antenna reception problems in customer-accessible devices. This is not the only Starlink hardware mod we’ve seen [Oleg] make, we’ve just covered his Starlink Ethernet port restoration journey that meticulously fixes Ethernet connectivity oversights in the newer models, and the blog also has an article about powering Starlink terminals without the need for PoE, so, do check it out if you’re looking for more!

Pictures of the internals of the Starlink adapter

Restoring Starlink’s Missing Ethernet Ports

Internet connectivity in remote areas can be a challenge, but recently SpaceX’s Starlink has emerged as a viable solution for many spots on the globe — including the Ukrainian frontlines. Unfortunately, in 2021 Starlink released a new version of their hardware, cost-optimized to the point of losing some nice features such as the built-in Ethernet RJ45 (8P8C) port, and their proposed workaround has some fundamental problems to it. [Oleg Kutkov], known for fixing Starlink terminals in wartime conditions, has released three posts on investigating those problems and, in the end, bringing the RJ45 ports back.

Starlink now uses an SPX connector with a proprietary pinout that carries two Ethernet connections at once: one to the Dishy uplink, and another one for LAN, with only the Dishy uplink being used by default. If you want LAN Ethernet connectivity, they’d like you to buy an adapter that plugs in the middle of the Dishy-router connection. Not only is the adapter requirement a bother, especially in a country where shipping is impeded, the SPX connector is also seriously fragile and prone to a few disastrous failure modes, from moisture sensitivity to straight up bad factory soldering.

Continue reading “Restoring Starlink’s Missing Ethernet Ports”

Starlink’s Inter-Satellite Laser Links Are Setting New Record With 42 Million GB Per Day

Slide from the SpaceX Starlink presentation on mesh routing via the laser links. (Credit: PCMag/Michael Kan)
Slide from the SpaceX Starlink presentation on mesh routing via the laser links. (Credit: PCMag/Michael Kan)

Although laser communication in space is far from novel, its wide-scale deployment as seen with SpaceX’s Starlink satellite internet constellation has brought the technology to the forefront like never before. This was quite apparent during the SPIE Photonics West event on January 30th when [Michael Kan] and other journalists attended a presentation by SpaceX’s [Travis Brashears] on the inter-satellite laser communication performance that was first enabled with the Starlink v1.5 satellites.

Among currently active inter-satellite communication systems, Starlink is by far the most numerous and with the highest bandwidth, reaching over 42 PB per day across its over 9000 space lasers (yes, that is over 9000) for a 5.6 Tbps throughput. Since these satellites form a mesh network with their 100 Gbps laser transceivers, a big part of using it efficiently is to route any data with the least amount of latency while taking into account link distance (maximum of 5,400 km), link duration (up to multiple weeks) and presence of other Starlink satellites before they become within reach. With this complex mesh in LEO, this also means that a very high uptime can be accomplished, with a claimed 99.99% due to rapid route changing.

For the future, SpaceX has plans to not only keep upgrading its own Starlink satellites with better laser transceivers, but to also make them available to third-party satellites, as well as beam the lasers directly down to Earth for ground-based transceivers. The latter is still cutting edge, despite it being tested to beam cat videos to Earth from Deep Space.

Hackaday Links Column Banner

Hackaday Links: January 28, 2024

From the “No good deed goes unpunished” files, this week came news of a German programmer who probably wishes he had selected better clients. According to Heise Online (English translation), a freelance programmer — referred to only as “defendant” in the article — was retained by a company to look into a database problem in their system. His investigation revealed that the customer’s database was being filled with log messages from a third-party service called Modern Solution GmbH & Co. KG. over a MySQL connection to a remote server. Assuming this connection was dedicated for his client’s use, the programmer looked at the executable used to make the connection with a text editor, which revealed a password in plain text. Upon connecting to the remote database, he found that it not only contained data for all of Modern Solution’s customers, but also data for all the end users of their customers.

Realizing he’d unintentionally wandered into verboten territory, the programmer immediately backed out and contacted Modern Solutions. They quickly fixed the issue, and then just as quickly reported him to the police. Their “investigation” revealed that the programmer had “decompiled” the executable to obtain the password, in violation of German law. The judge agreed, stating that merely looking at and using the password constituted a criminal offense, regardless of intent and despite the fact that Modern Solution had provided the password to the programmer’s client when they sold them the software. The upshot of all of this nonsense? A €3,000 fine for the programmer, if the verdict stands on appeal. It could have been worse, though; German law allows for up to three years in prison for such offenses.

Continue reading “Hackaday Links: January 28, 2024”

Diving Into Starlink’s User Terminal Firmware

The average Starlink user probably doesn’t spend a lot of time thinking about their hardware after getting the dish aligned and wiring run. To security researchers, however, it’s another fascinating device to tinker with as they reverse-engineer the firmware and try to both find out what makes it tick, as well as how to break it. This is essentially the subject of [Carlo Ramponi]’s article over at Quarkslab as he digs into the firmware architecture and potential weaknesses in its internal communication.

The user terminal hardware itself is a quite standard AArch64 ARM-based SoC, along with the proprietary communication interface, all of which is controlled by the Linux-based firmware. Dumping the firmware itself was made easy thanks to existing work by researchers at the KU Leuven, involving dumping the contents of the onboard eMMC storage. After this the firmware architecture could be analyzed, which turned out to consist out of mostly C++-based binaries, but with a single big binary for the user front-end written in Go.

Communication between these processes is handled through a custom inter-process protocol called ‘Slate Sharing’, all of which is coordinated via the core User Terminal Control process. It are these Slate IPC messages which form the most likely attack surface for a fuzzing attack, with the SoftwareUpdateRequest command being an interesting target as it would seem to not require authentication since it doesn’t address a specific user. This work is part of [Carlo]’s master’s thesis, and should form the basis of further research on the Starlink User Terminal firmware.

China Plans Its Own Megaconstellation To Challenge Starlink

Satellite internet used to be a woeful thing. Early networks relied on satellites in geostationary orbits, with high latency and minimal bandwidth keeping user demand low. That was until Starlink came along, and provided high-speed, low-latency internet access using a fleet of thousands of satellites in Low Earth orbit.

Starlink has already ruffled feathers due to concerns around light pollution and space junk in particular. Now, it appears that China may be readying its own competing constellation to avoid being crowded out of low orbits by the increasingly-popular service.

Continue reading “China Plans Its Own Megaconstellation To Challenge Starlink”

Converting On-Grid Electronics To Off-Grid

Husband and wife team [Jason & Kara] hail from Canada, and in 2018, after building their own camper, sold up their remaining earthly goods and headed south. If you’re not aware of them, they documented their journey on their YouTube channel, showing many interesting skills and hacks along the way. The video we’re highlighting today shows a myriad of ways to power all the DC-consuming gadgets this they lug along with them.

LiFePO4 batteries are far superior to lead acid for mobile solar installations.

Their heavily modded F-550 truck houses 12kWh of LiFePO4 batteries and a 1.5kW retractable solar array, with a hefty inverter generating the needed AC power. They weren’t too happy with the conversion losses from piles of wall warts that all drained a little power, knowing that the inverter that fed them was also not 100% efficient. For example, a typical laptop power brick gets really hot in a short time, and that heat is waste. They decided to run as much as possible direct from the battery bank, through different DC-DC converter modules in an attempt to streamline the losses a little. Obviously, these are also not 100%

Home, sorry, truck automation system

efficient, but keeping the load off the inverter (and thus reducing dependency upon it, in the event of another failure) should help stem the losses a little. After all as [Jason] says, Watts saved are Watts earned, and all the little lossy loads add up to a considerable parasitic drain.

One illustration of this is their Starlink satellite internet system consumes about 60W when running from the inverter, but only 28W when running direct from DC. Over the course of 24 hours, that’s not far off 1kWh of savings, and if the sun isn’t shining, then that 12kWh battery isn’t going to stretch as far.

There are far too many hacks, tips, and illustrations of neat space and power-saving solutions everywhere, to write here. Those interested in self-build campers or hacking a commercial unit may pick up a trick or two.

Continue reading “Converting On-Grid Electronics To Off-Grid”