From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Cc: HOMENET <homenet@ietf.org>,
bloat-devel <bloat-devel@lists.bufferbloat.net>,
babel-users@lists.alioth.debian.org,
Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Subject: Re: Source-specific routes in Linux [was: atomic updates...]
Date: Sun, 5 May 2013 15:23:37 -0700 [thread overview]
Message-ID: <CAA93jw636HK8e2kzGaVqXqGuJKNdcGR+HzyENFDD9rxtLbK8vQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4DieHEM74AjE4W04OMBCtZUS6BQ5_ri+m76ZR0Qu7fiA@mail.gmail.com>
On Sun, May 5, 2013 at 2:38 PM, Dave Taht <dave.taht@gmail.com> wrote:
> On Sun, May 5, 2013 at 1:05 PM, Juliusz Chroboczek
> <jch@pps.univ-paris-diderot.fr> wrote:
>>> It's not ECMP for ipv6 I'm looking to see solved for multiple routing
>>> protocols, but the multiple ipv6 prefixes/multiple exits source
>>> routing problem.
>>
>> As you well know, Dave, we've been working on that for the last
>> fortnight or so.
>>
>> We've run into a limitation of the kernel:
>>
>> http://www.spinics.net/lists/netdev/msg235316.html
>
> Hmm. Given that this code path has only barely been exercised before
> and so many changes to the routing paths have happened in the last 2+
> years, I'm not surprised its broken.
>
>>
>> Unfortunately, I've had no reply to my question:
>>
>> http://www.spinics.net/lists/netdev/msg235346.html
>>
>> So it looks like we're going to have to dynamically generate rule
>> table entries... sigh.
>
> Well, given the work going into mptcp in particular,
This was a very good overview of where that work stands.
http://lwn.net/Articles/544399/
> a better API for
> src specific routing for ipv6 than the ip rule system seems like a
> good idea.
>
> Widening the distribution a little bit...
>
>>> The homenet folk demonstrated this form of ipv6 multihoming working
>>> (using a version of OSPF and BIRD, I believe) at the last ietf.
>>
>> That is interesting. Would you happen to know how they're interfacing
>> with the kernel? Or perhaps have a link to their code?
>
> I don't know where the ietf 86 bird work on multihoming went. (?)
> Patterson's original work on ospf is here:
>
> https://github.com/paterben/bird-homenet
>
> and the ietf drafts are here
>
> http://tools.ietf.org/wg/homenet/
>
>>
>> -- Juliusz
>
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2013-05-05 22:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-05 21:38 Dave Taht
2013-05-05 22:23 ` Dave Taht [this message]
[not found] ` <loom.20130507T130051-512@post.gmane.org>
[not found] ` <87vc6vgghx.wl%jch@pps.univ-paris-diderot.fr>
[not found] ` <8F7177E4-6212-4A74-8A7C-A2D1703A59BF@iki.fi>
[not found] ` <87sj1zgfot.wl%jch@pps.univ-paris-diderot.fr>
2013-05-08 8:51 ` [homenet] " Dave Taht
2013-05-08 9:48 ` Steven Barth
2013-05-08 10:28 ` Ole Troan
2013-05-08 10:51 ` Steven Barth
2013-05-08 10:58 ` Ole Troan
2013-05-08 12:54 ` Steven Barth
2013-05-08 11:06 ` Lorenzo Colitti
2013-05-08 22:46 ` Juliusz Chroboczek
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw636HK8e2kzGaVqXqGuJKNdcGR+HzyENFDD9rxtLbK8vQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=babel-users@lists.alioth.debian.org \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=homenet@ietf.org \
--cc=jch@pps.univ-paris-diderot.fr \
--cc=nishida@sfc.wide.ad.jp \
/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