It [IGMPv3] supports Source Specific Multicast (SSM) in contrast to IGMPv2.
Quoting the documentation on IGMPv3: "The Source Specific Multicast feature is an extension of IP multicast where datagram traffic is forwarded to receivers from only those multicast sources to which the receivers have explicitly joined. For multicast groups configured for SSM, only source-specific multicast distribution trees (no shared trees) are created."
The biggest improvement that IGMPv3 offers over IGMPv2 is the ability to support source-specific joins. With IGMPv2, receivers could only request membership of a group and that would mean that traffic for that group would be sent to the receiver regardless of which source was sending to that group. With IGMPv3, receivers can request to only get traffic from a specific source, S, for a group G. That means that only the traffic that is being sent to that G by that particular source S will be sent to the receiver. If another source S2 starts sending to the same group, that traffic will NOT be sent.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.