From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <david@lang.hm>
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 F0C663B29D
 for <starlink@lists.bufferbloat.net>; Thu, 11 May 2023 19:47:43 -0400 (EDT)
Received: from dlang-mobile (unknown [10.2.2.69])
 by mail.lang.hm (Postfix) with ESMTP id AB14E18DC05;
 Thu, 11 May 2023 16:47:42 -0700 (PDT)
Date: Thu, 11 May 2023 16:47:42 -0700 (PDT)
From: David Lang <david@lang.hm>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
cc: starlink@lists.bufferbloat.net
In-Reply-To: <3a526869-c718-6e25-e84b-e973427acdbc@auckland.ac.nz>
Message-ID: <8p6ooqq3-5rnp-3p70-7oq2-2090p20porpo@ynat.uz>
References: <CAPcR1WqL++WbAqee36+8j1GAV+MiJRpk=z9Z7Gc6+2RxTieACQ@mail.gmail.com>
 <3a526869-c718-6e25-e84b-e973427acdbc@auckland.ac.nz>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Subject: Re: [Starlink] Quick questions about Starlink user terminal
X-BeenThere: starlink@lists.bufferbloat.net
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Starlink has bufferbloat. Bad." <starlink.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/starlink>,
 <mailto:starlink-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/starlink>
List-Post: <mailto:starlink@lists.bufferbloat.net>
List-Help: <mailto:starlink-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/starlink>,
 <mailto:starlink-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Thu, 11 May 2023 23:47:44 -0000

On Fri, 12 May 2023, Ulrich Speidel via Starlink wrote:

> On 12/05/2023 9:48 am, Sirapop Theeranantachai via Starlink wrote:
>> Hi, I'm currently working on packet simulation analysis over large LEO 
>> constellations such as Starlink, and I do have a few questions on the 
>> Starlink commodity terminals and ISL.
>>
>> 1) Is the commodity hardware capable of forming multiple GSL channels 
>> to multiple satellites? If it's not possible, is it possible that the 
>> hardware allows multiple downlink but only one uplink?

> Based on our observations, no to both questions - one sat at a time. 
> We've noticed that power use goes up with observed downlink rate, 
> though. Mike Puchol might be able to comment a bit more here as he's 
> tried to get between Dishy and the birds.

We don't know if this is a hardware limitation or a software limitation, what we 
can observe is that currently it doesn't appear to do multiple connections.

David Lang