From: Wolfgang Nothdurft <netdev@linux-dude.de>
To: netdev@vger.kernel.org
Subject: Forcing the output interface using ip6_route_output doesn't work
Date: Fri, 25 Sep 2015 15:56:55 +0200 [thread overview]
Message-ID: <560552A7.40305@linux-dude.de> (raw)
It seems that the ip6_route_output(net, sk, fl6) kernel function ignores
the fl6.flowi6_oif parameter for the routing decision.
Is this intended?
Should it possible to force the output device for ipv6 routing just as
for ipv4?
Here the example shown with the ip command:
With ipv4, I'm able to get the default route when using oif (force the
output interface).
# ip r
default via 192.168.0.1 dev enp3s0 proto static
192.0.2.0/24 dev enp2s0 proto kernel scope link src 192.0.2.163
192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.163
# ip r get 192.0.2.10
192.0.2.10 dev enp2s0 src 192.0.2.163
cache
# ip r get 192.0.2.10 oif enp3s0
192.0.2.10 via 192.168.0.1 dev enp3s0 src 192.168.0.163
cache
With ipv6, ip -6 route get always returns the specific route.
# ip -6 r
2001:db8:e2::1 dev enp2s0 proto kernel metric 256
2001:db8:e2::/64 dev enp2s0 metric 1024
2001:db8:e3::1 dev enp3s0 proto kernel metric 256
2001:db8:e3::/64 dev enp3s0 metric 1024
fe80::/64 dev enp3s0 proto kernel metric 256
default via 2001:db8:e3::255 dev enp3s0 metric 1024
ip -6 r get 2001:db8:e2::100
2001:db8:e2::100 from :: dev enp2s0 src 2001:db8:e3::1 metric 0
cache
# ip -6 r get 2001:db8:e2::100 oif enp3s0
2001:db8:e2::100 from :: dev enp2s0 src 2001:db8:e3::1 metric 0
cache
The detailed problem is described here, because I got the problem
initially when trying a ipsec Host-2-Host connection with libreswan/klips.
https://bugs.libreswan.org/show_bug.cgi?id=237
Thanks
Wolfgang
next reply other threads:[~2015-09-25 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 13:56 Wolfgang Nothdurft [this message]
2015-09-25 21:13 ` Forcing the output interface using ip6_route_output doesn't work David Ahern
2015-09-26 15:51 ` Wolfgang Nothdurft
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=560552A7.40305@linux-dude.de \
--to=netdev@linux-dude.de \
--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).