control multicast

Oct 02, 2006 6 Replies
control multicast open original image

I have a host on the network which I cannot find sending out traffic to the entire net destination ip


224.0.0.251

Is there anyway I can block this kind of traffic to prevent it from going to the entire net. its a layer 2 network here


You don't say what kind of equipment you have. If you have something like Cat 2950 switches then you might be able to block it, but anything lower level (e.g., 1900XL switches) probably not.

Looks like 224.0.0.251 is multicast DNS, such as is used by

formatting link
It tends to be turned on Apple and Windows systems both. A Windows system that does not get a response to DHCP will use it. This is all related to those 169.254.*.* addresses you see sometimes.

arpwatch might perhaps help you chase down the system.

CatOS or IOS? And which version and which feature set? Which supervisor engine?

For example if it is IOS and SE2+, SE3 or SE4, you could follow the "Configuring and Monitoring Policing" example at

formatting link
but change the access-list 111 to access-list 111 permit ip any host 240.0.0.252 and change the conform-action to drop

There might be other ways ;-)

formatting link

I don't think that Walter's approach will work in a Layer 2 interface but I may be mistaken.

There are several possible approaches

You could block it or send it somewhere that it will do no harm or maybe turn off multicast forwarding altogether.

formatting link
"Configuring a Static Connection to a Multicast Receiver" Send it somewhere.

formatting link
"...Use of MAC Access Lists ..." This is the idea but you would have to work out the mac-address of the packets that you want to block. This would need to be applied to all interfaces.

There is an algorithmic mapping between IP and MAC multicast addresses.

formatting link
"each Ethernet multicast address corresponds to 32 IP multicast addresses"

So you would have to block a range of 32 IP Addresses but that may not be an issue.

What happens if you turn off IGMP?

The documentation specifically indicates that the QoS policy may be applied to a port or to a VLAN. It also talks about per-interface policers.

There isn't anything -obvious- in the referenced documentation that would require a layer 3 interface.

Sorry, failed to read the post properly, just saw the ACL and assumed that that is all there was.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required