netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@pps.jussieu.fr>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: RTA_SRC doesn't work?
Date: Thu, 02 May 2013 23:18:03 +0200	[thread overview]
Message-ID: <7imwsd6pys.wl%jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <20130502.171013.1977432139945346146.davem@davemloft.net>

> But you can only do source based routing using FIB rules, the
> normal routing tables (which are hung off of the rules) do not
> have source keys in them.  They are keyed only by destination
> address.
> 
> Only the FIB rules support source address keying.
> 
> So you will need to use multiple routing table to route by source
> address.

Ok, that explains the IPv4 behaviour.  But what about v6?  The
following bit of ipv6/Kconfig would seem to imply that I can avoid
generating rules dynamically as new source prefixes appear:

  config IPV6_SUBTREES
          bool "IPv6: source address based routing"
          depends on IPV6_MULTIPLE_TABLES
          ---help---
            Enable routing by source address or prefix.

            The destination address is still the primary routing key, so mixing
            normal and source prefix specific routes in the same routing table
            may sometimes lead to unintended routing behavior.  This can be
            avoided by defining different routing tables for the normal and
            source prefix specific routes.

Thanks again,

-- Juliusz

      reply	other threads:[~2013-05-02 21:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-02 18:31 RTA_SRC doesn't work? Juliusz Chroboczek
2013-05-02 19:21 ` David Miller
2013-05-02 19:58   ` Juliusz Chroboczek
2013-05-02 20:21     ` David Miller
2013-05-02 20:42       ` Juliusz Chroboczek
2013-05-02 20:54         ` David Miller
2013-05-02 21:04           ` Juliusz Chroboczek
2013-05-02 21:05           ` Juliusz Chroboczek
2013-05-02 21:10           ` David Miller
2013-05-02 21:18             ` Juliusz Chroboczek [this message]

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=7imwsd6pys.wl%jch@pps.univ-paris-diderot.fr \
    --to=jch@pps.jussieu.fr \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).