From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Fernando Gont <fernando@gont.com.ar>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Question on Netlink IPv6 routing table lookup
Date: Fri, 27 Sep 2013 02:16:13 +0200 [thread overview]
Message-ID: <20130927001613.GA28287@order.stressinduktion.org> (raw)
In-Reply-To: <52440E48.3030102@gont.com.ar>
On Thu, Sep 26, 2013 at 07:36:56AM -0300, Fernando Gont wrote:
> 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>)
Correct.
> 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.
As soon as you add a route with RTA_SRC you will see those two fields != 0.
Subtrees don't get used by router advertisments. Only way to set these fields
is by using the RTA_SRC from user-land.
Greetings,
Hannes
prev parent reply other threads:[~2013-09-27 0:16 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
2013-09-27 0:16 ` Hannes Frederic Sowa [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=20130927001613.GA28287@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=fernando@gont.com.ar \
--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