From: Inemesit Affia <inemesitaffia@gmail.com>
To: David Lang <david@lang.hm>
Cc: Ulrich Speidel <u.speidel@auckland.ac.nz>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: Starlink and Iran
Date: Thu, 15 Jan 2026 17:20:49 +0100 [thread overview]
Message-ID: <bd2894f9-8bd3-4363-9436-3918f9ae2571@gmail.com> (raw)
In-Reply-To: <4ba64a41-bbbf-4fb5-adb0-c77c15e4ca0f@gmail.com>
Sorry I've messed up the flow in my client
Jan 15, 2026 5:18:16 PM Inemesit Affia <inemesitaffia@gmail.com>:
> Jan 15, 2026 3:06:39 PM David Lang <david@lang.hm>:
>
>> Inemesit Affia wrote:
>>
>>> Jan 15, 2026 12:17:46 PM David Lang via Starlink <starlink@lists.bufferbloat.net>:
>>>
>>>> Authorized or not, starlink service has been turned on in Iran, I would assume that D2C is enabled as well.
>>>
>>> If it was enabled these people asking for it aren't in the group.
>>
>> It's been publicly reported that Starlink is active.
>
> I'm talking about direct to cell. That's what the letter is about. Starlink broadband has been available in Iran since at least Q4 2022.
>
>
>>
>>>> Jamming the D2C signal is far easier than jamming the dishys, all you need is to have the towers running with a stronger signal. (the phones will connect to the tower with the strongest signal). It's also easier to jam the D2C satellites (wider beamwidth and fewer that need to be jammed)
>>>
>>> True. Hopefully there are free bands somewhere.
>>
>> D2C only operates on a single band.
>
> I don't believe this is true
>
> PCS G Block LTE band 25(1910-1915 MHz & 1990-1995 MHz) is T-Mobile's implementation
>
> VMO2 1710-1716 UL /MSS 2170-2200 DL (Band 66)
>
> Softbank 1975-1980 UL / MSS 2170-2200 DL (Band 65)
>
> DoCoMo 1940-1945 UL / MSS 2170-2200 DL (Band 65)
>
> KDDI 1920-1925 UL / MSS 2170-2200 DL (Band 65)
>
> The tech is capable of 1.6 GHz to at least 2.2 GHz from examples given here. That spans multiple LTE bands. I don't know what else it's capable of. If service is switched off or there are unallocated bands, then there's hope for urban use.
>
>>
>>
>>>> I don't think they would need to get new sims, esims, etc in place, they just need to instruct the satellites to accept any sim rather than only authorized sims.
>>>
>>> I just don't think this will work. Authorization free 4G.
>>
>> Why not? just hard code success for the authorization step.
>
> From what I retained from seminars around the introduction of 4G, the SIM authenticates the network and the network authenticates the Sim using a key stored in the SIM's HSM.
>
> 911/112 of course excepted
>
>>
>>
>>
>>>> In terms of tracking/jamming the dishys normal signal, I think it would be easier to track/jam their wifi signal, those default to SSID STARLINK and will be in a known MAC range. disabling wifi and only working with a wired connection is going to be much safer (admittedly, less convienient, but when they are threatening to kill you if you use a dishy, you should batch upload via a wired connection, not try to livestream the protests, at least, not unless you are truely mobile)
>>>
>>> I've suggested not using the Wi-Fi router at all. Any phone scanner would probably tell you it's a starlink. SpaceX should change the BSSID's too
>>
>> The SSID can be set by the user, the MAC address is hard-coded
>>
>> David Lang
>
>>
> MAC's can be changed in software. I've done it on Windows XP and 7 ages ago with smac. I'm sure it's doable on Linux. I remember doing similar with HOSTAPD.
>
> Remember how devices rotate MAC addresses for privacy? That requires a method for changing them. It's not like the ROM is overwritten. Once the device is reset, it will go back to default.
>
>
>>
next prev parent reply other threads:[~2026-01-15 16:20 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 9:51 [Starlink] Starlink and Iran 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2026-01-15 14:50 David Fernández
2026-01-15 16:11 ` Oleg Kutkov
2026-01-15 17:13 ` J Pan
[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
[not found] <176851123059.1249.8585659892308012167@gauss>
2026-01-15 21:49 ` 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
[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
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=bd2894f9-8bd3-4363-9436-3918f9ae2571@gmail.com \
--to=inemesitaffia@gmail.com \
--cc=david@lang.hm \
--cc=starlink@lists.bufferbloat.net \
--cc=u.speidel@auckland.ac.nz \
/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