Revert "kernel: disable multicast-to-unicast translation for ipv6 neighbor solicitati...
authornbd <nbd@3c298f89-4303-0410-b956-a3cf2f4a3e73>
Tue, 25 Aug 2015 07:25:10 +0000 (07:25 +0000)
committernbd <nbd@3c298f89-4303-0410-b956-a3cf2f4a3e73>
Tue, 25 Aug 2015 07:25:10 +0000 (07:25 +0000)
commit31ab13abf3c1422ff80ea4ab09a429237b33f37e
treee08e10f5225ed2a1d608006ce2347d6d663887fa
parentcac0fece39a7c6a9d7749082e7658e0eaab12b55
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>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@46720 3c298f89-4303-0410-b956-a3cf2f4a3e73
target/linux/generic/patches-3.18/645-bridge_multicast_to_unicast.patch
target/linux/generic/patches-4.1/645-bridge_multicast_to_unicast.patch