From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bosmailout06.eigbox.net (bosmailout06.eigbox.net [66.96.186.6]) (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 E9E1E3B29E for ; Mon, 21 Feb 2022 15:31:44 -0500 (EST) Received: from bosmailscan08.eigbox.net ([10.20.15.8]) by bosmailout06.eigbox.net with esmtp (Exim) id 1nMFLU-0001hU-Ba for starlink@lists.bufferbloat.net; Mon, 21 Feb 2022 15:31:44 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alum.mit.edu; s=dkim; h=Sender:Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From: Reply-To: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=LHsq6nTk4dw7UhHyIzZtS5w1o3iDjxMS9BsHPBfYn+g=; b=UpDJ+ZAnMLlPLPM4wgn3YHyn9+ /+N6+UAK7L93eTcyrpTz+Coor5+CgDKMgNoMpMdew9NSXaJbC6PXyxMMb++H+eoVPRFX+1MWSgj+h lSeD6lYeMe/ezSCjisijP9KbJpgoc4vG1LAw9qGHkldOPYmJLdvyBvXeIGuI4yBzcNj+gQeMAwag8 QafXHfnLgxYu4Kvcbr0luSHK+dvRD/xe+Du/4ey3OgvClpIhFFnUsM9vK61TS7dWuJKWGQUUwLJ37 9MmZ6zqIvNulTc2xmjbAF6qacKX8jmOg4FBeLQGTMZuLiH9/DGIaps5tFjDB1ddILUCfeWbMlK+iz VUscDuCA==; Received: from [10.115.3.33] (helo=bosimpout13) by bosmailscan08.eigbox.net with esmtp (Exim) id 1nMFLT-0008VP-P5 for starlink@lists.bufferbloat.net; Mon, 21 Feb 2022 15:31:43 -0500 Received: from bosauthsmtp16.yourhostingaccount.com ([10.20.18.16]) by bosimpout13 with id xwXg2600C0LoEWa01wXjSx; Mon, 21 Feb 2022 15:31:43 -0500 X-Authority-Analysis: v=2.3 cv=RNUo47q+ c=1 sm=1 tr=0 a=2OW49aEHms2tn/AeNJ+rfA==:117 a=nIEF4cAZMyOU5h9mcfI6lg==:17 a=kj9zAlcOel0A:10 a=oGFeUVbbRNcA:10 a=6ulraYUaiNAA:10 a=kurRqvosAAAA:8 a=9wEFEmgGAAAA:8 a=uherdBYGAAAA:8 a=7Lyishs_syT3JmI33iYA:9 a=CjuIK1q_8ugA:10 a=kbxRQ_lfPIoQnHsAj2-A:22 a=URuH0njPyasT08JpGQTJ:22 a=Ef4yma5cpRUEJWN9UqBm:22 Received: from c-67-180-86-211.hsd1.ca.comcast.net ([67.180.86.211]:62110 helo=SRA6) by bosauthsmtp16.eigbox.net with esmtpa (Exim) id 1nMFLQ-0004Xn-1A; Mon, 21 Feb 2022 15:31:40 -0500 Reply-To: From: "Dick Roy" To: "'David Lang'" , "'Larry Press'" Cc: References: <1p492142-q944-r494-6s6r-p6q37s57qnq4@ynat.uz> In-Reply-To: Date: Mon, 21 Feb 2022 12:31:35 -0800 Organization: SRA Message-ID: <1F1EB112F8CB446FAB4BF308A76955FA@SRA6> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Adgm9M9YP9HY5Zp3TJG6nZ5EPiXv4wAbGrXQ X-MimeOLE: Produced By Microsoft MimeOLE X-EN-UserInfo: f809475445fb8041985048e338e1a001:931c98230c6409dcc37fa7e93b490c27 X-EN-AuthUser: dickroy@intellicommunications.com Sender: "Dick Roy" X-EN-OrigIP: 67.180.86.211 X-EN-OrigHost: c-67-180-86-211.hsd1.ca.comcast.net 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, 21 Feb 2022 20:31:45 -0000 What does your contract say about the "where" you can expect service from your dishy? I suspect the system is capable of tracking all users at all times they're in coverage which is how they could/would enforce a contractual limitation/constraint. RR -----Original Message----- From: Starlink [mailto:starlink-bounces@lists.bufferbloat.net] On Behalf Of David Lang Sent: Sunday, February 20, 2022 11:30 PM To: Larry Press Cc: starlink@lists.bufferbloat.net Subject: Re: [Starlink] Starlink Roaming tonight I took it to a friends house about 25 miles away and within a couple min it gave me an error message saying that I wasn't at my assigned location. David Lang On Mon, 21 Feb 2022, Larry Press wrote: > Date: Mon, 21 Feb 2022 07:22:44 +0000 > From: Larry Press > To: David Lang , > Jonathan Bennett > Cc: "starlink@lists.bufferbloat.net" > Subject: Re: [Starlink] Starlink Roaming > > David brought his dish to my location -- about fifty miles from his service loacation and in a different cell and it could not connect. We had a clear view of the entire sky. He speculated that that was because it was registered to use a specific ground station that was out of range at my place. Does that seem reasonable? > > Larry Press > ________________________________ > From: Starlink on behalf of David Lang > Sent: Monday, February 14, 2022 12:29 PM > To: Jonathan Bennett > Cc: starlink@lists.bufferbloat.net > Subject: Re: [Starlink] Starlink Roaming > > 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 >> > _______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/starlink_ _;!!P7nkOOY!txPxU76SxJ4JvYe2kDjl5OcuAgSIb7mkHWuCMgt3eSH3Tec--6vePH_RCs0NVt6n 2TE6_9HsG20fOA$ > _______________________________________________ Starlink mailing list Starlink@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/starlink