Multicast: Hold ASM for a moment, let’s do SSM!… Part 4

IGMPv3 (RFC 4607) allows the receivers to specify the source they wish in additiont the multicast group trafic

By default we use the 232.0.0.0/8 range for SSM

In our lab setup

We configure Client1 to join SSM specific range @ip address 232.0.0.1 sourced from Server1 (in the same subnet)

Is it sufficient split-horizon rule to prevent RIP loops?

Per the split-horizon rule, don’t send an update back on the interface it was received on

What is the challenge here? In addition to bandwidth usage and system resources consumption, Split horizon helps prevent routing loops…

In this kind of loop the routing information is lost, incoherent between the domain routers

RIP: do not split it then… and unleach the power of the “network” command

In RIP domain routers R1 and R2 exchange information about loopback 0 and 1 networks

Router RIP command “network 0.0.0.0” hints routers to add all ip enabled interfaces to the update list and include their “subnets” into this update