From: Annika Wickert <aw@awlnx.space>
Cc: Starlink@lists.bufferbloat.net
Subject: Re: [Starlink] dhcpv6-pd details
Date: Tue, 18 May 2021 16:50:23 +0200 [thread overview]
Message-ID: <B8125CEE-F7A0-4E00-BB18-FE60E2EB4DF4@awlnx.space> (raw)
In-Reply-To: <CAGB08_fUz7CqtJADhSDtRYOKZRBDwBiLTn+AKSa2wuBEk27f5A@mail.gmail.com>
[-- 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 --]
next prev parent reply other threads:[~2021-05-18 14:50 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
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 [this message]
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=B8125CEE-F7A0-4E00-BB18-FE60E2EB4DF4@awlnx.space \
--to=aw@awlnx.space \
--cc=Starlink@lists.bufferbloat.net \
/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