From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ia0-x22b.google.com (mail-ia0-x22b.google.com [IPv6:2607:f8b0:4001:c02::22b]) (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 AB36821F104 for ; Sun, 5 May 2013 14:38:44 -0700 (PDT) Received: by mail-ia0-f171.google.com with SMTP id r13so2719297iar.2 for ; Sun, 05 May 2013 14:38:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=rXwcCBBJy8AKnAeyQHywheeDf6+hr1plqJLgqgUmYew=; b=r0K0AX1K8X7LBy89iFaGcPOoV/9w/zekbfIuS5ERAcwIgVDNRs4CWus3yhqn06QESk kkYS+zVRQaAhsCQCK2p7NrG/ngoB1MpapJAG5lQtHC7IaP+Udxc0bVJDjKR+NGhj+pqX jQgwNUrK/9Ske0Q4vCsKhZlq6zj0KUe3DwcQF6qVNjXJyCmC50saGMCdsc5c5FC29spS VECCQPpkfU3XDW5UaL8e+9TXYct8Q6Ptpd7IrR+xrTf/NhtyPO9ql5INa2jIEJ3mmTVD y/YEfB0Ujk/XbK2sW5a4RDXjoV6058UQh1eDvEkqlJtJrnwWHHe/SCiQWFV74nsA9t8l N1dQ== MIME-Version: 1.0 X-Received: by 10.43.7.1 with SMTP id om1mr1287722icb.49.1367789923987; Sun, 05 May 2013 14:38:43 -0700 (PDT) Received: by 10.64.7.51 with HTTP; Sun, 5 May 2013 14:38:43 -0700 (PDT) Date: Sun, 5 May 2013 14:38:43 -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 21:38:44 -0000 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, 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 --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html