[c-nsp] Ignoring / limiting 239.255/16

Collins, Richard (SNL US) richard.collins.ext at nsn.com
Mon Jul 23 15:34:15 EDT 2007


You were right about the combination of commands.  Here is a good link
ftp://ftpeng.cisco.com/ipmulticast/config-notes/upnp-note.txt

I wouldn't know about the last part of  your question.

-Richard

> Message: 6
> Date: Mon, 23 Jul 2007 14:08:51 +0100
> From: Phil Mayers <p.mayers at imperial.ac.uk>
> Subject: [c-nsp] Ignoring / limiting 239.255/16
> To: cisco-nsp at puck.nether.net
> Message-ID: <1185196131.16985.20.camel at doorstop.net.ic.ac.uk>
> Content-Type: text/plain
> 
> We've got a lot of winXP boxes on-net which join the UPnP groups and
the
> multicast routing table is filled with useless entries.
> 
> Given that we don't have access lists at layer2, what is the best way
of
> preventing out routers:
> 
>  a. processing the IGMP joins
>  b. forwarding the packets
> 
> The network is 6500s running SXF6 (and upwards). If it matters (it
> shouldn't, I suspect) the networks are VRFs using MPLS and MVPN.
> 
> I suspect a combination of "ip igmp access-list" and "ip multicast
> boundary" would help, but I'm not sure on the syntax.
> 
> Also - is it *strictly* legal to limit these addresses to the local
> subnet?
> 
> 
>  



More information about the cisco-nsp mailing list