From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 1C58F200666 for ; Sun, 5 May 2013 15:23:38 -0700 (PDT) Received: by mail-ie0-f172.google.com with SMTP id 16so3520716iea.31 for ; Sun, 05 May 2013 15:23:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=tzF5YJssXOoXb+iKUJVFnerRRZe6m9WLnV3DRxDFKZA=; b=q3ABGK5vPmNKf5Dmn/dKjPWe6BcjJwq6C6IWs6NbSDqkjt3H6OBJVCGGuBZlNss8mC SalAsCcPieC1F34IxEc4lw1kVrF5TgbwLGg3Bf/ue/7PwcSEMktkf9hjBaaSN8SpDIbP n88Tgieao0PwlWX9UTwmekeTO0q2Zac9StBfHQ6MyhrSAXM3L5dO6Z7GKyPIP4zeKxB8 5EUibEVY2Qz3EL11pcriQWC2QAqnzaGlyxPR1T/nAZ+xzTZ8wZpljtJZeEeWmRYlsNsp lbJVE9rIpibfWEGsupeTJw5sGw/3wD4CSWSYTWymy9F5EkDmWDkor+/Qw/aCTvEp3LyT S1cQ== MIME-Version: 1.0 X-Received: by 10.50.127.212 with SMTP id ni20mr1929243igb.27.1367792617516; Sun, 05 May 2013 15:23:37 -0700 (PDT) Received: by 10.64.7.51 with HTTP; Sun, 5 May 2013 15:23:37 -0700 (PDT) In-Reply-To: References: Date: Sun, 5 May 2013 15:23:37 -0700 Message-ID: Subject: Re: Source-specific routes in Linux [was: atomic updates...] From: Dave Taht To: Juliusz Chroboczek Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: HOMENET , bloat-devel , babel-users@lists.alioth.debian.org, Yoshifumi Nishida X-BeenThere: bloat-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Developers working on AQM, device drivers, and networking stacks" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 May 2013 22:23:38 -0000 On Sun, May 5, 2013 at 2:38 PM, Dave Taht wrote: > On Sun, May 5, 2013 at 1:05 PM, Juliusz Chroboczek > 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=E4ht > > Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscrib= e.html --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html