[Starlink] dhcpv6-pd details

[Starlink] dhcpv6-pd details

[Nick Buraglio]

As discussed privately with Dave, I have removed the starlink provided
router and replaced it with a Mikrotik RB2011 to allow for more
granular control, and to better tie into my existing network. 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.
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/

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

Re: [Starlink] dhcpv6-pd details

[Dave Taht]

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

Re: [Starlink] dhcpv6-pd details

[Nick Buraglio]

Inline

On Mon, May 17, 2021 at 2: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.

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 release
14:17:03.087352 IP6 fe80::4e5e:cff:fe1a:7f3d.546 > ff02::1:2.547: dhcp6 solicit
14:17:03.142612 IP6 fe80::1.547 > fe80::4e5e:cff:fe1a:7f3d.546: dhcp6 advertise
14:17:04.035913 IP6 fe80::4e5e:cff:fe1a:7f3d.546 > ff02::1:2.547: dhcp6 request
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 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... ?

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=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

Re: [Starlink] dhcpv6-pd details

[David Lang]

On Mon, 17 May 2021, Nick Buraglio wrote:

> Inline
>
> On Mon, May 17, 2021 at 2:15 PM Dave Taht <dave.taht@gmail.com> wrote:
>>
>> 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.

Fantastic, I was hoping it would be something like this. I think this opens up a 
lot of more useful options (including more easily doing failover between the 
dish and other network options)

David  Lang

Re: [Starlink] dhcpv6-pd details

[Nathan Owens]

[-- 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 --]

Re: [Starlink] dhcpv6-pd details

[Nick Buraglio]

[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]

I have this working now between my providers with straight routing and
gateway checking, but it’s pretty easily doable other ways with platforms
like routerOS or pfsense.
FWIW, I’m working with some others on an IETF draft proposal that will
hopefully solve the plaguing problem of multiple IPv6 PD or otherwise
provider assigned address blocks that will make a lot of that easier, too.

nb


On Mon, May 17, 2021 at 2:36 PM David Lang <david@lang.hm> wrote:

> On Mon, 17 May 2021, Nick Buraglio wrote:
>
> > Inline
> >
> > On Mon, May 17, 2021 at 2:15 PM Dave Taht <dave.taht@gmail.com> wrote:
> >>
> >> 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.
>
> Fantastic, I was hoping it would be something like this. I think this
> opens up a
> lot of more useful options (including more easily doing failover between
> the
> dish and other network options)
>
> David  Lang
>

[-- Attachment #2: Type: text/html, Size: 2046 bytes --]

Re: [Starlink] dhcpv6-pd details

[Dave Taht]

On Mon, May 17, 2021 at 12:48 PM Nick Buraglio <nick@buraglio.com> wrote:
>
> I have this working now between my providers with straight routing and gateway checking, but it’s pretty easily doable other ways with platforms like routerOS or pfsense.
> FWIW, I’m working with some others on an IETF draft proposal that will hopefully solve the plaguing problem of multiple IPv6 PD or otherwise provider assigned address blocks that will make a lot of that easier, too.

Hmm? We solved this long ago in  cerowrt, openwrt, and in linux, by
using "source specific routing", which is the default for many openwrt
derived OSes.

Basically it looks like this:

ip route add from 2001:abcd::/56 via whatever
ip route add from 2001:dbcd::/56 via whatever2

You then distribute both sets of ipv6 addresses to the clients. Simple
clean and it solved the bcp38 problem because there is no
default route for any but these ipv6 addresses in the system. It works
well for vpns also.

Happy eyeballs takes care of the rest.

https://datatracker.ietf.org/doc/html/draft-ietf-babel-source-specific-08
describes how we added it to the babel routing protocol
as well, so best hops can be easily chosen in a more complex network.
In case I had 5+ comcast uplinks spread across a wifi campus so having
multiple uplinks and failover was needed. It's been up and running
for... 7 years?

https://en.wikipedia.org/wiki/Source-specific_routing also made it
into a few other places.

I'm pretty certain every other OS completely missed this key feature
of course including your mikrotik




>
> nb
>
>
> On Mon, May 17, 2021 at 2:36 PM David Lang <david@lang.hm> wrote:
>>
>> On Mon, 17 May 2021, Nick Buraglio wrote:
>>
>> > Inline
>> >
>> > On Mon, May 17, 2021 at 2:15 PM Dave Taht <dave.taht@gmail.com> wrote:
>> >>
>> >> 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.
>>
>> Fantastic, I was hoping it would be something like this. I think this opens up a
>> lot of more useful options (including more easily doing failover between the
>> dish and other network options)
>>
>> David  Lang



-- 
Latest Podcast:
https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/

Dave Täht CTO, TekLibre, LLC

Re: [Starlink] dhcpv6-pd details

[Nick Buraglio]

[-- Attachment #1: Type: text/plain, Size: 3436 bytes --]

The issue with this methodology (which I have used myself) is that it
relies on the host stack to do the heavy lifting. Our draft handles most,
if not all of this at the CPE, which will allow for a significant amount of
flexibility and reduction of complexity at the host layer. That is a fairly
large oversight in the operational model for 90% of v6 users that aren't
running BGP. One goal we have is to reduce the time to connectivity
failover and make deterministic IPv6 paths easily implemented by
non-technical folks, and to create a standard for all CPE to implement with
as minimal CPU as possible.

nb

On Mon, May 17, 2021 at 2:59 PM Dave Taht <dave.taht@gmail.com> wrote:

> On Mon, May 17, 2021 at 12:48 PM Nick Buraglio <nick@buraglio.com> wrote:
> >
> > I have this working now between my providers with straight routing and
> gateway checking, but it’s pretty easily doable other ways with platforms
> like routerOS or pfsense.
> > FWIW, I’m working with some others on an IETF draft proposal that will
> hopefully solve the plaguing problem of multiple IPv6 PD or otherwise
> provider assigned address blocks that will make a lot of that easier, too.
>
> Hmm? We solved this long ago in  cerowrt, openwrt, and in linux, by
> using "source specific routing", which is the default for many openwrt
> derived OSes.
>
> Basically it looks like this:
>
> ip route add from 2001:abcd::/56 via whatever
> ip route add from 2001:dbcd::/56 via whatever2
>
> You then distribute both sets of ipv6 addresses to the clients. Simple
> clean and it solved the bcp38 problem because there is no
> default route for any but these ipv6 addresses in the system. It works
> well for vpns also.
>
> Happy eyeballs takes care of the rest.
>
> https://datatracker.ietf.org/doc/html/draft-ietf-babel-source-specific-08
> describes how we added it to the babel routing protocol
> as well, so best hops can be easily chosen in a more complex network.
> In case I had 5+ comcast uplinks spread across a wifi campus so having
> multiple uplinks and failover was needed. It's been up and running
> for... 7 years?
>
> https://en.wikipedia.org/wiki/Source-specific_routing also made it
> into a few other places.
>
> I'm pretty certain every other OS completely missed this key feature
> of course including your mikrotik
>
>
>
>
> >
> > nb
> >
> >
> > On Mon, May 17, 2021 at 2:36 PM David Lang <david@lang.hm> wrote:
> >>
> >> On Mon, 17 May 2021, Nick Buraglio wrote:
> >>
> >> > Inline
> >> >
> >> > On Mon, May 17, 2021 at 2:15 PM Dave Taht <dave.taht@gmail.com>
> wrote:
> >> >>
> >> >> 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.
> >>
> >> Fantastic, I was hoping it would be something like this. I think this
> opens up a
> >> lot of more useful options (including more easily doing failover
> between the
> >> dish and other network options)
> >>
> >> David  Lang
>
>
>
> --
> Latest Podcast:
> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
>
> Dave Täht CTO, TekLibre, LLC
>

[-- Attachment #2: Type: text/html, Size: 4609 bytes --]

Re: [Starlink] dhcpv6-pd details

[Dave Taht]

[-- Attachment #1: Type: text/plain, Size: 4334 bytes --]



> On May 17, 2021, at 2:02 PM, Nick Buraglio <nick@buraglio.com> wrote:
> 
> The issue with this methodology (which I have used myself) is that it relies on the host stack to do the heavy lifting.

Ah, we are talking about two slightly
different things.

I was unhappy with relying on happy eyeballs for failover in the clients, but withdrawing the address that were not working did not work well with any clients we had at time.

May I have a peek at your draft?

> Our draft handles most, if not all of this at the CPE,

It would be cool to implement something better at the cpe.

> which will allow for a significant amount of flexibility and reduction of complexity at the host layer. That is a fairly large oversight in the operational model for 90% of v6 users that aren't running BGP. One goal we have is to reduce the time to connectivity failover and make deterministic IPv6 paths easily implemented by non-technical folks, and to create a standard for all CPE to implement with as minimal CPU as possible. 
> 
> nb 
> 
> On Mon, May 17, 2021 at 2:59 PM Dave Taht <dave.taht@gmail.com <mailto:dave.taht@gmail.com>> wrote:
> On Mon, May 17, 2021 at 12:48 PM Nick Buraglio <nick@buraglio.com <mailto:nick@buraglio.com>> wrote:
> >
> > I have this working now between my providers with straight routing and gateway checking, but it’s pretty easily doable other ways with platforms like routerOS or pfsense.
> > FWIW, I’m working with some others on an IETF draft proposal that will hopefully solve the plaguing problem of multiple IPv6 PD or otherwise provider assigned address blocks that will make a lot of that easier, too.
> 
> Hmm? We solved this long ago in  cerowrt, openwrt, and in linux, by
> using "source specific routing", which is the default for many openwrt
> derived OSes.
> 
> Basically it looks like this:
> 
> ip route add from 2001:abcd::/56 via whatever
> ip route add from 2001:dbcd::/56 via whatever2
> 
> You then distribute both sets of ipv6 addresses to the clients. Simple
> clean and it solved the bcp38 problem because there is no
> default route for any but these ipv6 addresses in the system. It works
> well for vpns also.
> 
> Happy eyeballs takes care of the rest.
> 
> https://datatracker.ietf.org/doc/html/draft-ietf-babel-source-specific-08 <https://datatracker.ietf.org/doc/html/draft-ietf-babel-source-specific-08>
> describes how we added it to the babel routing protocol
> as well, so best hops can be easily chosen in a more complex network.
> In case I had 5+ comcast uplinks spread across a wifi campus so having
> multiple uplinks and failover was needed. It's been up and running
> for... 7 years?
> 
> https://en.wikipedia.org/wiki/Source-specific_routing <https://en.wikipedia.org/wiki/Source-specific_routing> also made it
> into a few other places.
> 
> I'm pretty certain every other OS completely missed this key feature
> of course including your mikrotik
> 
> 
> 
> 
> >
> > nb
> >
> >
> > On Mon, May 17, 2021 at 2:36 PM David Lang <david@lang.hm <mailto:david@lang.hm>> wrote:
> >>
> >> On Mon, 17 May 2021, Nick Buraglio wrote:
> >>
> >> > Inline
> >> >
> >> > On Mon, May 17, 2021 at 2:15 PM Dave Taht <dave.taht@gmail.com <mailto:dave.taht@gmail.com>> wrote:
> >> >>
> >> >> 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.
> >>
> >> Fantastic, I was hoping it would be something like this. I think this opens up a
> >> lot of more useful options (including more easily doing failover between the
> >> dish and other network options)
> >>
> >> David  Lang
> 
> 
> 
> -- 
> Latest Podcast:
> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/ <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: 6764 bytes --]

Re: [Starlink] dhcpv6-pd details

[Nick Buraglio]

[-- Attachment #1: Type: text/plain, Size: 4360 bytes --]

Once we get a bit for there I’ll send it over. It’s not my idea, I’m a
contributor so I’ll need to ask first.

On Mon, May 17, 2021 at 6:56 PM Dave Taht <davet@teklibre.net> wrote:

>
>
> On May 17, 2021, at 2:02 PM, Nick Buraglio <nick@buraglio.com> wrote:
>
> The issue with this methodology (which I have used myself) is that it
> relies on the host stack to do the heavy lifting.
>
>
> Ah, we are talking about two slightly
> different things.
>
> I was unhappy with relying on happy eyeballs for failover in the clients,
> but withdrawing the address that were not working did not work well with
> any clients we had at time.
>
> May I have a peek at your draft?
>
> Our draft handles most, if not all of this at the CPE,
>
>
> It would be cool to implement something better at the cpe.
>
> which will allow for a significant amount of flexibility and reduction of
> complexity at the host layer. That is a fairly large oversight in the
> operational model for 90% of v6 users that aren't running BGP. One goal we
> have is to reduce the time to connectivity failover and make deterministic
> IPv6 paths easily implemented by non-technical folks, and to create a
> standard for all CPE to implement with as minimal CPU as possible.
>
> nb
>
> On Mon, May 17, 2021 at 2:59 PM Dave Taht <dave.taht@gmail.com> wrote:
>
>> On Mon, May 17, 2021 at 12:48 PM Nick Buraglio <nick@buraglio.com> wrote:
>> >
>> > I have this working now between my providers with straight routing and
>> gateway checking, but it’s pretty easily doable other ways with platforms
>> like routerOS or pfsense.
>> > FWIW, I’m working with some others on an IETF draft proposal that will
>> hopefully solve the plaguing problem of multiple IPv6 PD or otherwise
>> provider assigned address blocks that will make a lot of that easier, too.
>>
>> Hmm? We solved this long ago in  cerowrt, openwrt, and in linux, by
>> using "source specific routing", which is the default for many openwrt
>> derived OSes.
>>
>> Basically it looks like this:
>>
>> ip route add from 2001:abcd::/56 via whatever
>> ip route add from 2001:dbcd::/56 via whatever2
>>
>> You then distribute both sets of ipv6 addresses to the clients. Simple
>> clean and it solved the bcp38 problem because there is no
>> default route for any but these ipv6 addresses in the system. It works
>> well for vpns also.
>>
>> Happy eyeballs takes care of the rest.
>>
>> https://datatracker.ietf.org/doc/html/draft-ietf-babel-source-specific-08
>> describes how we added it to the babel routing protocol
>> as well, so best hops can be easily chosen in a more complex network.
>> In case I had 5+ comcast uplinks spread across a wifi campus so having
>> multiple uplinks and failover was needed. It's been up and running
>> for... 7 years?
>>
>> https://en.wikipedia.org/wiki/Source-specific_routing also made it
>> into a few other places.
>>
>> I'm pretty certain every other OS completely missed this key feature
>> of course including your mikrotik
>>
>>
>>
>>
>> >
>> > nb
>> >
>> >
>> > On Mon, May 17, 2021 at 2:36 PM David Lang <david@lang.hm> wrote:
>> >>
>> >> On Mon, 17 May 2021, Nick Buraglio wrote:
>> >>
>> >> > Inline
>> >> >
>> >> > On Mon, May 17, 2021 at 2:15 PM Dave Taht <dave.taht@gmail.com>
>> wrote:
>> >> >>
>> >> >> 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.
>> >>
>> >> Fantastic, I was hoping it would be something like this. I think this
>> opens up a
>> >> lot of more useful options (including more easily doing failover
>> between the
>> >> dish and other network options)
>> >>
>> >> David  Lang
>>
>>
>>
>> --
>> 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: 6746 bytes --]

Re: [Starlink] dhcpv6-pd details

[Gert Doering]

Hi,

On Mon, May 17, 2021 at 09:21:53PM -0500, Nick Buraglio wrote:
> Once we get a bit for there I???ll send it over. It???s not my idea, I???m a
> contributor so I???ll need to ask first.

I'm interested as well.

The lack of usable dual-ipv6 multihoming with "standard CPEs" and
"standard hosts" today irks me a lot (especially since OpenWRT and
the homenet protocol suite had this all sorted out 7+ years ago)

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279

Re: [Starlink] dhcpv6-pd details

[Annika Wickert]

[-- Attachment #1: Type: text/plain, Size: 5124 bytes --]

I got dhcpv6-pd running some time ago with wide-dhcpv6 and the following settings:

profile default
{
  information-only;

  request domain-name-servers;
  request domain-name;

  script "/etc/wide-dhcpv6/dhcp6c-script";
};

interface eth0 {
        send ia-pd 0;
        send ia-na 0;
};

id-assoc na 0 {
};

id-assoc pd 0 {
        prefix-interface wlan0 {
                sla-len 8;
                sla-id 1;
        };
        prefix-interface eth0.222 {
                sla-len 8;
                sla-id 2;
        };

};


To request my IPv6 /64 on my WAN interface I run the following every two minutes, otherwise I lose the address:
/bin/rdisc6 -v eth0

With this v6 works very good and I have no issues at all.

But prefixes change every 24 hours or so

Best,
Annika

> On 17. May 2021, at 21:15, Dave Taht <dave.taht@gmail.com> wrote:
> 
> On Mon, May 17, 2021 at 12:04 PM Nick Buraglio <nick@buraglio.com <mailto: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 <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/ <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/ <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 <mailto:Starlink@lists.bufferbloat.net>
>> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>
> 
> 
> 
> -- 
> Latest Podcast:
> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/ <https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/>
> 
> Dave Täht CTO, TekLibre, LLC
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>

[-- Attachment #2: Type: text/html, Size: 46724 bytes --]

Re: [Starlink] dhcpv6-pd details

[Nick Buraglio]

[-- Attachment #1: Type: text/plain, Size: 5051 bytes --]

Interesting. My lease time is set to 5m(!!!) but it’s only changed once in
about 2 months. Where are you located?

nb

On Tue, May 18, 2021 at 3:33 AM Annika Wickert <aw@awlnx.space> wrote:

> I got dhcpv6-pd running some time ago with wide-dhcpv6 and the following
> settings:
>
> profile default
> {
>   information-only;
>
>   request domain-name-servers;
>   request domain-name;
>
>   script "/etc/wide-dhcpv6/dhcp6c-script";
> };
>
> interface eth0 {
>         send ia-pd 0;
>         send ia-na 0;
> };
>
> id-assoc na 0 {
> };
>
> id-assoc pd 0 {
>         prefix-interface wlan0 {
>                 sla-len 8;
>                 sla-id 1;
>         };
>         prefix-interface eth0.222 {
>                 sla-len 8;
>                 sla-id 2;
>         };
>
> };
>
>
> To request my IPv6 /64 on my WAN interface I run the following every two
> minutes, otherwise I lose the address:
> /bin/rdisc6 -v eth0
>
> With this v6 works very good and I have no issues at all.
>
> But prefixes change every 24 hours or so
>
> Best,
> Annika
>
>
> On 17. May 2021, at 21:15, 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
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>

[-- Attachment #2: Type: text/html, Size: 35861 bytes --]

Re: [Starlink] dhcpv6-pd details

[Annika Wickert]

[-- Attachment #1: Type: text/plain, Size: 6079 bytes --]

My lease time is also at 5min, I am in Germany close to Munich.

Maybe it stops changing when my pole mount finally arrives and I get a more stable connection.

> On 18. May 2021, at 13:37, Nick Buraglio <buraglio@forwardingplane.net> wrote:
> 
> Interesting. My lease time is set to 5m(!!!) but it’s only changed once in about 2 months. Where are you located? 
> 
> nb
> 
> On Tue, May 18, 2021 at 3:33 AM Annika Wickert <aw@awlnx.space <mailto:aw@awlnx.space>> wrote:
> I got dhcpv6-pd running some time ago with wide-dhcpv6 and the following settings:
> 
> profile default
> {
>   information-only;
> 
>   request domain-name-servers;
>   request domain-name;
> 
>   script "/etc/wide-dhcpv6/dhcp6c-script";
> };
> 
> interface eth0 {
>         send ia-pd 0;
>         send ia-na 0;
> };
> 
> id-assoc na 0 {
> };
> 
> id-assoc pd 0 {
>         prefix-interface wlan0 {
>                 sla-len 8;
>                 sla-id 1;
>         };
>         prefix-interface eth0.222 {
>                 sla-len 8;
>                 sla-id 2;
>         };
> 
> };
> 
> 
> To request my IPv6 /64 on my WAN interface I run the following every two minutes, otherwise I lose the address:
> /bin/rdisc6 -v eth0
> 
> With this v6 works very good and I have no issues at all.
> 
> But prefixes change every 24 hours or so
> 
> Best,
> Annika
> 
> 
>> On 17. May 2021, at 21:15, Dave Taht <dave.taht@gmail.com <mailto:dave.taht@gmail.com>> wrote:
>> 
>> On Mon, May 17, 2021 at 12:04 PM Nick Buraglio <nick@buraglio.com <mailto: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 <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/ <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/ <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 <mailto:Starlink@lists.bufferbloat.net>
>>> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>
>> 
>> 
>> 
>> -- 
>> Latest Podcast:
>> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/ <https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/>
>> 
>> Dave Täht CTO, TekLibre, LLC
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
>> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>


[-- Attachment #2: Type: text/html, Size: 38845 bytes --]

Re: [Starlink] dhcpv6-pd details

[Nick Buraglio]

[-- Attachment #1: Type: text/plain, Size: 5827 bytes --]

I suspect it is due to roaming between ground stations, but I am totally
guessing.

nb

ᐧ

On Tue, May 18, 2021 at 6:41 AM Annika Wickert <aw@awlnx.space> wrote:

> My lease time is also at 5min, I am in Germany close to Munich.
>
> Maybe it stops changing when my pole mount finally arrives and I get a
> more stable connection.
>
> On 18. May 2021, at 13:37, Nick Buraglio <buraglio@forwardingplane.net>
> wrote:
>
> Interesting. My lease time is set to 5m(!!!) but it’s only changed once in
> about 2 months. Where are you located?
>
> nb
>
> On Tue, May 18, 2021 at 3:33 AM Annika Wickert <aw@awlnx.space> wrote:
>
>> I got dhcpv6-pd running some time ago with wide-dhcpv6 and the following
>> settings:
>>
>> profile default
>> {
>>   information-only;
>>
>>   request domain-name-servers;
>>   request domain-name;
>>
>>   script "/etc/wide-dhcpv6/dhcp6c-script";
>> };
>>
>> interface eth0 {
>>         send ia-pd 0;
>>         send ia-na 0;
>> };
>>
>> id-assoc na 0 {
>> };
>>
>> id-assoc pd 0 {
>>         prefix-interface wlan0 {
>>                 sla-len 8;
>>                 sla-id 1;
>>         };
>>         prefix-interface eth0.222 {
>>                 sla-len 8;
>>                 sla-id 2;
>>         };
>>
>> };
>>
>>
>> To request my IPv6 /64 on my WAN interface I run the following every two
>> minutes, otherwise I lose the address:
>> /bin/rdisc6 -v eth0
>>
>> With this v6 works very good and I have no issues at all.
>>
>> But prefixes change every 24 hours or so
>>
>> Best,
>> Annika
>>
>>
>> On 17. May 2021, at 21:15, 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
>>
>>
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
>>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>

[-- Attachment #2: Type: text/html, Size: 36973 bytes --]

Re: [Starlink] dhcpv6-pd details

[Annika Wickert]

[-- Attachment #1: Type: text/plain, Size: 6909 bytes --]

That could be the reason, yes. Some times I get France as Groundstation.


> On 18. May 2021, at 16:48, Nick Buraglio <buraglio@forwardingplane.net> wrote:
> 
> I suspect it is due to roaming between ground stations, but I am totally guessing. 
> 
> nb
> 
> ᐧ
> 
> On Tue, May 18, 2021 at 6:41 AM Annika Wickert <aw@awlnx.space <mailto:aw@awlnx.space>> wrote:
> My lease time is also at 5min, I am in Germany close to Munich.
> 
> Maybe it stops changing when my pole mount finally arrives and I get a more stable connection.
> 
>> On 18. May 2021, at 13:37, Nick Buraglio <buraglio@forwardingplane.net <mailto:buraglio@forwardingplane.net>> wrote:
>> 
>> Interesting. My lease time is set to 5m(!!!) but it’s only changed once in about 2 months. Where are you located? 
>> 
>> nb
>> 
>> On Tue, May 18, 2021 at 3:33 AM Annika Wickert <aw@awlnx.space <mailto:aw@awlnx.space>> wrote:
>> I got dhcpv6-pd running some time ago with wide-dhcpv6 and the following settings:
>> 
>> profile default
>> {
>>   information-only;
>> 
>>   request domain-name-servers;
>>   request domain-name;
>> 
>>   script "/etc/wide-dhcpv6/dhcp6c-script";
>> };
>> 
>> interface eth0 {
>>         send ia-pd 0;
>>         send ia-na 0;
>> };
>> 
>> id-assoc na 0 {
>> };
>> 
>> id-assoc pd 0 {
>>         prefix-interface wlan0 {
>>                 sla-len 8;
>>                 sla-id 1;
>>         };
>>         prefix-interface eth0.222 {
>>                 sla-len 8;
>>                 sla-id 2;
>>         };
>> 
>> };
>> 
>> 
>> To request my IPv6 /64 on my WAN interface I run the following every two minutes, otherwise I lose the address:
>> /bin/rdisc6 -v eth0
>> 
>> With this v6 works very good and I have no issues at all.
>> 
>> But prefixes change every 24 hours or so
>> 
>> Best,
>> Annika
>> 
>> 
>>> On 17. May 2021, at 21:15, Dave Taht <dave.taht@gmail.com <mailto:dave.taht@gmail.com>> wrote:
>>> 
>>> On Mon, May 17, 2021 at 12:04 PM Nick Buraglio <nick@buraglio.com <mailto: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 <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/ <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/ <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 <mailto:Starlink@lists.bufferbloat.net>
>>>> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>
>>> 
>>> 
>>> 
>>> -- 
>>> Latest Podcast:
>>> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/ <https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/>
>>> 
>>> Dave Täht CTO, TekLibre, LLC
>>> _______________________________________________
>>> Starlink mailing list
>>> Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
>>> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
>> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>
> 
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>


[-- Attachment #2: Type: text/html, Size: 40186 bytes --]

Re: [Starlink] dhcpv6-pd details

[Darrell Budic]

[-- Attachment #1: Type: text/plain, Size: 7765 bytes --]

Just wanted to comment that NetworkManager (testing on Centos 8 Stream) beyond 1.20 or 1.22 works for -pd as well, once you tell it to use dhclient for dhcp anyway. method=shared after that and it’s good to go.

I’m using 'rdisc6 <starlink interface>' every 150 seconds to keep starlink sending RAs and keep my main v6 address alive as well, so far it hasn’t changed at all in ~48 hours.

> On May 18, 2021, at 9:50 AM, Annika Wickert <aw@awlnx.space> wrote:
> 
> That could be the reason, yes. Some times I get France as Groundstation.
> 
> 
>> On 18. May 2021, at 16:48, Nick Buraglio <buraglio@forwardingplane.net <mailto:buraglio@forwardingplane.net>> wrote:
>> 
>> I suspect it is due to roaming between ground stations, but I am totally guessing. 
>> 
>> nb
>> 
>> ᐧ
>> 
>> On Tue, May 18, 2021 at 6:41 AM Annika Wickert <aw@awlnx.space <mailto:aw@awlnx.space>> wrote:
>> My lease time is also at 5min, I am in Germany close to Munich.
>> 
>> Maybe it stops changing when my pole mount finally arrives and I get a more stable connection.
>> 
>>> On 18. May 2021, at 13:37, Nick Buraglio <buraglio@forwardingplane.net <mailto:buraglio@forwardingplane.net>> wrote:
>>> 
>>> Interesting. My lease time is set to 5m(!!!) but it’s only changed once in about 2 months. Where are you located? 
>>> 
>>> nb
>>> 
>>> On Tue, May 18, 2021 at 3:33 AM Annika Wickert <aw@awlnx.space <mailto:aw@awlnx.space>> wrote:
>>> I got dhcpv6-pd running some time ago with wide-dhcpv6 and the following settings:
>>> 
>>> profile default
>>> {
>>>   information-only;
>>> 
>>>   request domain-name-servers;
>>>   request domain-name;
>>> 
>>>   script "/etc/wide-dhcpv6/dhcp6c-script";
>>> };
>>> 
>>> interface eth0 {
>>>         send ia-pd 0;
>>>         send ia-na 0;
>>> };
>>> 
>>> id-assoc na 0 {
>>> };
>>> 
>>> id-assoc pd 0 {
>>>         prefix-interface wlan0 {
>>>                 sla-len 8;
>>>                 sla-id 1;
>>>         };
>>>         prefix-interface eth0.222 {
>>>                 sla-len 8;
>>>                 sla-id 2;
>>>         };
>>> 
>>> };
>>> 
>>> 
>>> To request my IPv6 /64 on my WAN interface I run the following every two minutes, otherwise I lose the address:
>>> /bin/rdisc6 -v eth0
>>> 
>>> With this v6 works very good and I have no issues at all.
>>> 
>>> But prefixes change every 24 hours or so
>>> 
>>> Best,
>>> Annika
>>> 
>>> 
>>>> On 17. May 2021, at 21:15, Dave Taht <dave.taht@gmail.com <mailto:dave.taht@gmail.com>> wrote:
>>>> 
>>>> On Mon, May 17, 2021 at 12:04 PM Nick Buraglio <nick@buraglio.com <mailto: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 <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/ <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/ <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 <mailto:Starlink@lists.bufferbloat.net>
>>>>> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> Latest Podcast:
>>>> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/ <https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/>
>>>> 
>>>> Dave Täht CTO, TekLibre, LLC
>>>> _______________________________________________
>>>> Starlink mailing list
>>>> Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
>>>> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>
>>> _______________________________________________
>>> Starlink mailing list
>>> Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
>>> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>
>> 
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
>> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>
> 
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink


[-- Attachment #2: Type: text/html, Size: 41379 bytes --]