summaryrefslogtreecommitdiffstats
path: root/net/ipv6
diff options
context:
space:
mode:
authorJiri Olsa <jolsa@redhat.com>2010-04-20 21:21:26 +0000
committerDavid S. Miller <davem@davemloft.net>2010-04-21 22:59:24 -0700
commitf4f914b58019f0e50d521bbbadfaee260d766f95 (patch)
tree7a9690cf187a0b2c0f7583f94668ef307690c9bb /net/ipv6
parentf2228f785a9d97307aa8ba709088cfda6c3df73f (diff)
downloadlinux-stable-f4f914b58019f0e50d521bbbadfaee260d766f95.tar.gz
linux-stable-f4f914b58019f0e50d521bbbadfaee260d766f95.tar.bz2
linux-stable-f4f914b58019f0e50d521bbbadfaee260d766f95.zip
net: ipv6 bind to device issue
The issue raises when having 2 NICs both assigned the same IPv6 global address. If a sender binds to a particular NIC (SO_BINDTODEVICE), the outgoing traffic is being sent via the first found. The bonded device is thus not taken into an account during the routing. From the ip6_route_output function: If the binding address is multicast, linklocal or loopback, the RT6_LOOKUP_F_IFACE bit is set, but not for global address. So binding global address will neglect SO_BINDTODEVICE-binded device, because the fib6_rule_lookup function path won't check for the flowi::oif field and take first route that fits. Signed-off-by: Jiri Olsa <jolsa@redhat.com> Signed-off-by: Scott Otto <scott.otto@alcatel-lucent.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv6')
-rw-r--r--net/ipv6/route.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/net/ipv6/route.c b/net/ipv6/route.c
index c2438e8cb9d0..05ebd7833043 100644
--- a/net/ipv6/route.c
+++ b/net/ipv6/route.c
@@ -815,7 +815,7 @@ struct dst_entry * ip6_route_output(struct net *net, struct sock *sk,
{
int flags = 0;
- if (rt6_need_strict(&fl->fl6_dst))
+ if (fl->oif || rt6_need_strict(&fl->fl6_dst))
flags |= RT6_LOOKUP_F_IFACE;
if (!ipv6_addr_any(&fl->fl6_src))