summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin
diff options
context:
space:
mode:
authorNikolay Aleksandrov <nikolay@cumulusnetworks.com>2016-10-31 15:21:05 +0300
committerDavid S. Miller <davem@davemloft.net>2016-10-31 23:18:30 +0300
commit91b02d3d133bbb101466325cdd9a6007cd9ec5a8 (patch)
tree05987ec9f8f4c7bfcb2b29c59d89d6a4096fb86b /tools/perf/scripts/python/bin
parent56245cae19f5ccb371fa63b09bb6b9ce7c0f1266 (diff)
downloadlinux-91b02d3d133bbb101466325cdd9a6007cd9ec5a8.tar.xz
bridge: mcast: add router port on PIM hello message
When we receive a PIM Hello message on a port we can consider that it has a multicast router attached, thus it is correct to add it to the router list. The only catch is it shouldn't be considered for a querier. Using Daniel's description: leaf-11 leaf-12 leaf-13 \ | / bridge-1 / \ host-11 host-12 - all ports in bridge-1 are in a single vlan aware bridge - leaf-11 is the IGMP querier - leaf-13 is the PIM DR - host-11 TXes packets to 226.10.10.10 - bridge-1 only forwards the 226.10.10.10 traffic out the port to leaf-11, it should also forward this traffic out the port to leaf-13 Suggested-by: Daniel Walton <dwalton@cumulusnetworks.com> Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions