Multicast usage examples
RouterOS supports PIM-SM and IGMP-Proxy as possible tools to manage and enable multicast traffic in network user is controlling. It is important to use correct tools and correct values to avoid problems that can arise while using multicast traffic.
There are several configurations available, each of them have its benefits and drawbacks.
If router hardware resources allow, it is possible to configure multicast network using just PIM-SM
- use more router resources to manage it.
- clients should be IGMP aware to manage joins to groups
- more information about what is happening
- more control over what is supported and what is not
- works for all possible network topologies
Network can be IGMP-Proxy only if network topology is simple and without loops (for example star topology)
- if you have complex network topology it will not be suitable
- almost no control over multicast streaming
- no multicast sources in network
- simple configuration
- uses little resources to sustain multicast
- with static multicast routes, clients can be IGMP unaware.
when combining both methods together then it is possible to get best out of both. Backbone with PIM-SM configuration for management, client areas with IGMP proxy.
- routers with complex configuration become even more complex
- configuration with simple configurations does not get any more complex
- Full control over what happens where, due to PIM-SM controls every necessary aspect.