Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Oleg Kutkov <contact@olegkutkov.me>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink cheaper in Colombia,cand gps spoofing
Date: Sun, 1 Jan 2023 19:17:48 +0200	[thread overview]
Message-ID: <4b18869c-1a68-1a16-ec59-59214eef98db@olegkutkov.me> (raw)
In-Reply-To: <895ff23b-a263-4cf1-abf5-d403a63e5b0c@Spark>

[-- Attachment #1: Type: text/plain, Size: 2958 bytes --]

There is also interesting behavior. If you physically disconnect the 
Starlink GNSS receiver from the SoC, it still connects to the Starlink 
satellites, but it takes up to 20-25 minutes. It looks like there is 
some fallback mechanism, like RF sync on their own satellites.

But for normal operation, they use GNSS (GPS + Galileo) to set the 
system time faster.

On 1/1/23 19:09, Mike Puchol via Starlink wrote:
> I can confirm that spoofing with “non-milspec” methods don’t seem to 
> work against the receiver in the Starlink terminal. I tried with a 
> HackRF and a USRP and it didn’t work, while an Android phone was 
> spoofed fine. I was however able to jam the receiver with very 
> moderate power levels and a sweep generated with a HackRF Portapack 
> and patch antenna.
>
> Best,
>
> Mike
> On Jan 1, 2023 at 17:23 +0100, Benjamin Henrion via Starlink 
> <starlink@lists.bufferbloat.net>, wrote:
>> Le dim. 1 janv. 2023 à 12:49, Oleg Kutkov via Starlink 
>> <starlink@lists.bufferbloat.net> a écrit :
>>
>>     Hi,
>>
>>     Starlink has a multisystem GNSS receiver with data filtering, so it
>>     can't be fooled with the single HackRF (i tested it).
>>
>>
>> Here they describe another method with gps jammers:
>>
>> https://gpspatron.com/spoofing-a-multi-band-rtk-gnss-receiver-with-hackrf-one-and-gnss-jammer/
>>
>>
>>     I experimented with NMEA data injected directly into the Dishy
>>     operating
>>     system, so I can tell there is no way to cheat the system.
>>     Satellites know your location a wouldn't accept a connection from the
>>     client in an unexpected Cell. All connection slots for all
>>     clients and
>>     areas are scheduled.
>>
>>     Besides this, Starlink requires valid and strict GNSS and 1PPS to
>>     sync
>>     the local clock, that's vital for the TDD system.
>>
>>
>>     On 1/1/23 13:18, Benjamin Henrion via Starlink wrote:
>>     > Hi,
>>     >
>>     > Just wondering if you could pay less by pretending to be in
>>     Colombia
>>     > by spoofing gps sats with a HackRF board:
>>     >
>>     >
>>     https://mobile.twitter.com/GeoffreyHuntley/status/1609490537484275712
>>     >
>>     > Best,
>>     >
>>     > _______________________________________________
>>     > Starlink mailing list
>>     > Starlink@lists.bufferbloat.net
>>     > https://lists.bufferbloat.net/listinfo/starlink
>>
>>     --
>>     Best regards,
>>     Oleg Kutkov
>>
>>     _______________________________________________
>>     Starlink mailing list
>>     Starlink@lists.bufferbloat.net
>>     https://lists.bufferbloat.net/listinfo/starlink
>>
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink

-- 
Best regards,
Oleg Kutkov

[-- Attachment #2: Type: text/html, Size: 7475 bytes --]

      reply	other threads:[~2023-01-01 17:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-01 11:18 Benjamin Henrion
2023-01-01 11:48 ` Sebastian Moeller
2023-01-01 11:49 ` Oleg Kutkov
2023-01-01 12:01   ` Sebastian Moeller
2023-01-01 14:26     ` Nathan Owens
2023-01-01 16:23   ` Benjamin Henrion
2023-01-01 17:09     ` Mike Puchol
2023-01-01 17:17       ` Oleg Kutkov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4b18869c-1a68-1a16-ec59-59214eef98db@olegkutkov.me \
    --to=contact@olegkutkov.me \
    --cc=starlink@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox