summaryrefslogtreecommitdiff
path: root/firmware
diff options
context:
space:
mode:
authorOctavian Purdila <opurdila@ixiacom.com>2010-01-06 20:37:01 -0800
committerDavid S. Miller <davem@davemloft.net>2010-01-06 20:37:01 -0800
commit7ad6848c7e81a603605fad3f3575841aab004eea (patch)
treec95cc3473a2c47d6dedbbe5bc1a298546fc4127f /firmware
parent58933c643f86651decc4818cf680f9ec3b0460d2 (diff)
downloadlinux-3.10-7ad6848c7e81a603605fad3f3575841aab004eea.tar.gz
linux-3.10-7ad6848c7e81a603605fad3f3575841aab004eea.tar.bz2
linux-3.10-7ad6848c7e81a603605fad3f3575841aab004eea.zip
ip: fix mc_loop checks for tunnels with multicast outer addresses
When we have L3 tunnels with different inner/outer families (i.e. IPV4/IPV6) which use a multicast address as the outer tunnel destination address, multicast packets will be loopbacked back to the sending socket even if IP*_MULTICAST_LOOP is set to disabled. The mc_loop flag is present in the family specific part of the socket (e.g. the IPv4 or IPv4 specific part). setsockopt sets the inner family mc_loop flag. When the packet is pushed through the L3 tunnel it will eventually be processed by the outer family which if different will check the flag in a different part of the socket then it was set. Signed-off-by: Octavian Purdila <opurdila@ixiacom.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions