ping a multicast address specifying source interface

ok,

leave it.. I've just realized that ping 224.x.x.x source interface doesn't
work.. I must use extended ping.

---------- Forwarded message ----------
From: ccie99999 <ccie99999_at_gmail.com>
Date: Tue, Oct 23, 2012 at 9:20 AM
Subject: ping a multicast address specifying source interface
To: Cisco certification <ccielab_at_groupstudy.com>

Hi guys,

is it just me and my gns3 or ping to a multicast address specifying the
source interface does not work very well?

I've a lab where I filter sources using "ip pim accept-register list"

my expectation are that I can filter all sources in the access-list
specified in the command above.. and this works. (in the access-list
loopback addresses are permitted)

I would also expect that if I do ping 224.x.x.x source loo 0 this would
work.. but it doesn't.

I'm using ip pim sparse-dense mode and I've specified the rp-address.

the ip pim sparse-mode is configured also on the loopback interfaces.

on the rp I get these messages even when I ping from loopbacks:

%PIM-4-INVALID_SRC_REG: Received Register from y.y.y.y for (x.x.x.x,
224.x.x.x), not willing to be RP

where am I wrong?

thanks

-- 
@ccie99999
-- 
@ccie99999
Blogs and organic groups at http://www.ccie.net