diff options
author | Paolo Abeni <pabeni@redhat.com> | 2016-06-23 16:25:09 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2016-06-27 17:37:20 +0300 |
commit | 48f1dcb55a7d29aeb8965c567660c14d0dfd1a42 (patch) | |
tree | 1707081a7e522c1f4ae9a8b30997e4f72532ef0c /drivers/dax | |
parent | 5aa3e24928bb95ddb159c5949f1c09493e9e8505 (diff) | |
download | linux-48f1dcb55a7d29aeb8965c567660c14d0dfd1a42.tar.xz |
ipv6: enforce egress device match in per table nexthop lookups
with the commit 8c14586fc320 ("net: ipv6: Use passed in table for
nexthop lookups"), net hop lookup is first performed on route creation
in the passed-in table.
However device match is not enforced in table lookup, so the found
route can be later discarded due to egress device mismatch and no
global lookup will be performed.
This cause the following to fail:
ip link add dummy1 type dummy
ip link add dummy2 type dummy
ip link set dummy1 up
ip link set dummy2 up
ip route add 2001:db8:8086::/48 dev dummy1 metric 20
ip route add 2001:db8:d34d::/64 via 2001:db8:8086::2 dev dummy1 metric 20
ip route add 2001:db8:8086::/48 dev dummy2 metric 21
ip route add 2001:db8:d34d::/64 via 2001:db8:8086::2 dev dummy2 metric 21
RTNETLINK answers: No route to host
This change fixes the issue enforcing device lookup in
ip6_nh_lookup_table()
v1->v2: updated commit message title
Fixes: 8c14586fc320 ("net: ipv6: Use passed in table for nexthop lookups")
Reported-and-tested-by: Beniamino Galvani <bgalvani@redhat.com>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Acked-by: David Ahern <dsa@cumulusnetworks.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/dax')
0 files changed, 0 insertions, 0 deletions