On Thu, 9 Jun 2005 16:33:44 +0200 "Tomo Ceferin" <tomo@xxxxxxxxxxxxxx> wrote: > True. However, allow me to make two assumptions (true in our case): > 1) Bridge implements set_multicast_list() and uses it to learn multicast > groups. > 2) IPv4 or IPv6 is attached to bridge - both provide IGMP snooping which in > turn feeds bridge with multicast lists through set_multicast_list(). > > With both above assumptions true, bridge now has awareness of which ports > belong to which multicast groups, hence removing the need to flood all ports. > > Am I getting something wrong? 1. Bridge does more than IP and so it knows nothing about IP protocols. Many times a bridge has no IP address at all. 2. The bridge machine itself may not be listening the multicast traffic but needs to forward it. 3. If you need to do some filtering of multicast, than use netfilter (ebtables) to restrict the traffic.
