Johannes Berg
2017-Jan-06 13:54 UTC
[Bridge] [PATCH net-next] bridge: multicast to unicast
> The bridge layer can use IGMP snooping to ensure that the multicast > stream is only transmitted to clients that are actually a member of > the group. Can the mac80211 feature do the same?No, it'll convert the packet for all clients that are behind that netdev. But that's an argument for dropping the mac80211 feature, which hasn't been merged upstream yet, no? johannes
Felix Fietkau
2017-Jan-06 13:54 UTC
[Bridge] [PATCH net-next] bridge: multicast to unicast
On 2017-01-06 14:54, Johannes Berg wrote:> >> The bridge layer can use IGMP snooping to ensure that the multicast >> stream is only transmitted to clients that are actually a member of >> the group. Can the mac80211 feature do the same? > > No, it'll convert the packet for all clients that are behind that > netdev. But that's an argument for dropping the mac80211 feature, which > hasn't been merged upstream yet, no?Right. - Felix
Am 06.01.2017 um 14:54 schrieb Johannes Berg:> >> The bridge layer can use IGMP snooping to ensure that the multicast >> stream is only transmitted to clients that are actually a member of >> the group. Can the mac80211 feature do the same? > > No, it'll convert the packet for all clients that are behind that > netdev. But that's an argument for dropping the mac80211 feature, which > hasn't been merged upstream yet, no?But there is multicast/broadcast traffic like e.g. ARP and some IP multicast groups that are not covered by IGMP snooping. The mac80211 patch converts this to unicast as well, which the bridge cannot do. That way, these features both complement and overlap each other. Regards, Michael