From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 4831321F232 for ; Thu, 27 Nov 2014 00:32:41 -0800 (PST) Received: by mail-ob0-f173.google.com with SMTP id uy5so3446548obc.18 for ; Thu, 27 Nov 2014 00:32:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=xYtf42ymMTSWdnn7FO8e0Cwo2SYLYxx2AfJ7J4doIro=; b=BdHJIva2CBEHR5Dh/mjf5wQpbywVhWbogyeBGeEXYe/Wc90zUP8jEkiNdlYYGxhfFe rZUAA+PkKkqfZUDE3iBtPG8OMFISZFTcr3M+Ov5SlC78uk3HvSqHP5ZKkaSdaz3ejdaa XJLq0JmpwFMyoSPVlATWThVAVSgmgxnkKxaXlQYv73Woa3KqbqDxQsHpxDGig3BBwV+2 BAZNqmXgKpws//a8Uy3yTAD22IudmVa7AC+Nj7phqUMQEI+Fprd3CHPTJHPUbpvEmWkB Yqx72UCLcu+6Y0abTL4RpT/E/vRkx1QF4YT7U/rCoVVQuPqfPVqt9JqKRqC1cMQq9eUo GlOA== MIME-Version: 1.0 X-Received: by 10.60.55.200 with SMTP id u8mr22809123oep.43.1417077160525; Thu, 27 Nov 2014 00:32:40 -0800 (PST) Received: by 10.202.227.211 with HTTP; Thu, 27 Nov 2014 00:32:40 -0800 (PST) In-Reply-To: <20141127032113.GP16805@angus.ind.WPI.EDU> References: <20141127032113.GP16805@angus.ind.WPI.EDU> Date: Thu, 27 Nov 2014 00:32:40 -0800 Message-ID: From: Dave Taht To: "cerowrt-devel@lists.bufferbloat.net" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Cerowrt-devel] ipv6 confusion with source specific gateways. X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 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: Thu, 27 Nov 2014 08:33:10 -0000 On Wed, Nov 26, 2014 at 7:21 PM, Chuck Anderson wrote: > On Tue, Nov 25, 2014 at 11:11:17PM -0800, Dave Taht wrote: >> Some days I just lose it with prefix math. Or maybe we have a bug. > > Prefix math, there is no bug. > >> So here is a default gateway. So far as I know it is getting a /56 >> actually, not a /60, but it is requesting a /60 and thus distributing >> a source specific route to that /60. > > Looks like a /60. > >> default from :: via fe80::201:5cff:ee62:b646 dev ge00 proto static met= ric 1024 >> # should I even have a default route at all? >> default from 2001:558:6045:e9:44a9:4a25:ece9:55c3 via >> fe80::201:5cff:ee62:b646 dev ge00 proto static metric 1024 >> # my uplink, looks sane >> >> default from 2601:c:ce00:9d0::/60 via fe80::201:5cff:ee62:b646 dev >> ge00 proto static metric 1024 >> # and see that /60... >> >> # and then there is the default ipv6 address assignements on cero. >> >> 2601:c:ce00:9d1::/64 dev gw10 proto kernel metric 256 expires 326362s= ec >> >> Now, where my brain crashes: shouldn't 2601:c:ce00:9d1::/64 actually >> be something like >> >> 2601:c:ce00:9d01::/64 not, 2601:c:ce00:9d1::/64? > > No, it is correct. The /60 is: > > 2601:c:ce00:9d0::/60 > > which is really this when expanded out (zero-pad each : section): > > 2601:000c:ce00:09d0::/60 You are absolutely correct. Thank you! > > > Now the 60 bit prefix is: > > 2601:000c:ce00:09dX:XXXX:XXXX:XXXX:XXXX > > where X is the part which can be assigned to your LANs. The first X > is a 4-bit nibble that was assigned "1" by Cero creating a /64 subnet > prefix, leaving the remaining 64 bits for your Interface IDs... It turned out that I had a non-source-specific babeld between me and it, also (bloody meshy routing!), which was messing things up. Worse, that is on a roof where I cant update it easily. Also I AM getting a /56 from a comcast business class account elsewhere on the net... but grokking hnetd is killing me. > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel --=20 Dave T=C3=A4ht thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks