aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/generic/PATCHES
diff options
context:
space:
mode:
authorFelix Fietkau <nbd@openwrt.org>2015-09-18 12:46:59 +0000
committerFelix Fietkau <nbd@openwrt.org>2015-09-18 12:46:59 +0000
commitfcffd63a995b3eddd22cfd175d197ccc4b3a32d4 (patch)
tree1f799fc31a679708d16f6dbdcca2b720ef7233e1 /target/linux/generic/PATCHES
parent3747e6801438da5ea17e9e3df4d0dbd1848f502f (diff)
downloadupstream-fcffd63a995b3eddd22cfd175d197ccc4b3a32d4.tar.gz
upstream-fcffd63a995b3eddd22cfd175d197ccc4b3a32d4.tar.bz2
upstream-fcffd63a995b3eddd22cfd175d197ccc4b3a32d4.zip
Revert "kernel: disable multicast-to-unicast translation for ipv6 neighbor solicitation (#17625)"
This reverts commit a080e8e1943156168913d0353a2e99d1151102aa. It did not fix the problem but just hid some symptom. The real issue was that IGMP/MLD report suppression was not considered for the multicast-to-unicast feature. A recent netifd which isolates IGMP/MLD reports between STAs by utilizing AP-isolation and bridge-hairpinning should have fixed this. It is perfectly fine to apply multicast-to-unicast to IPv6 Neighbor Solicitations, too (once that feature is configured correctly). Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue> Signed-off-by: Felix Fietkau <nbd@openwrt.org> Backport of r46720 git-svn-id: svn://svn.openwrt.org/openwrt/branches/chaos_calmer@47000 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'target/linux/generic/PATCHES')
0 files changed, 0 insertions, 0 deletions