From: Scott Morris (swm@emanon.com)
Date: Tue Aug 03 2004 - 13:22:00 GMT-3
Nothing is "sourced" from the multicast IP range. So your access-group 10
out won't accomplish much of anything!
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, CISSP,
JNCIP, et al.
IPExpert CCIE Program Manager
IPExpert Sr. Technical Instructor
swm@emanon.com/smorris@ipexpert.net
http://www.ipexpert.net
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ccie2be
Sent: Tuesday, August 03, 2004 10:59 AM
To: Group Study
Subject: Multicast admin boundaries
Hi guys,
Given this acl
access-list 10 deny 239.192.0.0 0.0.255.255 access-list 10 permit any
Now, consider the 2 configs below
int s0
ip multicast boundary 10
versus
int s0
access-group 10 out
What's the difference? The idea is to prevent multicast packets from
traveling too far, but won't either command accomplish the same thing. So,
why do we need a "special" command, ip multicast boundary to simply apply an
acl to an interface?
Thanks, Tim
This archive was generated by hypermail 2.1.4 : Fri Sep 03 2004 - 07:02:31 GMT-3