From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (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 293F03B2A4 for ; Tue, 18 May 2021 11:28:14 -0400 (EDT) Received: by mail-io1-xd35.google.com with SMTP id z24so9805264ioi.3 for ; Tue, 18 May 2021 08:28:14 -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=0xpiSfKykT2WLXXc1ZaEkZtSMWDxXD9MGEAuXCyf+zs=; b=KGZ6Rq1Z1jI5WpGc2CSlAYfBczh/Cflnuwv3F3L+jlG5xklCj+n/SzaxIq0F7DKnuf HK1X3ax+nOjkI5YlHa55U+xJ5OQ0KuWaGCj4Kmof+ME8TkuTXS+LeEvAwQ7Fnn8UGQCp ey4d7WAsWgb4Ewq4HwKFWhO7HsyymuVMTDWGZR7pGtrYs0x8TU6SmD4iAh4P3BJmZiCL zq08o4rTXNC5wKR8icmv255pUQPOaVNf13MoIIy+Nv/nudiOTCuaHlHMX11va55znuSQ r9Qqx8Vrhk+KIhW+OqfSeq06WOUxorq0ogGoSUFCscjPZKKzidUYKg+KFhDRAIBRynFI +pVg== 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=0xpiSfKykT2WLXXc1ZaEkZtSMWDxXD9MGEAuXCyf+zs=; b=dPY2lQUFTQHCaIwUQPvPu2hrQnHsRVnXIH75WEUot9cwDaoJDIChCxfs2NhjQ+W1G3 EWYF8vQYPRSL30DBzVapKNQOaL0nPdc7rRcuse1PTBSW9+Y3taoZXZTHBbOGZWwpoaR8 aftBDPbRfD12rTjrAZhPYSYni7JOc3/jvqV57p0rVtv2cGrdUoHZsGC8sZWZk2P2V6Ot Tka5QMm0xqALqPwCof3AlNTJ8bEgjQJ9cPyd+SrakBaFDwKDkP8KkafarFZf4yv9/Unk 741IUBIXWFqxPpFZgWtv0hr8GMnCfpvb2u/iEg949b6jbFErNgCsB8PsYybDHqdN7W91 A8CA== X-Gm-Message-State: AOAM532BeBjV5fkXVP2wbdl61JoeJl+8+vsrFaMwCWSAxyr0nMlSJbYM vu/UbDaPYLZ7IGkRjb5zNtq+FpboUHDfRhZBGoVZVw== X-Google-Smtp-Source: ABdhPJwZSJtmobU9qrWEaIPgG6OERG5b1Itzqct039/dDydGVxHt64fqe3VXrHB+1kuwcPKx4+ow+XK/txs/RFMwdU0= X-Received: by 2002:a02:9621:: with SMTP id c30mr6076869jai.113.1621351693393; Tue, 18 May 2021 08:28:13 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Nathan Owens Date: Tue, 18 May 2021 08:28:02 -0700 Message-ID: To: Dave Taht Cc: starlink@lists.bufferbloat.net Content-Type: multipart/alternative; boundary="000000000000bdab6c05c29c5b11" 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:28:14 -0000 --000000000000bdab6c05c29c5b11 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Here are the chips in the dish: https://twitter.com/VirtuallyNathan/status/1331709138276024320 There's a bunch of the black ones, some sort of RF chip, and one of the heat-spreader capped ones. Parts seem to be custom, nothing I could find online. The Dish acts as the modem, so any router can be used. How were you testing? With their router? Without? On Tue, May 18, 2021 at 8:23 AM Nathan Owens wrote: > 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 >> > --000000000000bdab6c05c29c5b11 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Here are the chips in the dish:
There= 's a bunch of the black ones, some sort of RF chip, and one of the heat= -spreader capped ones. Parts seem to be custom, nothing I could find online= .

The Dish acts as the modem, so any router c= an be used. How were you testing? With their router? Without?



On Tue, May 18, 2021 at 8:23 AM Nathan Owens <nathan@nathan.io> wrote:
There's at le= ast 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, 2= 021 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
--000000000000bdab6c05c29c5b11--