hi Rin,
i've found myself in the same problem,
debug ip pim autorp is your friend.
applying the method 1 it's ok but it does not block pim discovery and
announcement messages.
so i've added the filter-rp option to the multicast boundary command.
/R
2009/6/19 Rin <rintrum_at_gmail.com>
> Hi all,
>
>
>
> Anyone find the differences between below methods to prevent Auto-RP
> message
> leaking:
>
> Method 1:
>
> ip access-list standard FILTER_AUTORP
>
> deny 224.0.1.39
>
> deny 224.0.1.40
>
> permit any
>
> !
>
> interface Serial0/0
>
> ip multicast boundary FILTER_AUTORP
>
> ++++++++++++++++++++++++++++++
>
> Method 2:
>
> ip access-list extended FILTER_AUTORP
>
> deny ip any host 224.0.1.39
>
> deny ip any host 224.0.1.40
>
> permit ip any any
>
> !
>
> interface Serial0/0
>
> ip access-group FILTER_AUTORP in
>
> ip access-group FILTER_AUTORP out
>
>
>
> Thanks.
>
> Rin.
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
-- Faeddare pagu, sabidorla meda. Blogs and organic groups at http://www.ccie.netReceived on Sat Jun 20 2009 - 10:20:23 ART
This archive was generated by hypermail 2.2.0 : Wed Jul 01 2009 - 20:02:37 ART