<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">Thanks Linus.<br>Sorry, it will not be possible to move to recent kernel.<br><br></div><div class="gmail_quote">How does the mdb gets updated for multicast addresses? Is it learnt on basis of packets received from the network? For example, the multicast address I use for iperf is 234.100.100.100. I mentioned two scenarios in my earlier email. In case of eth0 being the active port on the mbr (multicast working scenario), I see br_multicast_new_group() and br_multicast_add_group() being called for this IP address moments after mbr is up. However in case of wlan0 as the uplink port of mbr, I don't see those functions being called.<br><br></div><div class="gmail_quote">I guess for unicast packets, if the entry is not present in fdb, the packet is flooded on all other ports and its learnt and added to fdb based on the port on which response packet arrives. Is it true for Multicast packets too?<br></div><div class="gmail_quote"><br></div><div class="gmail_quote">Regards,<br></div><div class="gmail_quote">Saurav<br></div><div class="gmail_quote"><br>On Fri, Jul 31, 2015 at 7:27 PM, Linus Lüssing <span dir="ltr"><<a href="mailto:linus.luessing@c0d3.blue" target="_blank">linus.luessing@c0d3.blue</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Saurav,<br>
<span class=""><br>
On Fri, Jul 31, 2015 at 03:50:35PM +0530, saurav barik wrote:<br>
> I am working on an Access Point device (AP1) running linux kernel 3.0.34 on<br>
> which my bridge configuration is as follows.<br>
<br>
</span>There were quite some crucial bugs, I'm not quite sure whether<br>
3.0.34 was actually usuable for multicast snooping.<br>
<br>
Any chance to try a recent kernel?<br>
<br>
Cheers, Linus<br>
</blockquote></div><br></div></div>