Skip to Content.
Sympa Menu

wg-multicast - Re: constraining that pesky 239.255/16 traffic in a CGMP Borg

Subject: All things related to multicast

List archive

Re: constraining that pesky 239.255/16 traffic in a CGMP Borg


Chronological Thread 
  • From: Amel Caldwell <>
  • To: Alan Crosswell <>
  • Cc: wg-multicast <>
  • Subject: Re: constraining that pesky 239.255/16 traffic in a CGMP Borg
  • Date: Thu, 2 Oct 2003 14:45:00 -0700 (Pacific Daylight Time)

Alan--

I modified our inbound spoofing filters to deny ip any 239.255.0.0 0.0.255.255
before permitting the local subnet traffic out. I don't know the
ramifications on CGMP on this approach though.

Amel

On Thu, 2 Oct 2003, Alan Crosswell wrote:

>I want to define site-local as the same as link-local to constrain all
>the hokey SSDP and other 239.255/16 traffic on my campus. Can anyone
>suggest the "right" way to do this? I've tried blocking registers to
>the RP with "ip pim accept-register" which results in a syslog for each
>register attempt that is ignored, causing a lot of clutter.
>
>I've also tried "ip igmp access-group" on the individual router
>interfaces since I really don't want to know about these groups.
>However, this has wierd CGMP ramifications it seems: membership reports
>seem to cause the switch to get a CGMP join for the GDA. v2 leaves
>however do not cause a CGMP leave to make it to the switch, so the
>static cam entry hangs aroud forever.
>
>/a
>
>




Archive powered by MHonArc 2.6.16.

Top of Page