Skip to content

test with multicast snooping

Nicolas Bonnand edited this page Sep 5, 2018 · 11 revisions

9.4 Test with Multicast snooping enabled.

9.4.1 Without any listener multicast is dropped

Let's have again a look at statistics. multicastnetwork

  • a Push button to reset time origin for counters calculation. ( Sort of 'clear counters' )
  • b Wait a little and refresh.

We see that although W01 is still emitting multicast through P01 (c), no multicast is forwarded through P02 (d) and P03(e).

9.4.2 One listener started

Let's start a multicast listener on W02. multicastnetwork Immediately, we can see with wireshark that our listener 10.0.0.2 sends an IGMP packet. multicastnetwork br1 bridge instantly reacts after receiving this IGMP packet and enables forwarding of multicast traffic from 10.0.0.1 to W02.

multicastnetwork

  • f Push button to reset time origin for counters calculation. ( Sort of 'clear counters' )
  • g Wait a little and refresh. We can see that traffic is received by port P01 at 12798 byt/sec (h) and that this traffic is forwarded to P02 (m) but not to P03 (n) which is exactly what we want.

9.4.3 Additional multicast information

multicastnetwork

  • o Press button
  • p Output popup will appear and display information about br1 multicast table.

We see that last igmp message received by br1 on port P02 (of_number=1002 ) for multicast 226.1.1.1 was 135 second ago. (Remember that without any IGMP message from W02, this information will be destroyed when reaching ageing_time=300 sec and multicast forwarding will be stopped.)

Clone this wiki locally