From: Padhu (LFG) (padhu@xxxxxxxxxxxx)
Date: Fri Aug 03 2001 - 13:19:07 GMT-3
How about if the R4 was RP for ONLY r4 - join group 224.8.8.4 r6 join
group 224.8.8.6, r3 join group 224.8.8.6. So R3 would not know who the RP
is for r5 - join group 224.8.8.5. Just a guess . I am kinda weak on
multicasting.
Cheers,Padhu
-----Original Message-----
From: Brian Hescock [mailto:bhescock@cisco.com]
Sent: Thursday, August 02, 2001 10:13 PM
To: Piperw222@aol.com
Cc: ccielab@groupstudy.com
Subject: Re: multicasting route filtering
What are the limitations of the practice lab, i.e. must you have the
mroute for 224.8.8.5 on R3 but can't ping 224.8.8.5? Naturally, you could
just use an extended access-list to filter it or use "ip
multicast boundary" on the outbound interface on r3 and in the access-list
for the command have it apply to 224.8.8.5 only.
Brian
On Thu, 2 Aug 2001 Piperw222@aol.com wrote:
> here is the scenario
>
> all connected through frame relay multicast sparse mode with auto rp on
r4 -
> r4 is hub -
>
> r4 - join group 224.8.8.4 r6 join group 224.8.8.6, r3 join group
224.8.8.6
>
> r5 - join group 224.8.8.5
>
>
> I would like to make r3 be able to ping all groups except 224.8.8.5
>
> How should this be done....
>
> Thanks,
>
> Lou
> **Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:44 GMT-3