Jiri Olsa f4f914b580 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>		2010-04-21 22:59:24 -07:00
..
9p
802
8021q
appletalk
atm
ax25
bluetooth
bridge
can
core	net: Fix an RCU warning in dev_pick_tx()	2010-04-21 01:09:44 -07:00
dcb
dccp
decnet
dsa
econet
ethernet
ieee802154
ipv4
ipv6	net: ipv6 bind to device issue	2010-04-21 22:59:24 -07:00
ipx
irda
iucv
key
lapb
llc
mac80211
netfilter
netlabel
netlink
netrom
packet
phonet
rds
rfkill
rose
rxrpc
sched
sctp
sunrpc
tipc
unix
wanrouter
wimax
wireless
x25	X25 fix dead unaccepted sockets	2010-04-21 16:31:50 -07:00
xfrm
compat.c
Kconfig
Makefile
nonet.c
socket.c
sysctl_net.c
TUNABLE