Radware Alteon, Инструкция по применению

Страница: 835 / 842

Document ID: RDWR-ALOS-V2900_AG1302
835
Appendix C – IPv6
This appendix describes the basic configuration and management of IPv6. For IPv6 implementation
with specific Alteon features, refer to the appropriate chapters for details on the level of support.
This appendix includes the following topics:
• IPv4 versus IPv6, page 835
• IPv6 Address Format, page 836
• IPv6 Address Types, page 837
• Pinging IPv6 Addresses, page 837
• Verifying an IPv6 Configuration, page 838
• Verifying IPv6 Statistics, page 838
IPv4 versus IPv6
Internet Protocol version 6 (IPv6) is a network layer protocol for packet-switched internetworks. It is
designated as the successor of IPv4, the current version of the Internet Protocol, for general use on
the Internet.
The main improvement brought by IPv6 is the increase in the number of addresses available for
networked devices, allowing, for example, each cell phone and mobile electronic device to have its
own address. IPv4 supports 232 (about 4.3 billion) addresses, which is inadequate for giving even
one address to every living person, let alone supporting embedded and portable devices. IPv6,
however, supports 2128 addresses; this is approximately 5 × 1028 addresses for each of the
roughly 6.5 billion people alive today.
Table 71 includes a summary of the key differences between IPv4 and IPv6 protocols:
Table 71: Differences Between IPv4 and IPv6 Protocols
IPv4 IPv6
Source and destination addresses are 32 bits
(4 bytes) in length. Source and destination addresses are 128 bits (16
bytes) in length.
IPSec support is optional. IPSec support is required.
No identification of packet flow for QoS
handling by routers is present within IPv4. Packet flow identification for QoS handling by
routers is present within the IPv6 header using the
Flow Label field.
Fragmentation is performed by the sending
host, and at the routers, thus slowing
performance. Fragmentation is performed only by the sending
host.
No link-layer packet size requirements and
has to reassemble 576-byte packet. Link layer must support 1,280 byte packet and rea
sse mb el a 1,500 byte packet.
Header includes a checksum. Header does not include a checksum.
Header includes options. All optional data is moved to IPv6 extension
headers.
ARP uses Broadcast ARP Request frames to
resolve an IPv4 address to a link layer
address. ARP Request frames are replaced with multicast
Neighbor Solicitation (Discovery) messages.
IGMP is used to manage local subnet group
membership. IGMP is replaced with Multicast Listener Discovery
(MLD) messages.