From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cpanel9.c.fozzy.com (cpanel9.c.fozzy.com [206.54.190.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 695703B2A4 for ; Sun, 18 Dec 2022 22:22:32 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=olegkutkov.me; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:From:References:To:Subject:MIME-Version:Date:Message-ID:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=R82DyHkXFsdXLn0Wxtw6QWdhvqP6sG3nsRssvnj80No=; b=sFTbsM2FJe6Ja7K4Lb5Bm2kDlZ /zCwm4RMOAHwz+1Le8XdXmg4F0gbONNcgavgi1kfnBePko0g6Otn7pY9VpsXhXfnHBwQ4vOnGfCph +gtblfa/kE0rlhAZLZmDnnovzUsgpJajCx+72eK+GEOaecltQiwe05ocPFIl1C0MmjCOTysd9mXIb /Mup3RvMhrT0QMjMP1Vd9x/7sEIsbKWvDNRD+BZPW/qrSn+li7MbCyTWW++p26LgejPGJ3FFkZhCF mDyz8ookrn/8SW0/YYXOX490bWjBPuTdT3V1KewQEUgiiePjnnPqliKxhr4BTh2Nh0MJe5vZzd8YH RlpUyjjA==; Received: from 178-133-56-43.mobile.vf-ua.net ([178.133.56.43]:42541 helo=[172.20.10.2]) by cpanel9.c.fozzy.com with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.95) (envelope-from ) id 1p76jV-001mHs-JY for starlink@lists.bufferbloat.net; Mon, 19 Dec 2022 03:22:31 +0000 Message-ID: <41798860-aac5-7f36-3def-76c3400182a2@olegkutkov.me> Date: Mon, 19 Dec 2022 05:22:28 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Content-Language: en-US To: starlink@lists.bufferbloat.net References: From: Oleg Kutkov In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cpanel9.c.fozzy.com X-AntiAbuse: Original Domain - lists.bufferbloat.net X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - olegkutkov.me X-Get-Message-Sender-Via: cpanel9.c.fozzy.com: authenticated_id: contact@olegkutkov.me X-Authenticated-Sender: cpanel9.c.fozzy.com: contact@olegkutkov.me X-Source: X-Source-Args: X-Source-Dir: X-From-Rewrite: unmodified, already matched Subject: Re: [Starlink] Starlink terminal detector X-BeenThere: starlink@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Starlink has bufferbloat. Bad." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2022 03:22:32 -0000 From the beginning, the general rule is don't use Starlink WiFi. Or hide the router somewhere to reduce RF emissions. We have developed a set of rules and recommendations about using a PoE injector or bypassing the Starlink router. Unfortunately, a lot of people ignore safety. But there are some countermeasures on the way. On 12/19/22 05:03, Oleg Kutkov via Starlink wrote: > 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