All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fernando Gont <fernando@gont.com.ar>
To: netdev <netdev@vger.kernel.org>
Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>
Subject: Re: Question on Netlink IPv6 routing table lookup
Date: Thu, 26 Sep 2013 07:36:56 -0300	[thread overview]
Message-ID: <52440E48.3030102@gont.com.ar> (raw)
In-Reply-To: <20130924000453.GB2593@order.stressinduktion.org>

Hi, Hannes,

On 09/23/2013 09:04 PM, Hannes Frederic Sowa wrote:
> On Mon, Sep 23, 2013 at 04:41:07PM -0300, Fernando Gont wrote:
>> If that's not (currently) possible, should I expect RTA_SRC to work as
>> described above at some point in the future?
> 
> The RTA_SRC attriute matches on sutrees in the ipv6 routing table:
> 
> ip -6 r a default via fe80::1 dev eth0 from 2000::/64
> ip -6 r a default via fe80::2 dev eth0 from 2000:1:/64
> 
> ip -6 r g :: from 2000::
> ip -6 r g :: from 2000:1::
> 
> ...should return different routes. The from parameter is the RTA_SRC
> attribute.

Isn't the "from" the "source network" in /proc/net/ipv6_route? (as
described in <http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/proc-net.html>)

I have a node with multiple Ethernet interfaces, each of which connected
to a different network where IPv6 Router Advertisements are received...
and the "source network" is set to all-zeros in all cases.

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1

  reply	other threads:[~2013-09-26 10:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-23 19:41 Question on Netlink IPv6 routing table lookup Fernando Gont
2013-09-24  0:04 ` Hannes Frederic Sowa
2013-09-26 10:36   ` Fernando Gont [this message]
2013-09-27  0:16     ` Hannes Frederic Sowa

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=52440E48.3030102@gont.com.ar \
    --to=fernando@gont.com.ar \
    --cc=hannes@stressinduktion.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.