From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi1-x232.google.com (mail-oi1-x232.google.com [IPv6:2607:f8b0:4864:20::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 7B0E93CB37 for ; Mon, 27 Mar 2023 06:44:27 -0400 (EDT) Received: by mail-oi1-x232.google.com with SMTP id bk5so5966926oib.6 for ; Mon, 27 Mar 2023 03:44:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679913866; h=content-transfer-encoding:to:subject:message-id:date:from :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=+Nq2X6wT7cf/ERGeB342dID6HqntUk/ghgQoGLX5h2I=; b=gjvxTFyoSpAYKQHYSerVOtVOZ2jBizRc/ftDrU+5VGPAMwuR5Bv2wilgcfqlVNQLKx 9w6h2NxU1+rgmqR+gfDB7TH7Wo892SszMgeODo6BF33dL+wBUVhXhYb1K7+woV0JQMOk FZVq6ZjuHIV+lJiJvy/HGxuqzGv0BsoWK+NM4EWmDDjRPIc42yHpe53mczCRXUn2+2J2 r3MGc6/k2umaxoCvmPSvJYvmhp0Nmw4zSj1XH8fGkBBrbMVtzJ6cEfgQyAmXRC+Kj1i+ jzVe67iOb6SYCn3qp9FMH/DGDYokWcXPg/hW6gVRrMAwliRiW18e1vwSfOPptCxr/6IQ vzHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679913866; h=content-transfer-encoding:to:subject:message-id:date:from :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+Nq2X6wT7cf/ERGeB342dID6HqntUk/ghgQoGLX5h2I=; b=FSWx7J0aOqTDJFmHREPaIsz++4/Ss3GysfrozJL5iAGzI1jMvPCuQLjl2+/klAkHfQ xfAyjD1dTKaF2i0E65r8O9xUXmeHmPgyLsnKsOUVPBjCaABgLmlwdvI7MAaMEqw72A6/ J2mnE8dzRupu4LsR9Re8tMZoE2envrnbXXgh54NzauKxC3pzQ6pW+4Y31RDaA3oVWkqI b9XoQ9KqrxJJXoVL/6RTAdd0dYXk17DLKiTcjeg5Gwssq0MYRTQtabZKZzBpbIm6SZ90 R0O6Vrb3ugovmZYzIN5L4Z27maXSbMBMg2ArKWOHLsFX1PBQOvjc2e0kfiBD9VCMpBkX C03w== X-Gm-Message-State: AO0yUKXDADQ2zPrNm6ZBxd1LYEaRMaQIkSVV01VdHu6Ws+k3iv7Xt2BD 3rT0bKi6nqQrfgOonwxWgkcmxnF6VD29ug5XKwxDsF7R0O0= X-Google-Smtp-Source: AK7set9d7EloVzXyShCFY6VXdqUG7TTJmKw89fp+XG7SNVmNBGbu8wkW0owOeeCt6ewKwtRjONv41vd/hkx16G9wSgc= X-Received: by 2002:aca:3cc6:0:b0:386:e33f:84f2 with SMTP id j189-20020aca3cc6000000b00386e33f84f2mr2780956oia.1.1679913866562; Mon, 27 Mar 2023 03:44:26 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:6358:108a:b0:112:aa6f:321f with HTTP; Mon, 27 Mar 2023 03:44:26 -0700 (PDT) From: =?UTF-8?Q?David_Fern=C3=A1ndez?= Date: Mon, 27 Mar 2023 12:44:26 +0200 Message-ID: To: starlink@lists.bufferbloat.net Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [Starlink] Starlink ISL data 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, 27 Mar 2023 10:44:27 -0000 I thought Starlink was not supporting IPv6, because of this: https://twitter.com/elonmusk/status/967712110661615616 > Date: Sun, 26 Mar 2023 19:32:31 -0700 > From: Dave Taht > To: Dave Taht via Starlink > Subject: Re: [Starlink] Starlink ISL data > Message-ID: > > Content-Type: text/plain; charset=3D"utf-8" > > Nate gave me the opportunity to test a bit of ipv6 access on one of > his dishys today. I am going to give p2p a shot, also, and he > conveniently has bbr2 installed. It is of course difficult to discern > the difference between transport behaviors and their underlying > connectivity - for example the BBR2 result attached has a baseline > (idle!) latency jump of over 40ms which is hard to explain. > > Despite these plots saying downloads, they were essentially uploads > from his box over the internet. > > The summary of the data I have so far on this direction is: > > Cubic, looks like cubic, usually, but not always. BBR rarely looks like B= BR. > > On Fri, Mar 24, 2023 at 2:46=E2=80=AFPM Dave Taht w= rote: >> >> Vint just asked me a difficult question over here about the >> performance of the ISL links for my upcoming AMA next week >> >> https://twitter.com/mtaht/status/1639361656106156032 >> >> And to date, we really don't know. We do know it is up!? but... >> >> has anyone managed to measure p2p ipv6 performance starlink to >> starlink over an ISL link as yet? Do we know anyone at the poles? In >> general I always look for flent and irtt data, but I'd settle for a, >> oh, call it 5-10 minute long packet capture of single iperf flow, >> running over tcp cubic (bbr would be great too).... one test in each >> direction. >> >> (in fact that would be great from any starlink terminal to any of my >> servers around the world) >> >> I have some data from a couple of you (thx ulrich in particular!), but >> I have not sat down to take it apart as I have been far, far too busy >> with libreqos and a bunch of nice, small, competent ISPs deploying >> that, to worry about fixing a billionaire's network all that much.... >> but I've set aside next week to answer AMAs about everything from all >> and sundry, so if you got data, please share? >> >> -- >> Come Heckle Mar 6-9 at: https://www.understandinglatency.com/ >> Dave T=C3=A4ht CEO, TekLibre, LLC > > > > -- > https://www.youtube.com/watch?v=3DtAVwmUG21OY&t=3D6483s > Dave T=C3=A4ht CEO, TekLibre, LLC > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: tcp_ndown_-_starlink-ipv6-cubic.png > Type: image/png > Size: 145300 bytes > Desc: not available > URL: > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: tcp_ndown_-_starlink-ipv6-bbr2.png > Type: image/png > Size: 64805 bytes > Desc: not available > URL: >