From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.employees.org", Issuer "Equifax" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id F1F7521F1C5 for ; Wed, 8 May 2013 03:28:17 -0700 (PDT) Received: from dhcp-lys02-vla252-10-147-116-38.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 0E1C85EF6; Wed, 8 May 2013 03:28:15 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: [homenet] Source-specific routes in Linux [was: atomic updates...] From: Ole Troan In-Reply-To: <518A1F51.809@openwrt.org> Date: Wed, 8 May 2013 12:28:14 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <87vc6vgghx.wl%jch@pps.univ-paris-diderot.fr> <8F7177E4-6212-4A74-8A7C-A2D1703A59BF@iki.fi> <87sj1zgfot.wl%jch@pps.univ-paris-diderot.fr> <518A1F51.809@openwrt.org> To: Steven Barth X-Mailer: Apple Mail (2.1503) X-Mailman-Approved-At: Thu, 09 May 2013 02:16:43 -0700 Cc: bloat-devel , Juliusz Chroboczek , Markus Stenberg , boutier@pps.univ-paris-diderot.fr, homenet@ietf.org 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: Wed, 08 May 2013 10:28:18 -0000 [...] > We have switched to RA-Handling in userspace for similar reasons = already so I guess it's only the next logical step to create separate = routing tables for each upstream interface to do source-based routing = and filter out ULA-traffic on this layer instead of through iptables. don't do it per upstream interface, that wouldn't work. per next-hop = might. the draft suggests a single table with source constrained routers = and backtracking. > Having one central userspace management daemon for routing and address = / prefix delegation in general might not be the best or cleanest = solution in the end but I guess there is no better way right now. cheers, Ole _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet