From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (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 B93463B2A4 for ; Tue, 18 May 2021 11:24:10 -0400 (EDT) Received: by mail-io1-xd34.google.com with SMTP id z24so9791226ioi.3 for ; Tue, 18 May 2021 08:24:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nathan.io; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+K2qN111y/uRP9gZBMRNQSe3aqH9sbwapZBet/UjxKk=; b=gJQfUUjaYwfdmXpgQYCZ3m/hH72QOhCA+F9gWizXsbvsEO12VyqQb/pKPZrxBLePFa SgE39Mcv7pqcK+gr8vEYQF6UGI4fL2/C5NBDmq+xwFs+SRDu02Aodaex070iU6fSmN5v PYT02i6JUQdR/+G+B9YsAQJsd8ccZ71am+AB5w6RUFv4fiSr2qs6lgPvU0CcpYdWNpDT fVuoYe2Mn6xv2JeJDFexY2iQj7JsASuKFq+PfW6bY86INXfdII27l0x0RIU0OS5ywLaG uaWKMNUKfWKxkVMhWcamLQnj8ysfyog86cl13zQW1PCjM8m2pzwk64n+9XiyojMM//2b ZvlQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+K2qN111y/uRP9gZBMRNQSe3aqH9sbwapZBet/UjxKk=; b=IJ9XFKRT22p6Ur/PCl9Yr1xcJX0UHi8bfJgLcFM+f/Qil3bG7JH5hWHTREgSCjfbZW CJjO/FqGme3FSSO8VchDJS4k3O4EGxvZN8pkXSxj7h6IecjP5Mgc1LdD/v04eDMZKBBP SbgvIaebVUfQDVo02dRjHCfo5JgCI5WqpOB3roAyso5T+okfY8yIy2PA5bXe+ytOUoyb e2nO92ZAoBVwtbvcLTxu5M92mMOv/8o9IG5B8qsWc0nfba3kMznK8UqiivTfVvlrCiYX EvOGcXj2/Z+fob+GzIzva0Tjf2qyJTcIOE735CPTp/goA5T2RHeX/QN2Fwuelg0wM2pS gcqA== X-Gm-Message-State: AOAM533Ikan6/x011mwZ/9dJt8e9SVuCCfEO7q08P6Z2j073rwYocqx2 0gPda8nYyuA1VSh+86/exLTVqZ1CQjeoiuz6wG2DWQ== X-Google-Smtp-Source: ABdhPJzGW6cNXMCe+ANkFTg3dj7Eue9m7nsxjHJy6+lepBUo3iNkHh3moZpW+L3tq0rW2Hy4eXgDi4WJg28mck34BxY= X-Received: by 2002:a5d:818c:: with SMTP id u12mr4554695ion.81.1621351449994; Tue, 18 May 2021 08:24:09 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Nathan Owens Date: Tue, 18 May 2021 08:23:59 -0700 Message-ID: To: Dave Taht Cc: starlink@lists.bufferbloat.net Content-Type: multipart/alternative; boundary="0000000000003bc0cd05c29c4d58" Subject: Re: [Starlink] teardown of the starlink provided "router" 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: Tue, 18 May 2021 15:24:10 -0000 --0000000000003bc0cd05c29c4d58 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Here ya go: https://fcc.report/FCC-ID/2AWHPR201/4805890 There's at least one teardown video, but the FCC pics are better. Qualcomm IPQ4018, can run OpenWrt 19.07.7, or the latest 21.02.1 RC branch. --Nathan On Tue, May 18, 2021 at 8:20 AM Dave Taht wrote: > I would really like someone to disassemble, and take photographs of > the chipset and design of the starlink provided "router", > which is proving to be such a disaster, and put those up somewhere. > Youtube videos seem to be popular... we could do a > kvetchy one of those? > > I have really goofed in that my visit to the starlink site I'd assumed > the dishy was all there was! At one level I'm deliriously happy > that that router can be junked, and with a decent OS, ipv6 etc can be > enabled, as well as many other interesting local > networking services. At another level I'm grumpy as to have to throw > out all the bufferbloat related testing to date. > > In my dream world, the dishy would do ethernet flow control at a > "single transmit upstream buffer" granularity, below 4ms, and > emit pause frames that an fq_codel upstream could deal with, but that > still is not enough, accurate parsing of the dishy's actual link rates > up and down would allow for controlling the sch_cake queues tighter. > > -- > Latest Podcast: > https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/ > > Dave T=C3=A4ht CTO, TekLibre, LLC > _______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/starlink > --0000000000003bc0cd05c29c4d58 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Th= ere's at least one teardown video, but the FCC pics are better.

Qualcomm IPQ4018, can run OpenWrt 19.07.7, or the la= test 21.02.1 RC branch.

--Nathan

On= Tue, May 18, 2021 at 8:20 AM Dave Taht <dave.taht@gmail.com> wrote:
I would really like someone to disassemble, and = take photographs of
the chipset and design of the starlink provided "router",
which is proving to be such a disaster, and put those up somewhere.
Youtube videos seem to be popular... we could do a
=C2=A0kvetchy one of those?

I have really goofed in that my visit to the starlink site I'd assumed<= br> the dishy was all there was! At one level I'm deliriously happy
that that router can be junked, and with a decent OS, ipv6 etc can be
enabled, as well as many other interesting local
networking services. At another level I'm grumpy as to have to throw out all the bufferbloat related testing to date.

In my dream world, the dishy would do ethernet flow control at a
"single transmit upstream buffer" granularity, below 4ms, and
emit pause frames that an fq_codel upstream could deal with, but that
still is not enough, accurate parsing of the dishy's actual link rates<= br> up and down would allow for controlling the sch_cake queues tighter.

--
Latest Podcast:
https://www.linkedin.com/fe= ed/update/urn:li:activity:6791014284936785920/

Dave T=C3=A4ht CTO, TekLibre, LLC
_______________________________________________
Starlink mailing list
Starlin= k@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink
--0000000000003bc0cd05c29c4d58--