[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAF1ivSZqjaWvj4JkkzM_PTBuqYSKDdkYXxijfRWdcWqaF_P4-g@mail.gmail.com>
Date: Tue, 25 Sep 2012 23:12:00 +0800
From: Lin Ming <mlin@...pku.edu.cn>
To: Felix Fietkau <nbd@...nwrt.org>
Cc: netdev <netdev@...r.kernel.org>,
Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: bridge igmp snooping implementation
On Tue, Sep 25, 2012 at 6:18 PM, Felix Fietkau <nbd@...nwrt.org> wrote:
> 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.
Good idea. This can help to resolve my problem at:
http://marc.info/?l=linux-netdev&m=134855468803809&w=2
Thanks.
>
> 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
Powered by blists - more mailing lists