From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 13E7B3B2A4 for ; Wed, 24 Oct 2018 04:22:56 -0400 (EDT) Received: by uplift.swm.pp.se (Postfix, from userid 501) id 76D8AB4; Wed, 24 Oct 2018 10:22:54 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1540369374; bh=w3RBIIUweMsHFFpNj5SiZgbaLM+Jvd31ziRKNx4BTw0=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=DNIAtqcN1iE0ROI0yd9Gkys+4XahEaUkZWhY+3wyrY7hQja/fFpOe3A7ta9EW7yP7 a5YwRYdStL+S/ihqeaouCZwwvpqBghHgyJ7B0+5dcl4nUK6BFr6mfhzRVEFQv3tSSt patw7HNejrLoW4oqrvSxPLfydAakuFnVccIYK054= Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 7550BB0; Wed, 24 Oct 2018 10:22:54 +0200 (CEST) Date: Wed, 24 Oct 2018 10:22:54 +0200 (CEST) From: Mikael Abrahamsson To: Dave Taht cc: Dave Taht , Ted Lemon , cerowrt-devel@lists.bufferbloat.net In-Reply-To: <87ftwwy74v.fsf@taht.net> Message-ID: References: <10E89375-2591-49B2-9A67-AA0E14B17649@fugue.com> <87ftwwy74v.fsf@taht.net> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) Organization: People's Front Against WWW MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Re: [Cerowrt-devel] meanwhile... .home, finally has a home.arpa. X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2018 08:22:56 -0000 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