From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
"babel-users@lists.alioth.debian.org"
<babel-users@lists.alioth.debian.org>
Subject: [Cerowrt-devel] ipv6 confusion with source specific gateways.
Date: Tue, 25 Nov 2014 23:11:17 -0800 [thread overview]
Message-ID: <CAA93jw68EUNHyJRrKYZuc0egXZaC_9oUysqZEN-YkNfNhc6ERA@mail.gmail.com> (raw)
Some days I just lose it with prefix math. Or maybe we have a 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.
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?
(see the 01?)?
OK, so, like, I have another babel source specifc gateway a few hops
in from there, I add
ip -6 addr add 2601:c:ce00:9d01::1/64 dev wlan0-1
that doesnt work. I make it be
ip -6 addr add 2601:c:ce00:9d6::1/64 dev wlan0-1
and that does.
--
Dave Täht
http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
next reply other threads:[~2014-11-26 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 7:11 Dave Taht [this message]
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 ` [Cerowrt-devel] " Chuck Anderson
2014-11-27 8:32 ` 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=CAA93jw68EUNHyJRrKYZuc0egXZaC_9oUysqZEN-YkNfNhc6ERA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=babel-users@lists.alioth.debian.org \
--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