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 C42B13B29E for ; Mon, 17 May 2021 15:15:29 -0400 (EDT) Received: by mail-io1-xd34.google.com with SMTP id n40so6955664ioz.4 for ; Mon, 17 May 2021 12:15: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=PCiE7D9Yw/9xFTY3SCevrTx11JzkmSWUc1DyBb8qkfE=; b=rD8Hb8cSAyLUOa/tXYFhnXeo7kpUhNvy8z93mUaC3FaepV1tAYbUI76RO+Y4YyarMZ E6w7I26vu4R9NwiNM9mrPph5AeUna7jrmVZRKclKwmW03GTGOH6pz9GIDme4ZwjSRVjA Gi0a8dJ/nul6TwyyFVxGApKS0AprwicJdkbmWkgZGfdVhQTniAKpePWz7sBPlSR79N+2 +c+KIvC7LLXKo4+t2miWGr4uyTKZT2GNz2oIFUF2R2LktFxRgulpCAzy09mfdWf1Txtf XCST7uadAp2RGVPM9NIjaV3ZlOtc8cqm/kzLMBPBBsLFW2fJpM6jXv78vDSmVnTLMMau RA0Q== 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=PCiE7D9Yw/9xFTY3SCevrTx11JzkmSWUc1DyBb8qkfE=; b=B56zM7TbegxYtdbVehgv72FiQpTlLjmmLergJzkjdte9HsaZ9zAIbBP7m20nv3YaCm oGtT+rZHJzHqhw1tr7FoOE6NNTFz/iOsWbETHPzz3Fe3wQI+3c2BRS/sNnMhFR3cg7Uq 4i09W1gGE3b/IwwDokC5g1T9VCOEgEUV+BaCmyCed2y3C3wjFwbSV1GsujW9SHFrbKYj ApmS29KGObnKk3VzAznFW/WIBkRPIgRlcl0irEM7JiSf9Nc2Ep+ruUTNvd67Rxof/ZDa AtjRKybxvFeg32UHzxYWZTbuYkuc49eZT+nSICCAtGJgkRRA7ZmwnwdUTdBwJCCHtIEv bgYA== X-Gm-Message-State: AOAM533wux9mKwnUh2WxHlSWoWdIBiqcfZ6DzAdW2nFtOnxtJvOevNDk NCLMsv24kiGcO2jzQFaeixDR9hgEaiTSnbE156+exFxz0Gw= X-Google-Smtp-Source: ABdhPJzy7UHsa0YddAkN4y93fPBWHYXlNpFOyif0nV8WtBEW5OGV0sQcrmRnMbxZ/nEW1XTfNgIh8gMXRIRQBKxDSWM= X-Received: by 2002:a05:6638:10c4:: with SMTP id q4mr1481574jad.29.1621278929117; Mon, 17 May 2021 12:15:29 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dave Taht Date: Mon, 17 May 2021 12:15:18 -0700 Message-ID: To: Nick Buraglio 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:15:29 -0000 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. > 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? > 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 interfa= ce. 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_som= e_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... ? (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-ipv6 > 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 --=20 Latest Podcast: https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/ Dave T=C3=A4ht CTO, TekLibre, LLC