Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave@taht.net>
Cc: Dave Taht <dave.taht@gmail.com>, Ted Lemon <mellon@fugue.com>,
	 cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] meanwhile... .home, finally has a home.arpa.
Date: Wed, 24 Oct 2018 10:22:54 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1810241018190.26856@uplift.swm.pp.se> (raw)
In-Reply-To: <87ftwwy74v.fsf@taht.net>

On Tue, 23 Oct 2018, Dave Taht wrote:

> I just ping6 my upstream dns server, roughly the same algorithm. But
> if it goes down, you don't want to take away the local ipv6 addresses,
> just the default route, and when you do that, you end up falling back to
> ipv4.

I want to lower the preferred lifetime for the PD PIO from that connection 
to 0 when upstream lifecheck fails (ie, send RA with 0 preferred 
lifetime). So correct, don't take away the addresses, just make sure 
they're not chosen anymore for outgoing connections.

> You probably live in a place with reliable power. I get a power flicker 
> at least once a week. the corest routers are on battery backup but that 
> only lasts a few hours and the last big outage was about 9 hours about 6 
> weeks ago. When everything reboots, chaos reigns. When only some things 
> reboot, different kinds of chaos reign.

Right. The frequent re-addressing of interfaces (every time it goes up and 
down actually) is one thing I pointed out years ago is a weak spot in the 
homenet implementation.

> Secondly a usable set of /56s would be "enough" in my case (about 40 
> boxes), /60 doesn't divide into that.

Agreed, /56 is what's needed.

> thirdly, I don't want to assign routable ipv6 prefixes to everything, 
> just to end-user APs and when I last tried hnpd it wanted to give even 
> my p2p boxes /64s

Yes, it allocates /64 per interface. You can share interface with multiple 
things by creating bridge interfaces.

> fourthly, we have dnsmasq, odhcpd, odhcpc, babel and hnetd all battling 
> it out with slightly different notions of how to redistribute things.

Right, a device that speaks homenet should not request PD.

> I've come to rather appreciate NAT for what it does to separate my 
> policies from my ISP's.

Configuring static ULA addresses might be a way to handle it. Doesn't help 
reaching them from the outside though. We need DNS or other mechanism to 
keep track of addresses as they change over time.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

  reply	other threads:[~2018-10-24  8:22 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
2018-10-23 16:12       ` Dave Taht
2018-10-24  8:22         ` Mikael Abrahamsson [this message]
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.1810241018190.26856@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=dave@taht.net \
    --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