public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed

From: Fernando Gont <fernando@gont•com.ar>
To: netdev <netdev@vger•kernel.org>
Subject: Question on Netlink IPv6 routing table lookup
Date: Mon, 23 Sep 2013 16:41:07 -0300	[thread overview]
Message-ID: <52409953.8040208@gont.com.ar> (raw)

Folks,

I'm performing IPv6 routing table lookups with a netlink socket, and it
seems that specifying the Source Address with the RTA_SRC element does
not have any effect on the result of the look-up.

In my network setup, I have two interfaces, as follows:

 NET1 (fc00:1::/64) <------> MY_NODE <------> NET2 (fc00:2::/64)

For simplicity sake, let's say that my nodes' address on NET1 is
fc00:1::1, and my node's address on NET2 is fc00:2::1. And my node has
two default routes (one in NET1, and another in NET2).

I'd expect that if I set RTA_SRC to fc00:1::1, the default route on NET1
is selected, but if I set RTA_SRC to fc00:2::1, it is the default route
on NET2 that is selected.

However, the result of the routing tale look-up is always the same,
regardless of RTA_SRC.

I looked at /proc/net/ipv6_route, and it seems that, for all routes, the
"source network" is always set to :: (all zeroes), thus probably
explaining the above behavior.

Is there any way to influence the routing-table look-up based on the
IPv6 source address?

If that's not (currently) possible, should I expect RTA_SRC to work as
described above at some point in the future?
-- 
Fernando Gont
e-mail: fernando@gont•com.ar || fgont@si6networks•com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1

next             reply	other threads:[~2013-09-23 19:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-23 19:41 Fernando Gont [this message]
2013-09-24  0:04 ` Question on Netlink IPv6 routing table lookup Hannes Frederic Sowa
2013-09-26 10:36   ` Fernando Gont
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=52409953.8040208@gont.com.ar \
    --to=fernando@gont$(echo .)com.ar \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox