Posted:
23 Aug 07
C
C
N
P
B
S
C
I
I
P
v
6
|
IPv6
-
Features
-
Larger address space
-
128 bits
-
Allows large allocations - leads to better summarization
-
Simplified header
-
40 octets (compared to 20)
-
fewer fields - 7 compared to 12
-
next header extension field
-
mobility and security
-
stateless auto-configuration
-
MTU auto-discovery - performed every 5 minutes
-
transition mechanisms
-
Addresses
-
3 main types
-
Unicast
-
Global unicast (or global aggregateable) - 2001::/16 currently
being allocated
-
link-local - FE80::/10
-
identifies a single interface
-
Anycast - delivered to closest interface configured with that
anycast address
-
Multicast
-
No broadcast addresses
-
Each interface has multiple addresses
-
At least one loopback (::1) and one link-local address
-
may also have other global or local addresses
-
Interface identifier (EUI-64 format)
-
based on Layer2 information
-
On Ethernet:
-
Based on MAC address
-
Insert 0xFFFE between upper 3 bytes (OUI) and lower 3 bytes
-
7th bit in high -order byte set to 1 to indicate
uniqueness (Universal/Local bit)
-
Global Unicast Addresses
-
48-bit global routing prefix - Assigned by IANA through local
registries (ex ARIN)
-
16-bit subnet ID - Assigned by organizations to create addressing
hierarchy
-
64-bit interface ID - usually the Interface identifier
-
Link-Local
-
limited scope (local link)
-
dynamically created on all IPv6 interfaces
-
uses FE80::/10 and 64-bit interface ID
-
used for neighbor discovery, auto address configuration, router
discovery, and routing protocols
-
Multicast addresses
-
Subset of global unicast with FF00::/8 prefix
-
second octet defines the lifetime or scope
-
Flag - first nibble
-
Scope - second nibble
-
1 - interfaces
-
2 - link-local
-
3 - subnet-local
-
4 - admin-local
-
5 - site-local
-
8 - Org local
-
E - Global
-
Some Well-known addresses
-
FF02::1 - All nodes on a link
-
FF02::2 - All routers on a link
-
FF02::1:FFXX:XXXX - Solicited-node
-
XX:XXXX is the least significant 24-bits of IP of a node.
-
Used to determine link layer address of solicited node, as
in Ipv4 ARP
-
Stateless Auto-configuration
-
Routers periodically sent “router advertisements†to the “all
nodes†multicast address. Clients can use the router's source
address to determine the link prefix and the router address to use
as a gateway
-
clients can also send a “router solicitation†to the “all routersâ€
multicast ip to request a router solicitation.
-
Hosts combine the link prefix with their 64-bit interface ID to
make a full IP address
-
Header
-
Fields
-
version - 6
-
Traffic class - similar to T0S. Used for QOS.
-
Flow Label
-
new to v6
-
20 bits
-
tagged by source of the packet
-
allows multilayer switches to handle traffic per-flow rather
than per-packet and provides QOS
-
Payload length
-
Next header
-
Similar to Protocol field in v4
-
Points to a transport-layer packet or an extension header
-
Hop limit
-
same as TTL
-
no checksum in v6 header, so routers can decrement hop limit
without recomputing a checksum
-
source address
-
Destination add
-
Extension headers
-
Processed in the order they appear in the packet
-
usually only processed by destination except hop-by-hop header
-
Types
-
Hop-by-hop
-
destination options - used in mobile IPv6
-
Routing header - used for source routing and mobile IPv6
-
Fragment header
-
Authentication header and ESP header
-
Upper-layer header (TCP or UDP)
-
Mobility
-
Normal “home address†maintained while moving
-
“care-of†address bound to home address while moving between mobile
nodes
-
uses IPv6 mobility extension header
-
dynamic home agent address discovery mechanism returns a single reply
to the mobile node. directed broadcast in Ipv4 returns separate
replies from each home agent
-
Transitioning
-
Dual stack
-
node chooses stack based on destination address - prefers IPv6
-
ipv6 unicast-routing global command enables forwarding of IPv6
-
ipv6 address address/prefix-length
[eui-64]
interface command assigns IP
-
Tunneling
-
IPv6 is tunneled over IPv4 using IPv4 protocol 41
-
manual tunnel
-
configure a dual-stack edge router on each end
-
manually build a tunnel with an IPv6 address and “tunnel mode
ipv6ipâ€
-
6to4 tunneling
-
2002::/16 + hex of IPv4 address assigned to edge router
-
routers recognize the meaning of these IP's and automatically
tunnel packets when next hop is IPv4
-
ISATAP - treats IPv4 link as a virtual IPv6 link and maps
addresses between versions
-
Teredo - automatic UDP tunneling technique that claims to be able
to cross NAT
-
IPv4 addresses in IPv6
-
IPv4 Compatible IPv6 addresses
-
embeds IPv4 address in lower 32 bits (::/96) ex -
::192.168.1.1
-
these addresses are deprecated
-
IPv4 mapped IPv6 IP addresses
-
::ffff:0:0/96 w/IPv4 address in lower 32 bits. ex -
::ffff:192.168.1.1
-
represented in either dotted decimal or colon hex notation
-
dual stack nodes sending traffic to IPv4 hosts recognize the
meaning of these addresses and send IPv4 packets (no
encapsulation)
-
Translation
-
NAT-PT can be used to connect an IPv4 network to an IPv6 network
-
Stateless IP/ICMP Translation translates header fields
-
translations can be mapped statically or dynamically using dns and
a DNS-application layer gateway
-
Bump-in-the-API and Bump-in-the-Stack can translate on an IPv6
host for IPv4 upper-layer applications (although this is know to
be unreliable)
-
Routing Protocols
-
Static
-
specify next-hop add using link-local address, not global unicast
-
ipv6 route
prefix/prefix-length global
configuration command
-
RIPng
-
15 hop limit, split-horizon, poison reverse
-
uses link-local addresses as source address
-
multicast add FF02::9 as destination
-
UDP port 521
-
OSPFv3
-
permits multiple sessions per interfaces
-
supports authentication using IPsec within IPv6
-
runs on a link rather than a subnet
-
runs directly over IPv6 rather than TCP
-
uses link-local addresses for protocol communication
-
router ID and area ID remain 32 bits in dotted decimal format
-
header
-
includes Instance ID to support multiple instances per link
-
eliminates authentication fields and relies on IPv6 for
authentication
-
16 bytes vs 24 in v2
-
addresses moved to the payload
-
multicast addresses
-
FF02::5 - all spf routers
-
FF02::6 - All DR's
-
LSA's
-
Types
-
1 - Router-LSA - 0x2001
-
2 - Network-LSA - 0x2002
-
3 - Inter-Area-Prefix-LSA - 0x2003
-
4 - Inter-Area-Router-LSA - 0x2004
-
5 - Autonomous system-external-lsa
-
6 - group-membership-lsa
-
7 - type-7-lsa (nssa)
-
8 - link-lsa
-
9 - intra-area-prefix-lsa
-
characteristics
-
32 bit router ID, area id, and link-state id in dotted
decimal format
-
link-local, area, and AS flood scopes
-
support for forwarding of unknown LSA's based on flood
scope (useful in NSSA)
-
Configuration
-
ipv6 cef global command (recommended)
-
ipv6 router ospf process-id
global command
-
router-id
router-id(required)
-
ipv6 ospf
process-id area
area-id [instance
instance-id]
interface command (not “network x.x.x.x area x.x.x.xâ€)
-
area
area-id range
prefix/prefix-length
router configuration command (summarization)
-
most other commands are the same - just change “ip†to “ipv6â€
-
IS-IS
-
2 new TLV's
-
IPv6 reachability
-
IPv6 interface address
-
EIGRP
-
MP-BGP4
-
includes a new identifier for the IPv6 addresses
-
NEXT_HOP attrib contains a global IPv6 address and also has a
link-local address when there is local link connection between
peers
-
Sources
-
Cisco BSCI Authorized Self-Study Guide
-
Sybex CCNP Complete
-
Wikipedia
-
RFC 4291
-
Cisco BSCI Official Exam Certification Guide
Back to BGP - Up to index - Next to Multicast
| Updated:
23 Aug 07
C
C
N
P
B
S
C
I
I
P
v
6
|