From: Ashok M A (ashok_ccie@yahoo.co.in)
Date: Tue Oct 11 2005 - 08:10:02 GMT-3
Adding to this, I could see "ip igmp access-group" has
effect only if it is configured on the router where
the hosts directly connected. This has no effect if
configured on other router on the path towards the RP.
I see (*,G) is not filtered if configured on the
router on the path towards the RP.
Corret me if I am missing something.
Thanks & Regards,
Ashok M A
-----Original Message-----
From: nobody@groupstudy.com
[mailto:nobody@groupstudy.com] On Behalf Of simon hart
Sent: Thursday, September 01, 2005 6:44 PM
To: dusth@comcast.net; ccielab@groupstudy.com
Subject: RE: ip multicast boundary vs. ip igmp
access-group
Dustin,
The difference between the two commands are:
ip multicast boundary - this will prevent mulicast
traffic within the specified access list from
transiting the interface, thus blocking the defined
traffic.
ip igmp access-group - this will prevent hosts within
the attached subnet from joining multicast groups
identified within the associated access list.
This command does not stop the multicast traffic from
transiting the interface (ie to a PIM neighbor), just
stops the hosts from joining.
HTH
Simon
-----Original Message-----
From: nobody@groupstudy.com
[mailto:nobody@groupstudy.com]On Behalf Of
dusth@comcast.net
Sent: 01 September 2005 13:43
To: ccielab@groupstudy.com
Subject: ip multicast boundary vs. ip igmp
access-group
Hello group,
I'm confused the difference between < ip multicast
boundary vs. ip igmp
access-group>. I do not know exactly when to use one
or the other. Is
access-group><ip
mulitcast boundary> command used when filter out only
one single multicast stream? In contrast, is <ip igmp
access-group> command used when need to filter a
range of multicast stream?
Please help.
Thanks,
Dustin
This archive was generated by hypermail 2.1.4 : Sun Nov 06 2005 - 22:00:50 GMT-3