Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Oleg Kutkov <contact@olegkutkov.me>,
	Oleg Kutkov via Starlink <starlink@lists.bufferbloat.net>,
	starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink cheaper in Colombia,cand gps spoofing
Date: Sun, 01 Jan 2023 13:01:38 +0100	[thread overview]
Message-ID: <E7B2691E-AE35-418C-86D5-383EFE21A821@gmx.de> (raw)
In-Reply-To: <7381115c-e248-d885-e4da-c33da77d6fe1@olegkutkov.me>

Hi Oleg,

Tangential question below.

On 1 January 2023 12:49:20 CET, Oleg Kutkov via Starlink <starlink@lists.bufferbloat.net> wrote:
>Hi,
>
>Starlink has a multisystem GNSS receiver with data filtering, so it can't be fooled with the single HackRF (i tested it).
>
>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.

[SM] Do dishies export their high quality time via NTP or PTP to their LANs?

Regards
        Sebastian

>
>
>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
>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

  reply	other threads:[~2023-01-01 12:02 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 [this message]
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

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=E7B2691E-AE35-418C-86D5-383EFE21A821@gmx.de \
    --to=moeller0@gmx.de \
    --cc=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