aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/brcm47xx/patches-4.1/160-kmap_coherent.patch
diff options
context:
space:
mode:
authorFelix Fietkau <nbd@openwrt.org>2015-08-25 07:25:10 +0000
committerFelix Fietkau <nbd@openwrt.org>2015-08-25 07:25:10 +0000
commitea9963bb212d5bca446d081ed7c85946a1e20850 (patch)
tree247e10dd16bb5d96abffe2c9115156f646e89b76 /target/linux/brcm47xx/patches-4.1/160-kmap_coherent.patch
parentd4e9c8d7efcbc66e97ff8688cceb17055a2297db (diff)
downloadupstream-ea9963bb212d5bca446d081ed7c85946a1e20850.tar.gz
upstream-ea9963bb212d5bca446d081ed7c85946a1e20850.tar.bz2
upstream-ea9963bb212d5bca446d081ed7c85946a1e20850.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> SVN-Revision: 46720
Diffstat (limited to 'target/linux/brcm47xx/patches-4.1/160-kmap_coherent.patch')
0 files changed, 0 insertions, 0 deletions