From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (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 7467F3B2A4 for ; Tue, 18 May 2021 12:32:29 -0400 (EDT) Received: by mail-io1-xd2c.google.com with SMTP id d11so10033306iod.5 for ; Tue, 18 May 2021 09:32:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=xUySHMkfI3PFrLrg6GQxCkP6TRdZHN397gGVSsPhPyE=; b=fsYJHfgjpRCcPoKZ2zdD5DOHcSJSl294/xkPI6yYo29d/i5ABLag9z1JNTOHSq+EFo bDRjoWyzjM7vpYJ2u1tsns+E8cIUiQIOAZ1fBbiZof/LaNLIdbxx7U+iQw0/Y64UZPqF 8uaKw/uPaLVhFquskykc5WM1Y/B++wes/AThmvh6w22/EgV2nyY9JnPbP5v5fUi0iMCC utvqQ37UdSFBAekzHXDqPhO1a0edZOHAv5iGNcg3vmGo0lFKGGL44sGNziKmxriGF1OK UesvTMaRCIH8WMojj42eWvQ5PXuEeo0+NEJAVfYcihKeZ+Z1zg67gB3cMZgP0LrH0ZST PbwQ== 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:content-transfer-encoding; bh=xUySHMkfI3PFrLrg6GQxCkP6TRdZHN397gGVSsPhPyE=; b=UqL+Mtj19zGcnLdSWUpSiP3w495Tmxag6ixfc4Kqc0l6GwMyvT2VbalJH/DFlRQtGb HnInAO4OJyFTpg0r/LbVK36rJCVzvVN4JGjoWHT6jyMQcav/m8Yt/zCk0T3FuPwT+QBB M7VgJPpiKpA6fsAJ0ORguYtyMcjxlbHFylq1NyXSUd7t8ty/BtZNViAccWl46zqdi0kF AdZQ7mY0zCLUPfXK8g3oReHC+FpU6kbvVe+MwuDpGHSdtYbJUxJNvkvDQv4msZmqgslH +y5Fl6YMIFdRnCoigzaPs4GiCmDocDHcVssNGeJ9RpBpEDBq+G90LSvVDI9R+skomjg8 yMjg== X-Gm-Message-State: AOAM532Wf8q8Q/nka5a/TlkXN3O6WtAgFy/+PmABDxh8P9OthtI+GrQD M8UZbrnmKaqaRL+o/uyJcJOVRRNFMl+gixM7UOK/cp2jnJI= X-Google-Smtp-Source: ABdhPJzblm7Dig0l6fXy2ISZFzijyRb4pu4zKMmB1bZTDxl1zfxQrlqCXBtDsabmITL0Qs1oouF6FbyfZSF86O6zXEs= X-Received: by 2002:a6b:d918:: with SMTP id r24mr4847144ioc.25.1621355548939; Tue, 18 May 2021 09:32:28 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dave Taht Date: Tue, 18 May 2021 09:32:17 -0700 Message-ID: To: Nathan Owens Cc: starlink@lists.bufferbloat.net Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 16:32:29 -0000 On Tue, May 18, 2021 at 8:28 AM Nathan Owens wrote: > > 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 h= eat-spreader capped ones. Parts seem to be custom, nothing I could find onl= ine. > > The Dish acts as the modem, so any router can be used. How were you testi= ng? With their router? Without? behind their router. this explains my issues with ipv6, and at least some, with bufferbloat. We will toss the starlink router over the cliff soon and start over. > > > 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 bran= ch. >> >> --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:679101428493678592= 0/ >>> >>> Dave T=C3=A4ht CTO, TekLibre, LLC >>> _______________________________________________ >>> Starlink mailing list >>> Starlink@lists.bufferbloat.net >>> https://lists.bufferbloat.net/listinfo/starlink --=20 Latest Podcast: https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/ Dave T=C3=A4ht CTO, TekLibre, LLC