Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Chuck Anderson <cra@WPI.EDU>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] ipv6 confusion with source specific gateways.
Date: Wed, 26 Nov 2014 22:21:14 -0500	[thread overview]
Message-ID: <20141127032113.GP16805@angus.ind.WPI.EDU> (raw)
In-Reply-To: <CAA93jw68EUNHyJRrKYZuc0egXZaC_9oUysqZEN-YkNfNhc6ERA@mail.gmail.com>

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  metric 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 326362sec
> 
> 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


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...

  parent reply	other threads:[~2014-11-27  3:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26  7:11 Dave Taht
2014-11-26  7:40 ` Toke Høiland-Jørgensen
2014-11-26 22:03   ` Robert Bradley
2014-12-02  2:15   ` [Cerowrt-devel] [Babel-users] " Juliusz Chroboczek
2014-12-02  2:38     ` Dave Taht
2014-12-02  5:53     ` Toke Høiland-Jørgensen
2014-11-27  3:21 ` Chuck Anderson [this message]
2014-11-27  8:32   ` [Cerowrt-devel] " 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=20141127032113.GP16805@angus.ind.WPI.EDU \
    --to=cra@wpi.edu \
    --cc=cerowrt-devel@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