From: David Ahern <[email protected]>
Date: Wed, 7 Oct 2015 08:40:13 -0700
> Commit deaa0a6a930 ("net: Lookup actual route when oif is VRF device")
> exposed a bug in __ip_route_output_key_hash for VRF devices: on FIB lookup
> failure if the oif is specified the current logic drops to make_route on
> the assumption that the route tables are wrong. For VRF/L3 master devices
> this leads to wrong dst entries and route lookups. For example:
> $ ip route ls table vrf-red
> unreachable default
> broadcast 10.2.1.0 dev eth1 proto kernel scope link src 10.2.1.2
> 10.2.1.0/24 dev eth1 proto kernel scope link src 10.2.1.2
> local 10.2.1.2 dev eth1 proto kernel scope host src 10.2.1.2
> broadcast 10.2.1.255 dev eth1 proto kernel scope link src 10.2.1.2
>
> $ ip route get oif vrf-red 1.1.1.1
> 1.1.1.1 dev vrf-red src 10.0.0.2
> cache
>
> With this patch:
> $ ip route get oif vrf-red 1.1.1.1
> RTNETLINK answers: No route to host
>
> which is the correct response based on the default route
>
> Signed-off-by: David Ahern <[email protected]>
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
