Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Cc: homenet@ietf.org, Markus Stenberg <markus.stenberg@iki.fi>,
	bloat-devel <bloat-devel@lists.bufferbloat.net>,
	boutier@pps.univ-paris-diderot.fr
Subject: Re: [homenet] Source-specific routes in Linux [was: atomic updates...]
Date: Wed, 8 May 2013 01:51:00 -0700	[thread overview]
Message-ID: <CAA93jw6KPxb-wsTLNsLMixGtVmwFkzmi8SvU2EwnhajCL_rC2g@mail.gmail.com> (raw)
In-Reply-To: <87sj1zgfot.wl%jch@pps.univ-paris-diderot.fr>

[-- Attachment #1: Type: text/plain, Size: 2072 bytes --]

On Tue, May 7, 2013 at 5:03 AM, Juliusz Chroboczek <
jch@pps.univ-paris-diderot.fr> wrote:

> > > If you're actually doing source-specific routing, please show me how
> > > you speak to the kernel.
>
> > Most of that code is in Lua, and while I could have included
> > C extension module that did similar things as ip -6 does, I didn't
> > bother.
>
> We're doing pretty the same in our prototype code (saying
> system("ip...") rather than speaking the netlink dialect of the day).
> Could you point us at the relevant code, please?
>
> > So I'm just using ip -6 {route,rule} to set up source-specific rules
> > that map to destination tables.
>
> Ah, okay.  So you're using rules, just as we found out (the hard way)
> that we need to do.
>
>   http://www.spinics.net/lists/netdev/msg235316.html
>   http://www.spinics.net/lists/netdev/msg235346.html
>

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.



>
> > One (destination-based) routing table is maintained by routing
> > protocol, and the rest by Lua code which figures external defaults
> > based on routes within routing protocol implementation.
>
> Nice hack.
>

Except that probably it interacts badly with existing vpn manipulation of
these tables.


>
> -- Juliusz
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>



-- 
Dave Täht

Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html

[-- Attachment #2: Type: text/html, Size: 3271 bytes --]

  parent reply	other threads:[~2013-05-08  8:51 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           ` Dave Taht [this message]
2013-05-08  9:48             ` [homenet] " 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=CAA93jw6KPxb-wsTLNsLMixGtVmwFkzmi8SvU2EwnhajCL_rC2g@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=boutier@pps.univ-paris-diderot.fr \
    --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