Use both...
The reason being.
BSR --> ip pim bsr boarder does it
AutoRP--> ACL does it
with BSR, i used both in production. It's a bit hard but when you run BSR
with other ISP they might use your series of multicast address. ACL solves
that issue.
On Fri, Jan 18, 2013 at 1:51 AM, ccie99999 <ccie99999_at_gmail.com> wrote:
> in that way you filter auto-rp messages..
>
> for filtering BSR you just need to use the command "ip pim bsr border"
> under the interface on non-multicast domain side.
>
> someone correct me if I am wrong. Thanks
>
>
> On Thu, Jan 17, 2013 at 2:00 PM, Tauseef Khan <tasneemjan_at_googlemail.com
> >wrote:
>
> > To set the multicast boundary for PIM BSR do i need to block the
> following
> > two groups on the interface:
> > 224.0.1.39
> > 224.0.1.40
> >
> > like this?
> > ip access-list 1 deny 224.0.1.39
> > ip access-list 1 deny 224.0.1.40
> > ip access-list 1 permit any
> >
> > int gi0/0
> > ip multicast boundary 1 out
> >
> > Rgards
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> --
> @ccie99999
> https://twitter.com/ccie99999
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Fri Jan 18 2013 - 21:20:36 ART
This archive was generated by hypermail 2.2.0 : Sun Feb 03 2013 - 16:27:17 ART