From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: Ted Lemon <mellon@fugue.com>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] meanwhile... .home, finally has a home.arpa.
Date: Tue, 23 Oct 2018 17:47:03 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1810231744390.26856@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw6omcj3Z0c97=OuC=P0VpWW-h_i_sFh_c=YyU0L4z8Nag@mail.gmail.com>
On Tue, 23 Oct 2018, Dave Taht wrote:
> Mikael is the sole survivor here, so far as I know.
I ended up disabling the homenet stuff because lifetimes didn't align with
my preference in provider (my non-preferred provider has longer
lease-times than my preferred provider, so in the whole source-selection
mechanism my non-preferred provider won). Also, there is no good way to
detect L2 failures towards providers.
https://tools.ietf.org/html/draft-patterson-intarea-ipoe-health-05 solves.
> As examples that persist, dhcpv6-pd renewals seem to be broken in
> openwrt still, so I get a bunch of prefixes... and a few a days later
> they vanish. I get static routes to nowhere, often, out of that. And:
> with only a /60 available, I also run out of prefixes to allocate if
> something reboots at the wrong time at the wrong place, and so on.
I do not have this problem. I get /56 PD from provider and it hasn't
changed yet.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2018-10-23 15:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 3:51 Dave Taht
2018-10-23 4:13 ` Ted Lemon
2018-10-23 15:09 ` Dave Taht
2018-10-23 15:42 ` Ted Lemon
2018-10-23 16:15 ` Dave Taht
2018-10-23 16:44 ` Ted Lemon
2018-10-23 15:47 ` Mikael Abrahamsson [this message]
2018-10-23 16:12 ` Dave Taht
2018-10-24 8:22 ` Mikael Abrahamsson
2018-10-24 16:39 ` Dave Taht
2018-10-24 18:04 ` Mikael Abrahamsson
2018-10-23 23:28 ` Michael Richardson
2018-10-23 23:38 ` Dave Taht
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1810231744390.26856@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=mellon@fugue.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