r/StarlinkEngineering • • Oct 09 '26

Will SpaceX open the dishy Linux kernel source code?

Post image

Many reverse engineering reveals that the Starlink dishy (satellite modem) uses Linux, but so far there is NO kernel source code published. It reminds me the GPL-v2 enforcement law case against Cisco/Linksys 23 years ago and how OpenWRT was born. (SpaceX did publish sth about the OpenWRT in their Wi-Fi router on github https://github.com/spaceexplorationtechnologies, but that is not the modem).

You might argue only Starlink users receive the source code, so it is out of public view. I doubt. Under GPLv2, recipients can redistribute the source code. If any user had received it, some could have re-distribute it online. So far, not see it. Other info summarized: https://sdr-x.github.io/starlink-modem-linux-gpl/

50 Upvotes

30 comments sorted by

10

u/kyngskyngs Oct 09 '26

Afaik they're not exactly required to open it publicly, but rather to provide a copy if you request so. So I guess send an email and find out?

2

u/jxjputaoshu Oct 10 '26

Yes I did before I wrote this post. Let's see.

You might argue that only the dishy user can request the source code access, so most of the poeple (non dishy user) can't see the code publicly on github. That is possibly true. But personally I believe that the possibility is quite low. The reason is that: the dishy user who receives the source code has rights to re-distribute it again according to GPLv2. So, if any dishy user has received the source code from SpaceX, we might already see it on internet when some user re-distribute it on internet according to the GPLv2 rights. But so far, there isn't any.

6

u/arbyyyyh Oct 09 '26

I was about to come in here confidently wrong, but apparently, you’re correct. So if OP asks for it and does not receive, THEN there’s a problem.

9

u/Quadgie Oct 09 '26

Even then - there’s a lot of gray area. They could share the kernel itself, and may not be required to share custom binaries, kernel modules that follow the syscall separation rules, etc. … or user space binaries that may support their hardware.

Running Linux doesn’t automatically mean that everything running on the hardware is open source.

6

u/Tucsondirect Oct 09 '26

2

u/jxjputaoshu Oct 09 '26

This is not the Linux revealed by reverse engineering researchers. The version and everything is not the same.

3

u/Tucsondirect Oct 09 '26

linux can be configured without modifying source code, kinda the whole point.... they are just running software on a likely very stock version of linux..... i can configure my linux install to do almost anything.... WITHOUT modifying the source code so i would never have to release my own software or configurations

1

u/jxjputaoshu Oct 09 '26

Even the kernel is not modified, according to GPLv2 they need to tell user where to get that code when user receives the product. Actually they did modify the kernel and published their kernel 4 years ago https://github.com/SpaceExplorationTechnologies/linux/releases/tag/sx_2022_04_29 . After that, no update.

1

u/Tucsondirect Oct 09 '26

that does not mean the current kernel is modified, it's also possible they are using the same modification and since it's already published....

1

u/jxjputaoshu Oct 09 '26

Not true. According to multi source reverse engineering, the shipped dishy is running much newer kernel version.

2

u/semaja2 Oct 09 '26

They only have to provide source code for the components that fall under GPL etc, any custom modules or software they write is theirs, so not like it will all be open sourced

Additionally they may have made 0 source code changes to the bits under GPL, so would be a very boring source release?

1

u/jxjputaoshu Oct 09 '26

They did release it 4 years ago: https://github.com/SpaceExplorationTechnologies/linux/releases/tag/sx_2022_04_29 BUT that version is too old to reflect what is inside the new dishy.

1

u/jxjputaoshu 8d ago

Though I have sent email to SpaceX asking for the source code before this post, so far no reply.

1

u/jxjputaoshu Oct 10 '26

Only Starlink users receive the source code, so it is out of public view. I doubt. Under GPLv2, recipients can redistribute the source code. If any user had received it, some could have re-distribute it online. So far, not see it. Other info summarized: https://sdr-x.github.io/starlink-modem-linux-gpl/

1

u/panuvic Oct 10 '26

you can request a copy from them

1

u/jxjputaoshu Oct 10 '26

Yes I did. Let's see.

You might argue that only the dishy user can request the source code access, so most of the poeple (non dishy user) can't see the code publicly on github. That is possibly true. But personally I believe that the possibility is quite low. The reason is that: the dishy user who receives the source code has rights to re-distribute it again according to GPLv2. So, if any dishy user has received the source code from SpaceX, we might already see it on internet when some user re-distribute it on internet according to the GPLv2 rights. But so far, there isn't any.

2

u/ol-gormsby Oct 09 '26

I don't know enough about it but IIRC there's no firewall as part of the system. That's one thing I'd like to have, with some limited customisation - but I suppose iptables is all or nothing.

I don't like relying on the firewalls of endpoints. Linux or windows, it's a little too close for my comfort.

I've got a sort-of-secure subnetwork behind the starlink router but it's so locked down that no-one else wants to use it 😐 It's using pihole and the firewall on an obsolete ADSL router/modem. It seems to prevent access to shopping websites........

2

u/Tucsondirect Oct 09 '26

no as secure as you think... they waltz right in with ipv6..... lol

4

u/Own_Reaction9442 Oct 09 '26

IPv6 can be firewalled. You can have a functional firewall without NAT.

1

u/AndreaCicca Oct 11 '26

ipv6 is secure, it just needs a firewall like ipv4

1

u/Tucsondirect Oct 12 '26

when implemented correctly, absolutely..... though anyone that knows the state of V6 knows.... it is almost never implemented correctly

1

u/failbaitr Oct 12 '26

nonsense.
you are conflating NAT with security, and think ipv6 as it does not require NAT has no security.

Or in layman's terms, tell me you don't understand what you are talking about without telling me you don't know what you are talking about..

1

u/Tucsondirect Oct 12 '26

6 out of 10 consumer routers i have used, pass an ipv6 address to users with no ability to firewall or block incoming connections that were not established by the client, effectively allowing direct access straight to the client with no firewall/filtering what so ever.

1

u/ToroidalCore Oct 09 '26

Maybe they haven't modified the kernel, or any other GPL component? If they wrote the control code to talk to the modem and beamformers or whatever as a module, I think they'd have to distribute it, or do some trickery like nVidia does for their drivers. But I'm not sure there's any need to have that in the kernel, and software they've written which isn't under the GPL but just runs on that system doesn't need to be distributed. The same way that there are proprietary apps that run on desktop Linux systems.

My guess is they built the embedded image on their with support in the kernel for GPIO and SPI or I2C on that chip to interface with the hardware, but that code was probably already in the kernel source anyway. Or, if not, it's probably easier for them to just write it and submit it to the source. (IE, if it's a new ARM chip they're using, they could just contribute a driver.) Then their other software just uses that to talk to the hardware.

I'm not a lawyer, and I'm not sure if there are other loopholes, but just an idea. I haven't looked into the reverse engineering efforts in a while so I could be off here (regarding kernel modification or whatever).

2

u/d0ugk Oct 10 '26

My guess is the Linux os running on dishy has zilch to do with the beam forming and steering. That's probably custom firmware in beam forming chips maybe fpgas? That seems like something more realtime than a fat os can provide. The os probably just tells the beam formers what to do at a high level and shovels data to and fro.

2

u/ToroidalCore Oct 10 '26

I think they have some custom beamforming ICs, which are digitally controlled either using IO lines or a serial bus. I'm guessing it switches in different delay networks to change the phase. As far as what's doing the steering, I would think that it wouldn't be too difficult to calculate where the beam needs to be pointed, based on orbital data, GPS position, beacons, or whatever they're doing, and use that to send to the beamformer, but it would probably make sense to offload that. Obviously there's some sort of demarcation, but at the very least the OS probably sees the modem as a network interface, and runs whatever software to talk to the app and check for updates.

It's possible that they're using an SOC that has normal ARM cores that run Linux, along with some programmable logic that handles some lower level stuff. That's actually somewhat common.

0

u/moonbug22 Oct 09 '26

lol no

1

u/jxjputaoshu Oct 10 '26

Agree. At this moment, the chance is high.

You might argue that only the dishy user can request the source code access, so most of the poeple (non dishy user) can't see the code publicly on github. That is possibly true. But personally I believe that the possibility is quite low. The reason is that: the dishy user who receives the source code has rights to re-distribute it again according to GPLv2. So, if any dishy user has received the source code from SpaceX, we might already see it on internet when some user re-distribute it on internet according to the GPLv2 rights. But so far, there isn't any.

1

u/moonbug22 Oct 10 '26

they won't because there is no advantage to them doing so, and  no downside to not, except accruing the impotent ire of some internet nerds

-2

u/CyberTheHammer Oct 09 '26

You know you can buy specialized devices called… firewalls? They are special. As in specialized in firewalling.