From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.lang.hm (unknown [66.167.227.145]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id A23EC3B2A4 for ; Mon, 14 Feb 2022 15:29:09 -0500 (EST) Received: from dlang-mobile (unknown [10.2.2.69]) by mail.lang.hm (Postfix) with ESMTP id 9CD5D121AF9; Mon, 14 Feb 2022 12:29:08 -0800 (PST) Date: Mon, 14 Feb 2022 12:29:08 -0800 (PST) From: David Lang To: Jonathan Bennett cc: starlink@lists.bufferbloat.net, Dave Taht In-Reply-To: Message-ID: <1p492142-q944-r494-6s6r-p6q37s57qnq4@ynat.uz> References: MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII Subject: Re: [Starlink] Starlink Roaming 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, 14 Feb 2022 20:29:09 -0000 I asked starlink about temp service away from my registered location, they said I have two options 1. formally change the service location (if approved, guaranteed to work, but you aren't guaranteed to be able to change the service location back) 2. best effort, set it up and try it. Service may perfect, or may be worse (all the way to non-existant) depending on how many other dishes are in use in the area. I've done some limited testing with my dish within about 15 miles of my registered location (in both cases with less than optimal sky views) and it's worked without a hitch. I plan to do a test further away this weekend (but in a less populated area, so I have high hopes) David Lang On Mon, 14 Feb 2022, Jonathan Bennett wrote: > It appears that there is now a system in place for Starlink to re-connect > even if you are outside your official service cell. For those of us who > want to use Starlink on vacations or other trips, this is quite the > development. > > --Jonathan Bennett >