Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
* [Starlink] Starlink and user identification especially wrt the Islamic Republic of Iran
@ 2026-03-16 15:18 Inemesit Affia
  2026-03-16 15:25 ` [Starlink] " Inemesit Affia
  0 siblings, 1 reply; 4+ messages in thread
From: Inemesit Affia @ 2026-03-16 15:18 UTC (permalink / raw)
  To: Dave Taht via Starlink

I've dropped some comments in the past on other fora but not here.

There's a recent issue with user outages in Iran caused by an update. There are individuals with multiple terminals where one is down and the other up.

Users should avoid using devices with local apps installed. Avoid Chinese devices if possible (both are telemetry issues)

Starlink has RF and heat issues that make it easily identified with the right equipment so you need to hide the device and avoid WiFi transmission (where possible).

A piece of plain cloth is enough to hide the heat signature in most cases, especially during the day. But what I've been hearing is Wi-Fi scanners being deployed. Unfortunately Starlink ships not only with a default Starlink name, but like every other WiFi device, identifies it's manufacturer in its transmission which you don't need more than a phone to find.

Fortunately that's fixable for the less tech savvy users. If the device identifies it's cell as being in Iran, change the mac one to one mimicking the device of the user or AP's more common in the area. And allow users to limit it's power like I can do on my cheap D-link

I'm hopeful for those in the area and I'm glad about the recent shutdown of Russian users in Ukraine.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Starlink] Re: Starlink and user identification especially wrt the Islamic Republic of Iran
  2026-03-16 15:18 [Starlink] Starlink and user identification especially wrt the Islamic Republic of Iran Inemesit Affia
@ 2026-03-16 15:25 ` Inemesit Affia
  2026-03-16 18:11   ` David Lang
  0 siblings, 1 reply; 4+ messages in thread
From: Inemesit Affia @ 2026-03-16 15:25 UTC (permalink / raw)
  To: Dave Taht via Starlink

By fixable, I mean fixable by SpaceX, not the end user. I realize not everyone has the extra equipment i do. So going straight to "use third party routers" is a non

Mar 16, 2026 4:18:57 PM Inemesit Affia <inemesitaffia@gmail.com>:

> I've dropped some comments in the past on other fora but not here.
> 
> There's a recent issue with user outages in Iran caused by an update. There are individuals with multiple terminals where one is down and the other up.
> 
> Users should avoid using devices with local apps installed. Avoid Chinese devices if possible (both are telemetry issues)
> 
> Starlink has RF and heat issues that make it easily identified with the right equipment so you need to hide the device and avoid WiFi transmission (where possible).
> 
> A piece of plain cloth is enough to hide the heat signature in most cases, especially during the day. But what I've been hearing is Wi-Fi scanners being deployed. Unfortunately Starlink ships not only with a default Starlink name, but like every other WiFi device, identifies it's manufacturer in its transmission which you don't need more than a phone to find.
> 
> Fortunately that's fixable for the less tech savvy users. If the device identifies it's cell as being in Iran, change the mac one to one mimicking the device of the user or AP's more common in the area. And allow users to limit it's power like I can do on my cheap D-link
> 
> I'm hopeful for those in the area and I'm glad about the recent shutdown of Russian users in Ukraine.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Starlink] Re: Starlink and user identification especially wrt the Islamic Republic of Iran
  2026-03-16 15:25 ` [Starlink] " Inemesit Affia
@ 2026-03-16 18:11   ` David Lang
  2026-03-16 18:17     ` David Lang
  0 siblings, 1 reply; 4+ messages in thread
From: David Lang @ 2026-03-16 18:11 UTC (permalink / raw)
  To: Inemesit Affia; +Cc: Dave Taht via Starlink

Starlink, like every other wifi manufacturer is allocated specific addresses to 
avoid collisions in the addresses in use. Any new addresses they get allocated 
will be well known very quickly. What is it you suggest that they do?

but as a matter of common sense, if you are hiding something from your 
government, hard-wire where possible, don't use wifi at all.

David Lang


On Mon, 16 Mar 2026, Inemesit Affia via Starlink wrote:

> Date: Mon, 16 Mar 2026 16:25:21 +0100
> From: Inemesit Affia via Starlink <starlink@lists.bufferbloat.net>
> Reply-To: Inemesit Affia <inemesitaffia@gmail.com>
> To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
> Subject: [Starlink] Re: Starlink and user identification especially wrt the
>     Islamic Republic of Iran
> 
> By fixable, I mean fixable by SpaceX, not the end user. I realize not everyone has the extra equipment i do. So going straight to "use third party routers" is a non
>
> Mar 16, 2026 4:18:57 PM Inemesit Affia <inemesitaffia@gmail.com>:
>
>> I've dropped some comments in the past on other fora but not here.
>>
>> There's a recent issue with user outages in Iran caused by an update. There are individuals with multiple terminals where one is down and the other up.
>>
>> Users should avoid using devices with local apps installed. Avoid Chinese devices if possible (both are telemetry issues)
>>
>> Starlink has RF and heat issues that make it easily identified with the right equipment so you need to hide the device and avoid WiFi transmission (where possible).
>>
>> A piece of plain cloth is enough to hide the heat signature in most cases, especially during the day. But what I've been hearing is Wi-Fi scanners being deployed. Unfortunately Starlink ships not only with a default Starlink name, but like every other WiFi device, identifies it's manufacturer in its transmission which you don't need more than a phone to find.
>>
>> Fortunately that's fixable for the less tech savvy users. If the device identifies it's cell as being in Iran, change the mac one to one mimicking the device of the user or AP's more common in the area. And allow users to limit it's power like I can do on my cheap D-link
>>
>> I'm hopeful for those in the area and I'm glad about the recent shutdown of Russian users in Ukraine.
> _______________________________________________
> Starlink mailing list -- starlink@lists.bufferbloat.net
> To unsubscribe send an email to starlink-leave@lists.bufferbloat.net
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Starlink] Re: Starlink and user identification especially wrt the Islamic Republic of Iran
  2026-03-16 18:11   ` David Lang
@ 2026-03-16 18:17     ` David Lang
  0 siblings, 0 replies; 4+ messages in thread
From: David Lang @ 2026-03-16 18:17 UTC (permalink / raw)
  To: David Lang; +Cc: Inemesit Affia, Dave Taht via Starlink

by the way, there was a more in-depth discussion on the issues a couple months 
ago when the protests started there.

David Lang

On Mon, 16 Mar 2026, David Lang via Starlink wrote:

> Date: Mon, 16 Mar 2026 11:11:08 -0700 (MST)
> From: David Lang via Starlink <starlink@lists.bufferbloat.net>
> Reply-To: David Lang <david@lang.hm>
> To: Inemesit Affia <inemesitaffia@gmail.com>
> Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
> Subject: [Starlink] Re: Starlink and user identification especially wrt the
>     Islamic Republic of Iran
> 
> Starlink, like every other wifi manufacturer is allocated specific addresses 
> to avoid collisions in the addresses in use. Any new addresses they get 
> allocated will be well known very quickly. What is it you suggest that they 
> do?
>
> but as a matter of common sense, if you are hiding something from your 
> government, hard-wire where possible, don't use wifi at all.
>
> David Lang
>
>
> On Mon, 16 Mar 2026, Inemesit Affia via Starlink wrote:
>
>> Date: Mon, 16 Mar 2026 16:25:21 +0100
>> From: Inemesit Affia via Starlink <starlink@lists.bufferbloat.net>
>> Reply-To: Inemesit Affia <inemesitaffia@gmail.com>
>> To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
>> Subject: [Starlink] Re: Starlink and user identification especially wrt the
>>     Islamic Republic of Iran
>> 
>> By fixable, I mean fixable by SpaceX, not the end user. I realize not 
>> everyone has the extra equipment i do. So going straight to "use third 
>> party routers" is a non
>> 
>> Mar 16, 2026 4:18:57 PM Inemesit Affia <inemesitaffia@gmail.com>:
>> 
>>> I've dropped some comments in the past on other fora but not here.
>>> 
>>> There's a recent issue with user outages in Iran caused by an update. 
>>> There are individuals with multiple terminals where one is down and the 
>>> other up.
>>> 
>>> Users should avoid using devices with local apps installed. Avoid Chinese 
>>> devices if possible (both are telemetry issues)
>>> 
>>> Starlink has RF and heat issues that make it easily identified with the 
>>> right equipment so you need to hide the device and avoid WiFi transmission 
>>> (where possible).
>>> 
>>> A piece of plain cloth is enough to hide the heat signature in most cases, 
>>> especially during the day. But what I've been hearing is Wi-Fi scanners 
>>> being deployed. Unfortunately Starlink ships not only with a default 
>>> Starlink name, but like every other WiFi device, identifies it's 
>>> manufacturer in its transmission which you don't need more than a phone to 
>>> find.
>>> 
>>> Fortunately that's fixable for the less tech savvy users. If the device 
>>> identifies it's cell as being in Iran, change the mac one to one mimicking 
>>> the device of the user or AP's more common in the area. And allow users to 
>>> limit it's power like I can do on my cheap D-link
>>> 
>>> I'm hopeful for those in the area and I'm glad about the recent shutdown 
>>> of Russian users in Ukraine.
>> _______________________________________________
>> 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
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2026-03-16 18:17 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-03-16 15:18 [Starlink] Starlink and user identification especially wrt the Islamic Republic of Iran Inemesit Affia
2026-03-16 15:25 ` [Starlink] " Inemesit Affia
2026-03-16 18:11   ` David Lang
2026-03-16 18:17     ` David Lang

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox