I believe that there is an important aspect of this that has not yet been addressed. Ryel phrases his requirement as being traffic from a multicast group but the multicast address would be the destination address. Multicast traffic is traffic from a unicast source to a multicast group. A standard access list such as access list 13 can only check the source address. If Ryel wants to restrict traffic to particular multicast groups then the access list needs to be an extended access list so that it can check the destination address.
thanks for pointing out the most important aspect: I thought it was an ACL to use with an RP not to filter traffic you are right in that case an extended acl has to be used with destination field = multicast group
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...