The first one blocks auto-rp and Administratively scoped multicast addresses. The second one only blocks auto-rp.
-Marc On Thu, Jun 16, 2011 at 3:54 PM, Huang, Kevin <[email protected]> wrote: > DSG for Vol1 Lab24 Task24.20 uses the "ip multicast boundary" interface > command w/ a standard ACL applied to it: > > access-list 23 deny 239.0.0.0 0.255.255.255 > access-list 23 deny 224.0.1.39 > access-list 23 deny 224.0.1.40 > access-list 23 permit any > > int gi0/0 > ip multicast boundary 23 > ============ > > DSG for Vol3 Lab4 Task4.1 just applies an extended ACL to the interface: > > ip access-l ext NO-AUTORP > deny ip any host 224.0.1.39 > deny ip any host 224.0.1.40 > permit ip any any > > int s0/1/0 > ip access-group NO-AUTORP in > ip access-group NO-AUTORP out > ============= > > Do both methods pretty much achieve the same goal? > Is there any difference other than the fact that it's more granular w/ an > extended ACL? > > Thx, > Kevin > > ---------------------------------------------------------------------- > CONFIDENTIALITY NOTICE: This email and any files transmitted with it are > confidential and intended solely for the use of the individual or entity to > which they are addressed. If you are not the intended recipient, you may not > review, copy or distribute this message. If you have received this email in > error, please notify the sender immediately and delete the original message. > Neither the sender nor the company for which he or she works accepts any > liability for any damage caused by any virus transmitted by this email. > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
