From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mail.toke.dk; spf=pass smtp.mailfrom=lang.hm; dkim=fail; arc=none (Message is not ARC signed); dmarc=none Received: from mail.lang.hm (wsip-70-167-213-146.ph.ph.cox.net [70.167.213.146]) by mail.toke.dk (Postfix) with ESMTPS id E0AAEE2012A for ; Mon, 16 Mar 2026 19:11:16 +0100 (CET) Received: from [10.2.2.53] (unknown [10.2.2.53]) by mail.lang.hm (Postfix) with ESMTP id 0E82821E6BE; Mon, 16 Mar 2026 11:11:14 -0700 (PDT) Date: Mon, 16 Mar 2026 11:11:08 -0700 (MST) From: David Lang To: Inemesit Affia cc: Dave Taht via Starlink In-Reply-To: <64f61ff1-11c2-454c-a5e2-2caaf4b78601@gmail.com> Message-ID: <214q1oq0-02pp-04r9-o695-o496s120315n@ynat.uz> References: <64f61ff1-11c2-454c-a5e2-2caaf4b78601@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Message-ID-Hash: 3U5ON5VKJ4SQGKZNW2FBSEQJ7IP4Q5XB X-Message-ID-Hash: 3U5ON5VKJ4SQGKZNW2FBSEQJ7IP4Q5XB X-MailFrom: david@lang.hm X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list Subject: [Starlink] Re: Starlink and user identification especially wrt the Islamic Republic of Iran List-Id: "Starlink has bufferbloat. Bad." Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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 > Reply-To: Inemesit Affia > To: Dave Taht via Starlink > 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 : > >> 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 >