From: Steven Barth <cyrus@openwrt.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: homenet@ietf.org, Markus Stenberg <markus.stenberg@iki.fi>,
bloat-devel <bloat-devel@lists.bufferbloat.net>,
boutier@pps.univ-paris-diderot.fr,
Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Source-specific routes in Linux [was: atomic updates...]
Date: Wed, 08 May 2013 11:48:01 +0200 [thread overview]
Message-ID: <518A1F51.809@openwrt.org> (raw)
In-Reply-To: <CAA93jw6KPxb-wsTLNsLMixGtVmwFkzmi8SvU2EwnhajCL_rC2g@mail.gmail.com>
On 08.05.2013 10:51, Dave Taht wrote:
> One thing that bugs me about hacks and workarounds like this is that
> Linux (as well as openwrt) are intensely mutable systems, and it's
> totally possible to improve linux rather than limp around in userspace.
>
> I have long disliked the ip rule system in its primary use prior to now
> (vpns), as buggy, arbitrary, and subject to race conditions, so if a
> better api and methods for injecting/managing source address dependent
> routing information could be designed I'm pretty sure there would be
> much enthusiasm across the vpn, mptcp/sctp, and routing worlds for
> getting it into linux itself.
Hmm I must admit I'm wondering about this for the OpenWrt stack as well.
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.
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.
next prev parent reply other threads:[~2013-05-08 9:48 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
[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 [this message]
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=518A1F51.809@openwrt.org \
--to=cyrus@openwrt.org \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=boutier@pps.univ-paris-diderot.fr \
--cc=dave.taht@gmail.com \
--cc=homenet@ietf.org \
--cc=jch@pps.univ-paris-diderot.fr \
--cc=markus.stenberg@iki.fi \
/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