From: marvin greenlee (marvin@ccbootcamp.com)
Date: Wed Mar 09 2005 - 20:27:10 GMT-3
Link local addressing is per link. The link local address of R3 means
nothing to R1, because R1 is on a different link. Whether you need site
local or global depends on what addressing you have configured on R3. Does
R3 have a site-local address?
Marvin Greenlee, CCIE#12237, CCSI# 30483
Network Learning Inc
marvin@ccbootcamp.com
www.ccbootcamp.com (Cisco Training)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ccie2be
Sent: Wednesday, March 09, 2005 3:16 PM
To: Group Study
Subject: ipv6 acl's [bcc][faked-from][bayes]
Importance: Low
Hi guys,
When an ipv6 acl is being configured, which type of ipv6 address should be
used: global, link-local, site-local?
I'm sure the answer depends but can someone explain how I should think about
this so I know how to go about this.
Assume this topology:
/-> r3
r1 --> r2
\--> r4
For example, suppose I need to block all ipv6 traffic at r2 coming from r1
and going to r3.
r2 is connected to r3 and r4 via a p2m f/r interface. I want to place the
acl on r2's interface connected to r1.
So, the acl will filter based on destination ipv6 address. Which type ipv6
address should be in the acl?
Does it matter?
Note that r3 interface has 2 types of ipv6 address: a link-local and a
global.
Thanks, Tim
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:44 GMT-3