netdev - bridge igmp snooping implementation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <506184ED.5040104@openwrt.org>
Date:	Tue, 25 Sep 2012 12:18:21 +0200
From:	Felix Fietkau <nbd@...nwrt.org>
To:	netdev <netdev@...r.kernel.org>
CC:	Herbert Xu <herbert@...dor.apana.org.au>
Subject: bridge igmp snooping implementation

Hi,

I'v been looking at the bridge IGMP snooping code and I noticed that it
appears to not keep track of multicast group member IP addresses. Is
this intentional?

It seems to me that this would lead to issues when multiple members of
the same multicast group are behind the same bridge port, and one of
them leaves.

I'm currently looking into adding a feature that allows bridge ports to
be configured to selectively turn multicast traffic into unicast
traffic. For this I would need to change the code to keep track of
member IP and MAC addresses.

This helps a lot on 802.11, where unicast is often much cheaper than
multicast, even when sending out duplicate packets (higher data rates
and aggregation heavily reduce airtime utilization).

- Felix
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html