In our test network R1, R2 and R3 are in the same RIP routing domain All these routers are configured for a PIM-SM mode operation The RP address is set to R3’s fa1/0 interface...
Read More
Multicast: rather than dense, sparse it and let’s meet at rendez-vous point… Part 5
Client1 is configured to join multicast destined for group 226.0.0.1 and sent from Server1 Instead of PIM-Dense (flood and prune) we use PIM-Sparse to build the forwarding path from the server to the client...
Read More
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...
Read More
Multicast routing: From the source… Part 3
We build on our discussion from the previous blogs The test topolgy How R3 handles Server2 source multicast trafic? R3 is the only UP router It’s mroute table show a correct source and incoming...
Read More
5 Minutes
Multicast routing: PIM dense… Part 2
Server2 is 3 hops away from its receivers R3 receives the multicast and forwards it to its forwarding list interfaces At R2 At R2 the outgoing interface list includes also the incoming interface The...
Read More
Multicast routing: a step by step… Part 1
In the above test lab, Servers send multicast trafic to both clients. In IPv4, multicasting servers uses class D range of addresses: 224.0.0.0-239.255.255.255. Some addresses are well known and others for specific use… In...
Read More