From: Nathan Owens <nathan@nathan.io>
To: Dave Taht <dave.taht@gmail.com>
Cc: Nick Buraglio <nick@buraglio.com>, Starlink@lists.bufferbloat.net
Subject: Re: [Starlink] dhcpv6-pd details
Date: Mon, 17 May 2021 12:37:30 -0700 [thread overview]
Message-ID: <CALjsLJu90M+nUP5ZSLw-yRRLOSD5n+Ln0spGzNB=Db5JABxdyA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4M3J5E-taXnTWqytJ-LoPBuP=EaeVdHvU6iHAqiBjfJA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4195 bytes --]
> 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 is what I was talking about in the other thread — there is a provided
router, its Qualcomm IPQ40xx based, and seems to run OpenWrt
The dish runs a custom ST Microelectroncis chip, and unknown firmware.
On Mon, May 17, 2021 at 12:15 PM Dave Taht <dave.taht@gmail.com> wrote:
> On Mon, May 17, 2021 at 12:04 PM Nick Buraglio <nick@buraglio.com> 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
> interface.
>
> 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=9
>
> 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_some_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=yes interface=ether2 pool-name=starlink-ipv6
> > prefix-hint=::/56 request=prefix
> >
> > On each interface you want to have IPv6 on:
> >
> > /ipv6 address
> >
> > add address=::1 from-pool=starlink-ipv6 interface=bridge.8
> >
> > add address=::1 from-pool=starlink-ipv6 interface=bridge.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äht CTO, TekLibre, LLC
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #2: Type: text/html, Size: 6421 bytes --]
next prev parent reply other threads:[~2021-05-17 19:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 18:58 Nick Buraglio
2021-05-17 19:15 ` Dave Taht
2021-05-17 19:30 ` Nick Buraglio
2021-05-17 19:36 ` David Lang
2021-05-17 19:48 ` Nick Buraglio
2021-05-17 19:59 ` Dave Taht
2021-05-17 21:02 ` Nick Buraglio
2021-05-17 23:56 ` Dave Taht
2021-05-18 2:21 ` Nick Buraglio
2021-05-18 6:51 ` Gert Doering
2021-05-17 19:37 ` Nathan Owens [this message]
2021-05-18 8:33 ` Annika Wickert
2021-05-18 11:37 ` Nick Buraglio
2021-05-18 11:41 ` Annika Wickert
2021-05-18 14:48 ` Nick Buraglio
2021-05-18 14:50 ` Annika Wickert
2021-06-06 3:41 ` Darrell Budic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALjsLJu90M+nUP5ZSLw-yRRLOSD5n+Ln0spGzNB=Db5JABxdyA@mail.gmail.com' \
--to=nathan@nathan.io \
--cc=Starlink@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=nick@buraglio.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox