From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (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 34FD63B29E for ; Mon, 17 May 2021 15:30:55 -0400 (EDT) Received: by mail-ej1-x636.google.com with SMTP id lg14so10869572ejb.9 for ; Mon, 17 May 2021 12:30:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=buraglio.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=LVHFBA+UlbJsp9B8/0AfmpsywocufPKdff/LGUyTylc=; b=ZB4iTCfWC/l6FEmhbZcHLhYce0kRA4fWaG4InylmfSHfq8qHCsP3FYodNTYeCr8bqp 6Tf9lV4kQ2ehMKrVDVVz3xAGafVHHTVSswf/cakwZ8fr3PzIyXtA+CQQAvwN6zH0ZJh/ 8TlOujGuM0MFXvJ3ktFvxTTDUHQsa7yYEIRGs= 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=LVHFBA+UlbJsp9B8/0AfmpsywocufPKdff/LGUyTylc=; b=TlIUTNeOjn6KJMdxRuhw/4Yrg8drEbZAZ7EndnG+a3mYej3ngxeLiwZ1O8Nss6lr8y OFWCFcTsih69/59b3fenOv2LM2WdQY+6sUqavCii/25oTeO/k9blql6yQVS6tMfh34zH yyn5NSdoHHIZkc40Xi45+KYuZGoXUPBs1v0ePKPFOfU4hNQUGC+hLYIgUP9RfxdiJKG0 sGhmTzowhn5ERHKWumE83o9fySdzbVBEGmlpHc+NgXu6G7HQnUFRk0+IhGSbyLcc5Cy6 8rKN+BziR0pX0h7NQcOTWqi3Fqky3ptjcrNYaFJboYlBEgxyUy2LmwKgtvtT//m0N473 oUPQ== X-Gm-Message-State: AOAM530dpppKYwTyekQb0Nh9IeYdTdkcxkDcg1AoK2raES9UniPNdSb6 oIhm8CUN/bl2tR3WgAycJHo4jgWQhH+i5Z2q+i1T7w== X-Google-Smtp-Source: ABdhPJwe5F39qzOZjz0K490zMgu2myU0h9UVmM3LQ3Qyxy5N0KN2F/iIz6W9ACJ5yeJWBaUDxgey/VbMv0fepwtqGQA= X-Received: by 2002:a17:906:1b42:: with SMTP id p2mr1577158ejg.550.1621279853875; Mon, 17 May 2021 12:30:53 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Nick Buraglio Date: Mon, 17 May 2021 14:30:42 -0500 Message-ID: To: Dave Taht Cc: Starlink@lists.bufferbloat.net Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [Starlink] dhcpv6-pd details 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, 17 May 2021 19:30:55 -0000 Inline On Mon, May 17, 2021 at 2:15 PM Dave Taht wrote: > > On Mon, May 17, 2021 at 12:04 PM Nick Buraglio wrote: > > > > As discussed privately with Dave, I have removed the starlink provided > > router and replaced it with a Mikrotik RB2011 to allow for more > > Running routerOS? Latest beta's of that have cake in 'em. I have the latest on a device in my home lab, but it's definitely not ready for prime time. Here are some packet captures directly from the Mikrotik using the "sniffer" command. It's not terribly useful, but here it is: reading from file dhcpv6, link-type EN10MB (Ethernet) 14:16:54.570633 IP6 fe80::4e5e:cff:fe1a:7f3d.546 > ff02::1:2.547: dhcp6 rel= ease 14:17:03.087352 IP6 fe80::4e5e:cff:fe1a:7f3d.546 > ff02::1:2.547: dhcp6 sol= icit 14:17:03.142612 IP6 fe80::1.547 > fe80::4e5e:cff:fe1a:7f3d.546: dhcp6 adver= tise 14:17:04.035913 IP6 fe80::4e5e:cff:fe1a:7f3d.546 > ff02::1:2.547: dhcp6 req= uest 14:17:04.075914 IP6 fe80::1.547 > fe80::4e5e:cff:fe1a:7f3d.546: dhcp6 reply > > > granular control, and to better tie into my existing network. > > Starlink provides a router, also? I'm so confused. I thought the dishy > was all there was. Care to tear it apart and describe what's in it? As far as the "router" is concerned, it's very much a consumer grade device that is managed via the mobile app. I hated it, so I took it out. It's still up in the attic. near the cable conduit, if I recall. > > > This has > > allowed me to make a dhcpv6-pd request that is reasonably stable (so > > far it has changed once in the last 2 months). The lease time is > > incredibly short, which is a little strange but as long as the DHCPv6 > > server is the same and remains unchanged, it should just hand out the > > same prefix upon request. > > That was a terrible habit that comcast had got into in the early days > that forced > openwrt to flush and reload the firewall every minute, or less. > > I'd pioneered a stateless firewall in cerowrt that never ever ever > needed to reload the > rules, using a pattern match for each specifically renamed ethernet inter= face. > > Regrettably that was not accepted into openwrt, because "nftables" was > just around the corner. > It scaled beautifully to tons of interfaces going up and down so long > as they were named appropriately, > at far less cpu overhead for complicated rules than the standard > openwrt firewall. > > https://www.bufferbloat.net/projects/cerowrt/wiki/CeroWall/?version=3D9 > > Anyway, I don't remember all that we did to suppress the flood of > useless static changes > to everything ipv6, but I hope that whatever we ended up doing still > works in this case. > > > I also built a very crude measurement display that just uses curl get > > and dig via smokeping to display reasonable RTT. It's detailed in the > > reddit post here: > > https://www.reddit.com/r/Starlink/comments/mykxjv/functional_ipv6_and_s= ome_crude_starlink_latency/ > > and can be viewed directly here: > > https://starmon.qosbox.com/ > > THX! We really need to collect the "good" information and publish it > somewhere, the reddit noise level is too high. > > One piece of mis-information I think was the news you can "route" > packets over ipv4 with a box in front of it and > a default gw of 192.168.100.1 Not clear from that news whether or not > NAT was required on the next hop or not... ? The 192.168.100.1 address is the default address of the dish, all of the statistical information resides on the dish itself. With a simple static route it is pretty simple to remove the home wifi gateway mentioned above and just look at the statistics on the disk itself - it's literally just a web page and an API. The 192.168.100.1 is similar to the cable modem bridges that display their channel sync statistics, it's a commonly used address on CPE. As far as NAT, it's all CGN, so there is no public IPv4 addressing (hence my strong desire to make IPv6 work ASAP). All IP space seems to be delegated from Google in one way or another, v4 and v6 are both via GoogleWifi (AS36492). First hop transit is Google (AS15169), so it looks a lot like the google fiber backbone. > > (that's from another reddit post I mis-remember) > > > > > Making dhcpv6-pd work is pretty standard: > > > > /ipv6 dhcp-client > > > > add add-default-route=3Dyes interface=3Dether2 pool-name=3Dstarlink-ipv= 6 > > prefix-hint=3D::/56 request=3Dprefix > > > > On each interface you want to have IPv6 on: > > > > /ipv6 address > > > > add address=3D::1 from-pool=3Dstarlink-ipv6 interface=3Dbridge.8 > > > > add address=3D::1 from-pool=3Dstarlink-ipv6 interface=3Dbridge.6 > > THANKS SO MUCH. I am thinking at the moment that openwrt's dhcp-pd > implementation is currently > broken (it's not working on admittedly a comcast modem I just got that > I'd not used before), but > as soon as I get a chance I'll try configuring odhcpd6 to do something > like this. If I can remember how. > > > > _______________________________________________ > > Starlink mailing list > > Starlink@lists.bufferbloat.net > > https://lists.bufferbloat.net/listinfo/starlink > > > > -- > Latest Podcast: > https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/ > > Dave T=C3=A4ht CTO, TekLibre, LLC