From: xprtofnet (xprtofnet@yahoo.com)
Date: Sat Sep 16 2006 - 01:56:33 ART
the only way i got the ping to stop is by using
extended acl and applying it to the interface. Static
rp works ok with rp-announce cmd with group filtering.
autorp does not work with this cmd.
any inputs welcome.
--- xprtofnet <xprtofnet@yahoo.com> wrote:
> Folks,
>
> This is what i am trying to do but dont know if
> whats
> wrong:
>
> I want RP to accept registration from 224.2.2.2 only
> and i am denying 224.3.3.3
>
> Here is RP configs:
>
> ip pim send-rp-announce Loopback0 scope 10
> group-list
> 10
> ip pim send-rp-discovery Loopback0 scope 10
> !
> access-list 10 permit 224.2.2.2 log
> access-list 10 deny 224.3.3.3 log
> !
>
> but here is what it shows:
>
> R4#sho ip pim rp map
> PIM Group-to-RP Mappings
> This system is an RP (Auto-RP)
> This system is an RP-mapping agent (Loopback0)
>
> Group(s) 224.2.2.2/32
> RP 100.1.4.4 (?), v2v1
> Info source: 100.1.4.4 (?), elected via Auto-RP
> Uptime: 00:03:49, expires: 00:02:11
> Group(s) (-)224.3.3.3/32
> RP 100.1.4.4 (?), v2v1
> Info source: 100.1.4.4 (?), elected via Auto-RP
> Uptime: 00:03:49, expires: 00:02:07
> R4#
>
> Why is 224.3.3.3 showing up when I have a filter ?
>
> I am not sure what (-) means...but i am able to PING
> this group.
>
> How can I stop the Source/Recievers from
> communicating
> through RP with filtering ?
>
>
> Thank you..
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam
> protection around
> http://mail.yahoo.com
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam
> protection around
> http://mail.yahoo.com
>
>
This archive was generated by hypermail 2.1.4 : Sun Oct 01 2006 - 16:55:40 ART