Configuring An Extended Ipv6 Acl - SMC Networks TigerStack II SMC8848M Management Manual

A C
CCESS ONTROL
CLI – This example configures one permit rule for the specific address
2009:DB9:2229::79 and another rule for addresses with the network prefix
2009:DB9:2229:5::/64.
Console(config-std-ipv6-acl)#permit host 2009:DB9:2229::79
Console(config-std-ipv6-acl)#permit 2009:DB9:2229:5::/64
Console(config-std-ipv6-acl)#

Configuring an Extended IPv6 ACL

Command Attributes
• Action – An ACL can contain any combination of permit or deny rules.
• Destination Address Type – Specifies the destination IP address. Use
"Any" to include all possible addresses, or "IPv6-prefix" to specify a
range of addresses. (Options: Any, IPv6-prefix; Default: Any)
• Destination IP Address – The address must be formatted according to
RFC 2373 "IPv6 Addressing Architecture," using 8 colon-separated
16-bit hexadecimal values. One double colon may be used in the address
to indicate the appropriate number of zeros required to fill the undefined
fields. (The switch only checks the first 64 bits of the destination
address.)
• Destination Prefix-Length – A decimal value indicating how many
contiguous bits (from the left) of the address comprise the prefix (i.e., the
network portion of the address).
• Next Header – Identifies the type of header immediately following the
IPv6 header. (Range: 0-255)
Optional internet-layer information is encoded in separate headers that
may be placed between the IPv6 header and the upper-layer header in a
packet. There are a small number of such extension headers, each
identified by a distinct Next Header value. IPv6 supports the values
defined for the IPv4 Protocol field in RFC 1700, and includes these
commonly used headers:
0 : Hop-by-Hop Options
6 : TCP Upper-layer Header
17: UDP Upper-layer Header
7-10
L
ISTS
(RFC 2460)
(RFC 1700)
(RFC 1700)
23-11