![SMC Networks 8926EM Management Manual Download Page 173](http://html1.mh-extra.com/html/smc-networks/8926em/8926em_management-manual_1300724173.webp)
Configuring Access Control Lists
7-9
7
•
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
(RFC 2460)
6 : TCP Upper-layer Header
(RFC 1700)
17: UDP Upper-layer Header
(RFC 1700)
43: Routing
(RFC 2460)
44: Fragment
(RFC 2460)
51: Authentication
(RFC 2402)
50: Encapsulating Security Payload
(RFC 2406)
60: Destination Options
(RFC 2460)
•
DSCP
– DSCP priority level. (Range: 0-63)
•
Flow Label
– A label for packets belonging to a particular traffic “flow” for which
the sender requests special handling by IPv6 routers, such as non-default quality
of service or “real-time” service (see RFC 2460). (Range: 0-16777215)
A flow label is assigned to a flow by the flow's source node. New flow labels must
be chosen pseudo-randomly and uniformly from the range 1 to FFFFF
hexadecimal. The purpose of the random allocation is to make any set of bits within
the Flow Label field suitable for use as a hash key by routers, for looking up the
state associated with the flow.
A flow identifies a sequence of packets sent from a particular source to a particular
(unicast or multicast) destination for which the source desires special handling by
the intervening routers. The nature of that special handling might be conveyed to
the routers by a control protocol, such as a resource reservation protocol, or by
information within the flow's packets themselves, e.g., in a hop-by-hop option. A
flow is uniquely identified by the combination of a source address and a non-zero
flow label. Packets that do not belong to a flow carry a flow label of zero.
Hosts or routers that do not support the functions specified by the flow label must
set the field to zero when originating a packet, pass the field on unchanged when
forwarding a packet, and ignore the field when receiving a packet.
Summary of Contents for 8926EM
Page 6: ...ii ...
Page 34: ...Getting Started ...
Page 44: ...Introduction 1 10 1 ...
Page 62: ...Initial Configuration 2 18 2 ...
Page 64: ...Switch Management ...
Page 76: ...Configuring the Switch 3 12 3 ...
Page 118: ...Basic Management Tasks 4 42 4 ...
Page 164: ...User Authentication 6 28 6 ...
Page 176: ...Access Control Lists 7 12 7 ...
Page 284: ...Quality of Service 14 8 14 ...
Page 294: ...Multicast Filtering 15 10 15 ...
Page 300: ...Domain Name Service 16 6 16 ...
Page 310: ...Dynamic Host Configuration Protocol 17 10 17 ...
Page 320: ...Configuring Router Redundancy 18 10 18 ...
Page 344: ...IP Routing 19 24 19 ...
Page 356: ...Unicast Routing 20 12 20 Web Click Routing Protocol RIP Statistics Figure 20 5 RIP Statistics ...
Page 386: ...Unicast Routing 20 42 20 ...
Page 388: ...Command Line Interface ...
Page 400: ...Overview of the Command Line Interface 21 12 21 ...
Page 466: ...SNMP Commands 24 16 24 ...
Page 520: ...Access Control List Commands 26 18 26 ...
Page 546: ...Rate Limit Commands 30 2 30 ...
Page 612: ...VLAN Commands 34 24 34 ...
Page 626: ...Class of Service Commands 35 14 35 ...
Page 670: ...DHCP Commands 39 16 39 ...
Page 716: ...IP Interface Commands 41 36 41 ...
Page 768: ...IP Routing Commands 42 52 42 ...
Page 770: ...Appendices ...
Page 791: ......