From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
"babel-users@lists.alioth.debian.org"
<babel-users@lists.alioth.debian.org>
Subject: Re: [Cerowrt-devel] ipv6 confusion with source specific gateways.
Date: Wed, 26 Nov 2014 08:40:14 +0100 [thread overview]
Message-ID: <E4B2D8FC-D37B-427F-BC18-2FB79C31AA33@toke.dk> (raw)
In-Reply-To: <CAA93jw68EUNHyJRrKYZuc0egXZaC_9oUysqZEN-YkNfNhc6ERA@mail.gmail.com>
>default from :: via fe80::201:5cff:ee62:b646 dev ge00 proto static
>metric 1024
># should I even have a default route at all?
The source on this is actually ::/128 so it's not a default route in the sense that it will forward arbitrary traffic through it. It is needed for IPv6 packets that originate on the host but where the application doesn't specify an address to bind to. To see that, try removing it and then ping6 something you don't have a specific route to...
>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?)?
2601:c:ce00:9d01 is 2601:000c:ce00:9d01
2601:c:ce00:9d1 is 2601:000c:ce00:09d1
So no? :)
-Toke
next prev parent reply other threads:[~2014-11-26 7:40 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 [this message]
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=E4B2D8FC-D37B-427F-BC18-2FB79C31AA33@toke.dk \
--to=toke@toke.dk \
--cc=babel-users@lists.alioth.debian.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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