From: Eric <evil.function@proton.me>
To: David Lang <david@lang.hm>
Cc: Oleg Kutkov <contact@olegkutkov.me>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink terminal detector
Date: Mon, 19 Dec 2022 15:54:43 +0000 [thread overview]
Message-ID: <vjsrdncxBpUp8RBqaANwAl12DenIq0bre81Jv9zEr3RJKpFstKpfUAnEpQHyzRlMSsqJkDdzck8W4tkPZ1e9Uc7HEV0W_himsDbK7BICY48=@proton.me> (raw)
In-Reply-To: <ooo0nr36-p502-qpp2-qs6o-p31039r68q7p@ynat.uz>
Get a bunch of US$3 ESP8266 devices, set them up in AP mode with spoofed Starlink MACs and BSSIDs, power them with solar cells + old vape-pen batteries and spread them all over the place. There's nothing like causing the other side to shoot $50k missiles at a $15 decoy.
------- Original Message -------
On Sunday, December 18th, 2022 at 20:49, David Lang via Starlink <starlink@lists.bufferbloat.net> wrote:
> and change the name of the starlink wifi so it doesn't stand out as much.
>
> David Lang
>
> On Mon, 19 Dec 2022, Oleg Kutkov via Starlink wrote:
>
> > From the beginning, the general rule is don't use Starlink WiFi. Or
> > hide the router somewhere to reduce RF emissions.
> >
> > We have developed a set of rules and recommendations about using a PoE
> > injector or bypassing the Starlink router.
> > Unfortunately, a lot of people ignore safety.
> >
> > But there are some countermeasures on the way.
> >
> > On 12/19/22 05:03, Oleg Kutkov via Starlink wrote:
> >
> > > Actually, there is nothing special.
> > >
> > > You can capture WiFi beacons and get a BSSID with a good directional
> > > antenna. 10 - 15 km it's not a problem.
> > >
> > > They are filtering Starlink router BSSID to figure out that somewhere
> > > there is Starlink.
> > > Starlink WiFi router uses Tibro corp. (74:24: prefix).
> > > On 12/19/22 04:41, Dave Taht via Starlink wrote:
> > >
> > > > Starlink detector boasted about... 10km range.
> >
> > https://www.notebookcheck.net/Starlink-terminal-detection-radar-to-enter-testing-in-Ukraine-as-per-Russian-military-blogger.675439.0.html
> >
> > > > I would have figured on starlinks less further front, combined with
> > > > non los radios and ptp wifi being viable. Targeting every wifi
> > > > transmitter is a low percentage play, and adhoc modes for directional
> > > > wifi with synthetic mac's harder to distinguish ...
> > > >
> > > > _______________________________________________
> > > > 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
next prev parent reply other threads:[~2022-12-19 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 2:41 Dave Taht
2022-12-19 3:03 ` Oleg Kutkov
2022-12-19 3:22 ` Oleg Kutkov
2022-12-19 4:49 ` David Lang
2022-12-19 15:54 ` Eric [this message]
2022-12-19 16:07 ` Dave Taht
2022-12-19 23:34 ` Ulrich Speidel
2022-12-20 0:46 ` Oleg Kutkov
2022-12-20 0:50 ` Gary E. Miller
2022-12-19 20:46 ` Hayden Simon
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='vjsrdncxBpUp8RBqaANwAl12DenIq0bre81Jv9zEr3RJKpFstKpfUAnEpQHyzRlMSsqJkDdzck8W4tkPZ1e9Uc7HEV0W_himsDbK7BICY48=@proton.me' \
--to=evil.function@proton.me \
--cc=contact@olegkutkov.me \
--cc=david@lang.hm \
--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