aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/dl_cleanup.py
diff options
context:
space:
mode:
authordaniel <daniel@dd-wrt.com>2016-06-30 23:49:52 +0200
committerJohn Crispin <john@phrozen.org>2016-06-30 22:48:39 +0200
commitf576ff05a1523a0c61a3399087454034d4739f2c (patch)
tree4d73eeeb0ce8b28774f38f5f82b0b4b26c4eeb32 /scripts/dl_cleanup.py
parent97c90557a9f5a6edf9cb0e9b51e7e6d0830ce34d (diff)
downloadupstream-f576ff05a1523a0c61a3399087454034d4739f2c.tar.gz
upstream-f576ff05a1523a0c61a3399087454034d4739f2c.tar.bz2
upstream-f576ff05a1523a0c61a3399087454034d4739f2c.zip
kernel: Fix ipv6 mc snooping if bridge has no ipv6 address
This patch is a backport for current LEDE 4.4 Kernels. It is already upstream, for linux-next and stable. The initial commit message is below: The bridge is falsly dropping ipv6 mulitcast packets if there is: 1. No ipv6 address assigned on the brigde. 2. No external mld querier present. 3. The internal querier enabled. When the bridge fails to build mld queries, because it has no ipv6 address, it slilently returns, but keeps the local querier enabled. This specific case causes confusing packet loss. Ipv6 multicast snooping can only work if: a) An external querier is present OR b) The bridge has an ipv6 address an is capable of sending own queries Otherwise it has to forward/flood the ipv6 multicast traffic, because snooping cannot work. This patch fixes the issue by adding a flag to the bridge struct that indicates that there is currently no ipv6 address assinged to the bridge and returns a false state for the local querier in __br_multicast_querier_exists(). Special thanks to Linus Lüssing. Signed-off-by: Daniel Danzberger <daniel@dd-wrt.com>
Diffstat (limited to 'scripts/dl_cleanup.py')
0 files changed, 0 insertions, 0 deletions