From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 04A5C3CB37 for ; Fri, 10 Nov 2023 11:09:15 -0500 (EST) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 3AAG9Cp2042665; Fri, 10 Nov 2023 17:09:12 +0100 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A778C204B4F; Fri, 10 Nov 2023 17:09:12 +0100 (CET) Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 9ADA7204ABF; Fri, 10 Nov 2023 17:09:12 +0100 (CET) Received: from [10.8.32.70] (is156570.intra.cea.fr [10.8.32.70]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 3AAG9CtU026988; Fri, 10 Nov 2023 17:09:12 +0100 Message-ID: <5df2b2b9-fc8a-4147-8a53-5b7baf268339@gmail.com> Date: Fri, 10 Nov 2023 17:09:12 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: fr To: David Lang Cc: starlink@lists.bufferbloat.net References: <13641F2C-B933-49AF-8289-7B8917667AAE@pch.net> <86062ps2-on4p-s855-6ss9-pr475q32q752@ynat.uz> From: Alexandre Petrescu In-Reply-To: <86062ps2-on4p-s855-6ss9-pr475q32q752@ynat.uz> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-CEA-Virus: SOPHOS_SAVI_ERROR_OLD_VIRUS_DATA Subject: Re: [Starlink] [NNagain] one dish per household is silly. 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: Fri, 10 Nov 2023 16:09:16 -0000 Le 10/11/2023 à 14:44, David Lang a écrit : > On Fri, 10 Nov 2023, Alexandre Petrescu via Starlink wrote: > >>> There is no prohibition against sharing. The closest that >>> document comes to it is: "The Standard Service Plan is designed >>> for personal, family, or household use." >> >> And, the specs of Starlink WiFi Router say "Mesh - Compatible with >> up to 3 Starlink Mesh nodes". Why 3 and not 4, one might wonder. >> >> Yet there are additional technical reasons as to why extending the >> WiFi to others is inconvenient. For both IPv4 and IPv6 the other >> users would be situated behind NATs, multiple levels of them. It >> would break certain apps. > > given how many users live behing multiple layers of NAT now, I think > there are fewer apps that would break than you think (and in terms > of overall traffic, it's a very small percentage) > > I'm not a fan of wifi mesh, it can work in some conditions, but it > breaks down quickly under load (aittime utilization, be it number of > nodes, number of users, area covered, or bandwidth used). But > setting up a structured distribution to a number of APs can scale > well (I run the wireless network at the Scale conference and use > simple APs (most over a decade old now) running openWRT to support >> 3500 geeks over a 100,000 sq ft facility) > >> This kind of WiFi sharing was tried and with some degree of success >> to ground multi-ISP settings. My home ISP WiFi allows other users >> having same ISP at their home. Some agreements exist between some >> ISPs to expand that domain of allowance. > > that's still a guest mode on a bunch of separate uplink networks, not > the same as sharing one uplink network with a wide group of people. > >> Here we talk about only one ISP. Starlink might want, as a first >> step, to allow other users that have Starlink at their home. When >> more space ISPs like this will appear, maybe some agreements might >> happen. > > I'm not understanding what you think Starlink is prohibiting here. Original poster (Dave, not me) provided this text: "There is no prohibition against sharing. The closest that document comes to it is: "The Standard Service Plan is designed for personal, family, or household use."" If that text is true, I tend to agree with the interpretation that that text prohibits sharing the wifi. It says 'personal, family, household'. That certainly means to be: not my visitors, not my neighbors. In the past it was the case like that with non-space home ISPs. There were requests to modify that, business to open. The response was the appearance of business that shared the wifi (independent wifi sharing boxes, free for end users), independent of the ISPs. It led into the development of the concept of sharing WiFi among users of same ISP, and agreements between ISPs. The same could happen now with Starlink. However, and I will post separately, there are so many unknowns and so much noise about Starlink in general, changing all the time, that it is hard to make a definitive oppinion. Basically one does not know what is real until one tries it, and I have not tried it (I am not a starlink user but considering it). Alex > > each dish in an area imposes noticable overhead, beyond simply the > bandwidth the user consumes, so it's better for the starlink system > to have fewer dishes that distribute to the same number of users, > with the same usage patterns. > >>> resale is prohibited. > > resale is prohibited, but cost sharing is not, and I don't even think > that resale of the service to the community would be prohibited, just > resale of the equipment, or setting yourself up as a distributer of > starlink service and equipment. > > David Lang