Forcing the output interface using ip6_route_output doesn't work
Subsystems (3)
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
cacheWith 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
cacheThe 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
Quoted 2 lines · Wolfgang Nothdurft
It seems that the
ip6_route_output(net, sk, fl6)kernel function ignores the fl6.flowi6_oif parameter for the routing decision.
It is considered, but a mismatch is not considered fatal.
I think the attached should fix your problem.
net/ipv6/route.c +2 -1
@@ -1169,7 +1169,8 @@ struct dst_entry *ip6_route_output(struct net *net, const struct sock *sk, fl6->flowi6_iif =LOOPBACK_IFINDEX ; -if ((sk && sk->sk_bound_dev_if) ||rt6_need_strict (&fl6->daddr)) +if ((sk && sk->sk_bound_dev_if) ||rt6_need_strict (&fl6->daddr) || + fl6->flowi6_oif) flags |=RT6_LOOKUP_F_IFACE ;if (!ipv6_addr_any (&fl6->saddr))
Am 25.09.2015 um 23:13 schrieb David Ahern:
Quoted 9 lines · Wolfgang Nothdurft
Quoted 2 lines
It seems that the
ip6_route_output(net, sk, fl6)kernel function ignores the fl6.flowi6_oif parameter for the routing decision.It is considered, but a mismatch is not considered fatal.
I think the attached should fix your problem.
Thanks, now it works as expected. :)
Wolfgang