Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: J Pan <Pan@uvic.ca>
To: Frantisek Borsik <frantisek.borsik@gmail.com>
Cc: starlink@lists.bufferbloat.net
Subject: [Starlink] Re: Starlink and Iran
Date: Fri, 16 Jan 2026 15:06:22 -0800	[thread overview]
Message-ID: <CAHn=e4jqkQ_bvWT0O2iNouu1WyH=+KeDp_LftwwyWF=o_EEQRA@mail.gmail.com> (raw)
In-Reply-To: <CAJUtOOjbA6p3qF3V=Y3vTvf_i8Gj1d0wBaa21-y3w+1Pg_5jWA@mail.gmail.com>

"Amendment to my earlier warning about IR regime scanning for Starlink
WiFi signals:Hiding SSID or using Bypass Mode is a helpful step, but
NOT bulletproof—scanners can still detect the active WiFi radio.The
safest option: TURN OFF WiFi broadcast entirely on the Starlink
router. Use only wired Ethernet connections."? for life-critical
things, better read, think and discuss (3), do and improve (2), and
write (1). why cautious about twitter/x/alike
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan


On Fri, Jan 16, 2026 at 2:52 PM Frantisek Borsik via Starlink
<starlink@lists.bufferbloat.net> wrote:
>
> "We've received some reports indicating that the Iranian regime is using
> handheld/vehicular scanners to detect WiFi signals (especially networks
> with default or strong names) to locate Starlink sources.
>
> Why? Because WiFi is FAR easier to detect than satellite signals.
> Starlink's uplink/downlink is highly directional and hard to pinpoint from
> ground level, but your router's WiFi broadcasts in all directions from your
> home.
>
> If your friends are inside Iran using Starlink: tell them to enable Bypass
> Mode to disable the built-in WiFi, or at minimum hide their SSID and change
> the network name."
>
> https://x.com/NarimanGharib/status/2012177548247969826?s=20
>
> All the best,
>
> Frank
>
> Frantisek (Frank) Borsik
>
>
> *In loving memory of Dave Täht: *1965-2025
>
> https://libreqos.io/2025/04/01/in-loving-memory-of-dave/
>
>
> https://www.linkedin.com/in/frantisekborsik
>
> Signal, Telegram, WhatsApp: +421919416714
>
> iMessage, mobile: +420775230885
>
> Skype: casioa5302ca
>
> frantisek.borsik@gmail.com
>
>
> On Fri, Jan 16, 2026 at 2:29 AM David Lang via Starlink <
> starlink@lists.bufferbloat.net> wrote:
>
> > Ulrich Speidel wrote:
> >
> > > The other issue is orbits: Starlink now occupies an increasing amount of
> > > space real estate in the LEO Goldilocks zone. Go higher and you pay in
> > terms
> > > of latency, and it also becomes harder to direct your beams into small
> > spots
> > > on the ground. Plus you need more transmitter power or antenna gain to
> > get to
> > > the EPFD limit. Go lower and you'll pay in terms of satellite lifetime -
> > not
> > > ideal unless you have rapid launch capability.
> >
> > Starlink recently announce it was lowering the altitude of about half
> > their
> > satellites.
> >
> > David Lang
> > _______________________________________________
> > Starlink mailing list -- starlink@lists.bufferbloat.net
> > To unsubscribe send an email to starlink-leave@lists.bufferbloat.net
> >
> _______________________________________________
> Starlink mailing list -- starlink@lists.bufferbloat.net
> To unsubscribe send an email to starlink-leave@lists.bufferbloat.net

  reply	other threads:[~2026-01-16 23:06 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <176851123059.1249.8585659892308012167@gauss>
2026-01-15 21:49 ` [Starlink] Re: Starlink and Iran Colin_Higbie
2026-01-15 23:15   ` Frantisek Borsik
2026-01-16  0:13   ` Ulrich Speidel
2026-01-16  1:29     ` David Lang
2026-01-16 22:55       ` Frantisek Borsik
2026-01-16 23:06         ` J Pan [this message]
     [not found]     ` <13187.1768590201@obiwan.sandelman.ca>
2026-01-16 23:30       ` Ulrich Speidel
2026-01-17  0:07         ` David Lang
2026-01-17 21:56           ` Ulrich Speidel
2026-01-19 20:39             ` David Lang
2026-01-28  3:09               ` Ulrich Speidel
2026-01-28  3:30                 ` David Lang
2026-01-28  4:02                   ` Mike Puchol
2026-01-28  9:05                     ` Ulrich Speidel
2026-01-28  9:53                       ` David Lang
2026-01-28 20:43                         ` Ulrich Speidel
2026-01-28 20:55                           ` David Lang
2026-01-17 18:32         ` Michael Richardson
2026-01-17 18:38           ` Inemesit Affia
2026-01-17 19:25             ` Michael Richardson
2026-01-17 22:12           ` Ulrich Speidel
     [not found] <176849731431.1249.14387618908540773471@gauss>
2026-01-15 17:42 ` Colin_Higbie
2026-01-15 18:56   ` Jim Forster
2026-01-15 20:15     ` Ulrich Speidel
2026-01-15 20:27   ` Ulrich Speidel
2026-01-15 20:30     ` Hayden Simon
2026-01-15 21:06       ` Ulrich Speidel
2026-01-15 21:09         ` Hayden Simon
2026-01-15 21:20           ` Ulrich Speidel
2026-01-15 21:23             ` Hayden Simon
2026-01-15 14:50 David Fernández
2026-01-15 16:11 ` Oleg Kutkov
2026-01-15 17:13   ` J Pan
  -- strict thread matches above, loose matches on Subject: below --
2026-01-15  9:51 [Starlink] " Ulrich Speidel
2026-01-15 10:06 ` [Starlink] " Inemesit Affia
2026-01-15 10:30   ` Ulrich Speidel
2026-01-15 10:44     ` Inemesit Affia
2026-01-15 11:16       ` Ulrich Speidel
2026-01-15 10:32 ` Inemesit Affia
2026-01-15 10:51   ` Ulrich Speidel
2026-01-15 11:17 ` David Lang
2026-01-15 11:59   ` Sauli Kiviranta
2026-01-15 14:08     ` David Lang
2026-01-15 15:29       ` Sauli Kiviranta
     [not found]   ` <3af2ac06-e098-4c79-869d-9c389959ca07@gmail.com>
     [not found]     ` <q9304244-661o-3qsr-o6rp-9q1nqq09r419@ynat.uz>
     [not found]       ` <4ba64a41-bbbf-4fb5-adb0-c77c15e4ca0f@gmail.com>
2026-01-15 16:20         ` Inemesit Affia
2026-01-15 20:12   ` Ulrich Speidel
2026-01-15 17:10 ` J Pan
2026-01-15 20:07   ` Ulrich Speidel
2026-01-15 21:47     ` Oleg Kutkov
2026-01-16  4:18       ` Ulrich Speidel
2026-01-16  8:12         ` Frantisek Borsik
2026-01-16  8:24           ` Inemesit Affia

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='CAHn=e4jqkQ_bvWT0O2iNouu1WyH=+KeDp_LftwwyWF=o_EEQRA@mail.gmail.com' \
    --to=pan@uvic.ca \
    --cc=frantisek.borsik@gmail.com \
    --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