ip multicast boundary

I was playing with the ip multicast boundary command and ran into some
confusion.

I set up a network with all routers running sparse-dense mode. I'm running
Auto-RP
to advertise an RP for all groups and set up a router's interface to join
group 225.0.0.1.
All routers in the network can ping 225.0.0.1.

           Network-----R6-----R9

 Now, R9 can only access the rest of the network through it's multilink 1
interface
connected to R6. I created an ACL blocking 225.0.0.1 but allowing all other
groups and
configured ip multicast boundary with that ACL on R6's multilink interface
connection
to R9. With this in place I should still get the RP information because
224.0.1.39 &
224.0.1.40 are both still allowed, but, I should no longer be able to ping
225.0.0.1
from R9 because that group is blocked using the ip multicast boundary
command.?.?

With this in place I CAN ping 225.0.0.1 from R9. Do I not understand the
functionality of ip multicast boundary? Is it not basically a bi-directional
ACL
applied only to multicast traffic?

R6:
interface Multilink1
 ip address 150.50.96.6 255.255.255.0
 ip pim sparse-dense-mode
 ip multicast boundary 5
 ppp multilink
 ppp multilink group 1

access-list 5 deny 225.0.0.1
access-list 5 permit 224.0.0.0 15.255.255.255

Thanks,
Bryan R.

Blogs and organic groups at http://www.ccie.net
Received on Tue Apr 14 2009 - 15:17:07 ART