From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Cc: "babel-users@lists.alioth.debian.org"
<babel-users@lists.alioth.debian.org>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Babel-users] ipv6 confusion with source specific gateways.
Date: Mon, 1 Dec 2014 18:38:40 -0800 [thread overview]
Message-ID: <CAA93jw4wObPZD_rvXEcxTUEZZUVR6subk6CoXgpcQZ1TdToZdQ@mail.gmail.com> (raw)
In-Reply-To: <878uiq23vs.wl-jch@pps.univ-paris-diderot.fr>
On Mon, Dec 1, 2014 at 6:15 PM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
>>> 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
>
> You mean ::/0.
>
>> It is needed for IPv6 packets that originate on the host but where the
>> application doesn't specify an address to bind to.
>
> Yes, it is also needed to ensure interoperability between Babel-S and
> stock Babel. (I really wish OpenWRT installed a non-specific route in
> that case, by the way.)
?
An issue I have had with owrt is that it used route to enter routes, which
does not support various tables (like dhcp, or babel-pinger).
I think, but am not sure, that netifd in chaos calmer actually calls
the routing commands directly now, so that
behavior could be more correct. I don't know what udhcp uses...
The unreachable syntax was also recently added to netifd, so exporting
covering routes has just got easier.
see: https://github.com/sbyx/hnetd/issues/23
for details.
>
> -- Juliusz
--
Dave Täht
thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
next prev parent reply other threads:[~2014-12-02 2:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 7:11 [Cerowrt-devel] " 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 [this message]
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=CAA93jw4wObPZD_rvXEcxTUEZZUVR6subk6CoXgpcQZ1TdToZdQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=babel-users@lists.alioth.debian.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=jch@pps.univ-paris-diderot.fr \
/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