Skip to contentSkip to conversation

bridge igmp snooping implementation

DISCUSSION Felix Fietkau 2 participants 2 messages Sep 25, 2012

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

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

#1 lore raw
Quoted 6 lines · Felix Fietkau

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?

Quoted 8 lines

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.

Good idea. This can help to resolve my problem at:
http://marc.info/?l=linux-netdev&m=134855468803809&w=2

Thanks.

Quoted 6 lines

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