From: Oleg Kutkov <contact@olegkutkov.me>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink terminal detector
Date: Mon, 19 Dec 2022 05:03:26 +0200 [thread overview]
Message-ID: <d38a5288-bdba-4338-ff86-04655e18ec32@olegkutkov.me> (raw)
In-Reply-To: <CAA93jw7N5KmxPoUTAQ7N4kVMHgNX16LF5e+kZzL1r6nS4_MpKg@mail.gmail.com>
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
--
Best regards,
Oleg Kutkov
next prev parent reply other threads:[~2022-12-19 3:03 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 [this message]
2022-12-19 3:22 ` Oleg Kutkov
2022-12-19 4:49 ` David Lang
2022-12-19 15:54 ` Eric
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=d38a5288-bdba-4338-ff86-04655e18ec32@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