Hi all, as switches treat multicasts like broadcasts, does my pc have to process each multicast like it does with a broadcast to see if its ment for that pc? also how do you stop the switch flooding multicasts, would I just enable igmp snooping ?
I believe a PC NIC should only forward multicast packets to the host's IP stack if the host is interested in them, although since there's overlap in Ethernet multicast addressing for unique IP multicast addressing, the NIC might forward multicast frames that the host isn't interested in at the IP level.
Yes, IGMP snooping is what's normally used to stop flooding multicast to switch ports that are uninterested in receiving multicast packets. (Not all switches have this capability.)
PCs send multicast group membership report to the router/switch for multicast group that it wants join/to be a part of. It does nothing with a multicast traffic that is flooded to a multicast group, which it is not a member of, unlike broadcast.
Although PCs do not utilize the unrelated multicast packets, flooding multicast traffic to unnecessary ports affects throughput, bandwith and resource utilization. You can either use IGMP or CGMP depending on your equipment. CGMP is recommended if you are low on switch resources.
For the switch to avoid flooding multicasts out all its ports, it should be configured for CGMP or IGMP snooping. By enabling either of these, switch prepare CAM entries for hosts willing to listen mcasts for specific groups. remember this information, which hosts are interrested to listen mcasts & belong to which mcast group is communicated to the switch by the router in case of CGMP(hosts doesnt indicate switch of hteir interest in mcast traffic). In case of IGMP snooping, switches sniff the pkts send by the hosts & thus bulit the CAM for mcast. Separate CAM entries for each group are maintained by switch.
Keep in mind also that there are two different multicast behaviors. Some multicasts can be forwarded beyond your local segment. SOme multicasts stay on the local segment and are not forwarded beyond it.
The range of addresses between 126.96.36.199 and 188.8.131.52, inclusive, is reserved for the use of routing protocols and other low-level topology discovery or maintenance protocols, such as gateway discovery and group membership reporting. Multicast routers should not forward any multicast datagram with destination addresses in this range, regardless of its TTL. RFC 3171
You might also want to use PIM if your multicasts are spanning multiple routers. As well as IGMP snooping.
But I don't think IGMP snooping would affect the traffic in the 184.108.40.206 to 220.127.116.11 range.
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...