From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 4EAEA3CB37 for ; Thu, 22 Feb 2024 07:18:52 -0500 (EST) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 41MCIoaT029069 for ; Thu, 22 Feb 2024 13:18:50 +0100 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C8F942038C5 for ; Thu, 22 Feb 2024 13:18:50 +0100 (CET) Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id C0BE72038BE for ; Thu, 22 Feb 2024 13:18:50 +0100 (CET) Received: from [10.8.32.70] (is156570.intra.cea.fr [10.8.32.70]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 41MCIowZ025651 for ; Thu, 22 Feb 2024 13:18:50 +0100 Message-ID: Date: Thu, 22 Feb 2024 13:18:50 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: fr To: starlink@lists.bufferbloat.net References: <10cabe9d-0c0f-4adc-baf7-0ba487867352@olegkutkov.me> <7849c840-fe56-4867-91bd-613c3d2b5f42@gmail.com> <4e7a1b3a-db75-4558-a5aa-42638ffa6962@auckland.ac.nz> From: Alexandre Petrescu In-Reply-To: <4e7a1b3a-db75-4558-a5aa-42638ffa6962@auckland.ac.nz> 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] First tests of the Starlink REV4 (aka gen3) 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: Thu, 22 Feb 2024 12:18:52 -0000 Le 25/01/2024 à 02:54, Ulrich Speidel via Starlink a écrit : > On 25/01/2024 1:37 am, Alexandre Petrescu via Starlink wrote: >> Thanks for the tests! >> >> The dl/ul speeds 300/15 mbit/s are impressive. > > "Speeds" (observed data rates) in terms of Starlink hardware are > actually fairly meaningless as they depend on: > > * Satellite(s) involved in the data transfer over the duration of the > measurement(s). > * Load on those satellites, which depends on the number of other > current users whose traffic goes via those birds, and what these > users are up to. Note this changes between handovers. > * RTT to other end of transfer path. > * Packet loss (including beyond Starlink's network) > > Unless a Dishy is able to handle communication via multiple satellites > in parallel, I would expect the rates to be the same more or less > regardless of model used. In fact, I would expect a Dishy model that is > able to align itself to do marginally better over time. > >> >> At video pointer 5:53 the reported Ping ?/dl/ul 88/204/121 ms and Jitter >> 9.2 ms seem interesting. >> >>     ==> I am not sure which of the two (ping or jitter) you name >> 'latency'? > All of them I guess. >> >>     ==> I am not sure why the dl (download) ping ms is higher than the ul. > Because that is where you have the longer queues. >> >>     ==> I don't know what is the first ('?') parameter reported as 88ms >> for Ping? > > I presume unloaded ping RTT. The second is ping RTT during the download > test (with inbound queues loaded), the last is ping RTT during the > upload test (with outbound queues loaded). > > I'd also note here that these are values obtained from Kyiv, which isn't > a Starlink environment that is easy to assess. For one, we don't know > whether there are Starlink gateways in Ukraine, or if there are, where > they'd be. One could find 'Kyiv' in the list shown by https://geoip.starlinkisp.net/feed.csv (not sure whether that is a teleport or a point of presence without satcom access). Alex We don't know where else there may be gateways - not > every jurisdiction publishes this - or whether Starlink may even be > operating opportunistic fair weather optical gateways which they don't > have to disclose to anyone. Plus we don't know what may be carted into > the area or away from it via laser links to gateways much further away. > >> >> I wonder whether the DHCPv6-PD is still supported by REV4 and whether >> the allocated prefix is still a non-/64 (i.e. a /56 delivered by >> DHCPv6-PD reported earlier on this email list by Steven on Dec. 12, 2023)? >> >> Alex >> >> Le 23/01/2024 à 10:07, Oleg Kutkov via Starlink a écrit : >> > I conducted the initial comparative tests of the new terminal in >> > Ukraine. I guess it's not a really "legal" because the new terminal is >> > not certified and not selling outside the US for the moment. But who >> > cares. >> > >> > Here's a video: https://youtu.be/hWPMpJrjd1g >> >> > >> > I will try to do more technical tests next week. There will be a new >> > video. >> > >> _______________________________________________ >> Starlink mailing list >> Starlink@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/starlink >> > > -- > **************************************************************** > Dr. Ulrich Speidel > > School of Computer Science > > Room 303S.594 (City Campus) > > The University of Auckland > u.speidel@auckland.ac.nz > http://www.cs.auckland.ac.nz/~ulrich/ > **************************************************************** > > > > > _______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/starlink