netdev - Forcing the output interface using ip6_route

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 25 Sep 2015 15:56:55 +0200
From:	Wolfgang Nothdurft <netdev@...ux-dude.de>
To:	netdev@...r.kernel.org
Subject: Forcing the output interface using ip6_route_output doesn't work

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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html