IGMP/MLD snooping through multiple bridges

As described, IGMP/MLD snooping only forwards incoming Join or Leave messages via router ports. In a structure with multiple bridges, initially none of the ports are router ports or members of a multicast group. If a station connected to the bridge registers with a multicast group, the port automatically becomes a member of this group. However, none of the ports are router ports at this phase, so the Join messages are not forwarded anywhere. Other bridges thus receive no information about the port's membership with the multicast group.





Consequently, bridges must have router ports in order for membership information to be propagated. Since the ports of a bridge only become router ports in the case of IGMP/MLD queries, one of the multicast-capable routers in the network must take over the task of distributing the necessary IGMP/MLD queries throughout the network. This router is referred to as the IGMP/MLD querier. If the network does not contain a multicast router, the access points are capable of simulating a querier. To avoid parallel queries arriving from various queriers, a querier will deactivate itself if it discovers another querier with a lower IP number. The distribution of IGMP/MLD information by the querier can be explained with the following example:

  1. The querier (Bridge 2 in this example) regularly sends out IGMP/MLD queries on all ports of bridge 2 (dotted lines). The next bridge (Bridge 1) receives the query on a port which is then marked as a router port (R). PC 1 responds to this query with a Join message for all multicast groups (light dashed lines) that it wishes to join. The port connecting PC 1 to Bridge 2 then becomes a member of the multicasting group(s).
  2. In addition to this, Bridge 1 sends the queries on all other ports to the bridges and stations lower down in the structure. In Bridge 3 the port receiving the query becomes a router port (R).
  3. The station (PC2) connected to Bridge 3 responds to this query with a Join message for all registered multicast groups. The port connecting PC 2 to Bridge 3 then becomes a member of the multicasting group(s).
  4. Bridge 3 forwards this Join message to Bridge 1 over the router port. The receiving port on Bridge 1 thus also takes on membership of the multicast groups that PC 2 has registered for.
  5. In the final step, Bridge1 forwards the Join message from PC 2 via the router port to Bridge 2, where the receiving port also takes on membership of PC 2's multicast groups.




If PC 1 now transmits a multicast for which PC 2 has registered, all of the bridges (2, 1 and then 3) forward the packets to PC 2 via the member port.

www.lancom-systems.com

LANCOM Systems GmbH | A Rohde & Schwarz Company | Adenauerstr. 20/B2 | 52146 Wuerselen | Germany | E‑Mail info@lancom.de

LANCOM Logo