
- •For Web Developers
- •Contents at a Glance
- •Table of Contents
- •List of Figures
- •List of Tables
- •Foreword
- •Why Does Microsoft Care About IPv6?
- •Preface
- •Acknowledgments
- •Introduction
- •Who Should Read This Book
- •What You Should Know Before Reading This Book
- •Organization of This Book
- •Appendices of This Book
- •About the Companion CD-ROM
- •System Requirements
- •IPv6 Protocol and Windows Product Versions
- •A Special Note to Teachers and Instructors
- •Disclaimers and Support
- •Technical Support
- •Limitations of IPv4
- •Consequences of the Limited IPv4 Address Space
- •Features of IPv6
- •New Header Format
- •Large Address Space
- •Stateless and Stateful Address Configuration
- •IPsec Header Support Required
- •Better Support for Prioritized Delivery
- •New Protocol for Neighboring Node Interaction
- •Extensibility
- •Comparison of IPv4 and IPv6
- •IPv6 Terminology
- •The Case for IPv6 Deployment
- •IPv6 Solves the Address Depletion Problem
- •IPv6 Solves the Disjoint Address Space Problem
- •IPv6 Solves the International Address Allocation Problem
- •IPv6 Restores End-to-End Communication
- •IPv6 Uses Scoped Addresses and Address Selection
- •IPv6 Has More Efficient Forwarding
- •IPv6 Has Support for Security and Mobility
- •Testing for Understanding
- •Architecture of the IPv6 Protocol for Windows Server 2008 and Windows Vista
- •Features of the IPv6 Protocol for Windows Server 2008 and Windows Vista
- •Installed, Enabled, and Preferred by Default
- •Basic IPv6 Stack Support
- •IPv6 Stack Enhancements
- •GUI and Command-Line Configuration
- •Integrated IPsec Support
- •Windows Firewall Support
- •Temporary Addresses
- •Random Interface IDs
- •DNS Support
- •Source and Destination Address Selection
- •Support for ipv6-literal.net Names
- •LLMNR
- •PNRP
- •Literal IPv6 Addresses in URLs
- •Static Routing
- •IPv6 over PPP
- •DHCPv6
- •ISATAP
- •Teredo
- •PortProxy
- •Application Support
- •Application Programming Interfaces
- •Windows Sockets
- •Winsock Kernel
- •Remote Procedure Call
- •IP Helper
- •Win32 Internet Extensions
- •Windows Filtering Platform
- •Manually Configuring the IPv6 Protocol
- •Configuring IPv6 Through the Properties of Internet Protocol Version 6 (TCP/IPv6)
- •Configuring IPv6 with the Netsh.exe Tool
- •Disabling IPv6
- •IPv6-Enabled Tools
- •Ipconfig
- •Route
- •Ping
- •Tracert
- •Pathping
- •Netstat
- •Displaying IPv6 Configuration with Netsh
- •Netsh interface ipv6 show interface
- •Netsh interface ipv6 show address
- •Netsh interface ipv6 show route
- •Netsh interface ipv6 show neighbors
- •Netsh interface ipv6 show destinationcache
- •References
- •Testing for Understanding
- •The IPv6 Address Space
- •IPv6 Address Syntax
- •Compressing Zeros
- •IPv6 Prefixes
- •Types of IPv6 Addresses
- •Unicast IPv6 Addresses
- •Global Unicast Addresses
- •Topologies Within Global Addresses
- •Local-Use Unicast Addresses
- •Unique Local Addresses
- •Special IPv6 Addresses
- •Transition Addresses
- •Multicast IPv6 Addresses
- •Solicited-Node Address
- •Mapping IPv6 Multicast Addresses to Ethernet Addresses
- •Anycast IPv6 Addresses
- •Subnet-Router Anycast Address
- •IPv6 Addresses for a Host
- •IPv6 Addresses for a Router
- •Subnetting the IPv6 Address Space
- •Step 1: Determining the Number of Subnetting Bits
- •Step 2: Enumerating Subnetted Address Prefixes
- •IPv6 Interface Identifiers
- •EUI-64 Address-Based Interface Identifiers
- •Temporary Address Interface Identifiers
- •IPv4 Addresses and IPv6 Equivalents
- •References
- •Testing for Understanding
- •Structure of an IPv6 Packet
- •IPv4 Header
- •IPv6 Header
- •Values of the Next Header Field
- •Comparing the IPv4 and IPv6 Headers
- •IPv6 Extension Headers
- •Extension Headers Order
- •Hop-by-Hop Options Header
- •Destination Options Header
- •Routing Header
- •Fragment Header
- •Authentication Header
- •Encapsulating Security Payload Header and Trailer
- •Upper-Layer Checksums
- •References
- •Testing for Understanding
- •ICMPv6 Overview
- •Types of ICMPv6 Messages
- •ICMPv6 Header
- •ICMPv6 Error Messages
- •Destination Unreachable
- •Packet Too Big
- •Time Exceeded
- •Parameter Problem
- •ICMPv6 Informational Messages
- •Echo Request
- •Echo Reply
- •Comparing ICMPv4 and ICMPv6 Messages
- •Path MTU Discovery
- •Changes in PMTU
- •References
- •Testing for Understanding
- •Neighbor Discovery Overview
- •Neighbor Discovery Message Format
- •Neighbor Discovery Options
- •Source and Target Link-Layer Address Options
- •Prefix Information Option
- •Redirected Header Option
- •MTU Option
- •Route Information Option
- •Neighbor Discovery Messages
- •Router Solicitation
- •Router Advertisement
- •Neighbor Solicitation
- •Neighbor Advertisement
- •Redirect
- •Summary of Neighbor Discovery Messages and Options
- •Neighbor Discovery Processes
- •Conceptual Host Data Structures
- •Address Resolution
- •Neighbor Unreachability Detection
- •Duplicate Address Detection
- •Router Discovery
- •Redirect Function
- •Host Sending Algorithm
- •References
- •Testing for Understanding
- •MLD and MLDv2 Overview
- •IPv6 Multicast Overview
- •Host Support for Multicast
- •Router Support for Multicast
- •MLD Packet Structure
- •MLD Messages
- •Multicast Listener Query
- •Multicast Listener Report
- •Multicast Listener Done
- •Summary of MLD
- •MLDv2 Packet Structure
- •MLDv2 Messages
- •The Modified Multicast Listener Query
- •MLDv2 Multicast Listener Report
- •Summary of MLDv2
- •MLD and MLDv2 Support in Windows Server 2008 and Windows Vista
- •References
- •Testing for Understanding
- •Address Autoconfiguration Overview
- •Types of Autoconfiguration
- •Autoconfigured Address States
- •Autoconfiguration Process
- •DHCPv6
- •DHCPv6 Messages
- •DHCPv6 Stateful Message Exchange
- •DHCPv6 Stateless Message Exchange
- •DHCPv6 Support in Windows
- •IPv6 Protocol for Windows Server 2008 and Windows Vista Autoconfiguration Specifics
- •Autoconfigured Addresses for the IPv6 Protocol for Windows Server 2008 and Windows Vista
- •References
- •Testing for Understanding
- •Name Resolution for IPv6
- •DNS Enhancements for IPv6
- •LLMNR
- •Source and Destination Address Selection
- •Source Address Selection Algorithm
- •Destination Address Selection Algorithm
- •Example of Using Address Selection
- •Hosts File
- •DNS Resolver
- •DNS Server Service
- •DNS Dynamic Update
- •Source and Destination Address Selection
- •LLMNR Support
- •Support for ipv6-literal.net Names
- •Peer Name Resolution Protocol
- •References
- •Testing for Understanding
- •Routing in IPv6
- •IPv6 Routing Table Entry Types
- •Route Determination Process
- •Strong and Weak Host Behaviors
- •Example IPv6 Routing Table for Windows Server 2008 and Windows Vista
- •End-to-End IPv6 Delivery Process
- •IPv6 on the Sending Host
- •IPv6 on the Router
- •IPv6 on the Destination Host
- •IPv6 Routing Protocols
- •Overview of Dynamic Routing
- •Routing Protocol Technologies
- •Routing Protocols for IPv6
- •Static Routing with the IPv6 Protocol for Windows Server 2008 and Windows Vista
- •Configuring Static Routing with Netsh
- •Configuring Static Routing with Routing and Remote Access
- •Dead Gateway Detection
- •References
- •Testing for Understanding
- •Overview
- •Node Types
- •IPv6 Transition Addresses
- •Transition Mechanisms
- •Using Both IPv4 and IPv6
- •IPv6-over-IPv4 Tunneling
- •DNS Infrastructure
- •Tunneling Configurations
- •Router-to-Router
- •Host-to-Router and Router-to-Host
- •Host-to-Host
- •Types of Tunnels
- •PortProxy
- •References
- •Testing for Understanding
- •ISATAP Overview
- •ISATAP Tunneling
- •ISATAP Tunneling Example
- •ISATAP Components
- •Router Discovery for ISATAP Hosts
- •Resolving the Name “ISATAP”
- •Using the netsh interface isatap set router Command
- •ISATAP Addressing Example
- •ISATAP Routing
- •ISATAP Communication Examples
- •ISATAP Host to ISATAP Host
- •ISATAP Host to IPv6 Host
- •Configuring an ISATAP Router
- •References
- •Testing for Understanding
- •6to4 Overview
- •6to4 Tunneling
- •6to4 Tunneling Example
- •6to4 Components
- •6to4 Addressing Example
- •6to4 Routing
- •6to4 Support in Windows Server 2008 and Windows Vista
- •6to4 Host/Router Support
- •6to4 Router Support
- •6to4 Communication Examples
- •6to4 Host to 6to4 Host/Router
- •6to4 Host to IPv6 Host
- •Example of Using ISATAP and 6to4 Together
- •Part 1: From ISATAP Host A to 6to4 Router A
- •Part 2: From 6to4 Router A to 6to4 Router B
- •Part 3: From 6to4 Router B to ISATAP Host B
- •References
- •Testing for Understanding
- •Introduction to Teredo
- •Benefits of Using Teredo
- •Teredo Support in Microsoft Windows
- •Teredo and Protection from Unsolicited Incoming IPv6 Traffic
- •Network Address Translators (NATs)
- •Teredo Components
- •Teredo Client
- •Teredo Server
- •Teredo Relay
- •Teredo Host-Specific Relay
- •The Teredo Client and Host-Specific Relay in Windows
- •Teredo Addresses
- •Teredo Packet Formats
- •Teredo Data Packet Format
- •Teredo Bubble Packets
- •Teredo Indicators
- •Teredo Routing
- •Routing for the Teredo Client in Windows
- •Teredo Processes
- •Initial Configuration for Teredo Clients
- •Maintaining the NAT Mapping
- •Initial Communication Between Teredo Clients on the Same Link
- •Initial Communication Between Teredo Clients in Different Sites
- •Initial Communication from a Teredo Client to a Teredo Host-Specific Relay
- •Initial Communication from a Teredo Host-Specific Relay to a Teredo Client
- •Initial Communication from a Teredo Client to an IPv6-Only Host
- •Initial Communication from an IPv6-Only Host to a Teredo Client
- •References
- •Testing for Understanding
- •IPv6 Security Considerations
- •Authorization for Automatically Assigned Addresses and Configurations
- •Recommendations
- •Protection of IPv6 Packets
- •Recommendations
- •Host Protection from Scanning and Attacks
- •Address Scanning
- •Port Scanning
- •Recommendations
- •Control of What Traffic Is Exchanged with the Internet
- •Recommendations
- •Summary
- •References
- •Testing for Understanding
- •Introduction
- •Planning for IPv6 Deployment
- •Platform Support for IPv6
- •Application Support for IPv6
- •Unicast IPv6 Addressing
- •Tunnel-Based IPv6 Connectivity
- •Native IPv6 Connectivity
- •Name Resolution with DNS
- •DHCPv6
- •Host-Based Security and IPv6 Traffic
- •Prioritized Delivery for IPv6 Traffic
- •Deploying IPv6
- •Set Up an IPv6 Test Network
- •Begin Application Migration
- •Configure DNS Infrastructure to Support AAAA Records and Dynamic Updates
- •Deploy a Tunneled IPv6 Infrastructure with ISATAP
- •Upgrade IPv4-Only Hosts to IPv6/IPv4 Hosts
- •Begin Deploying a Native IPv6 Infrastructure
- •Connect Portions of Your Intranet over the IPv4 Internet
- •Connect Portions of Your Intranet over the IPv6 Internet
- •Summary
- •References
- •Testing for Understanding
- •Basic Structure of IPv6 Packets
- •LAN Media
- •Ethernet: Ethernet II
- •Ethernet: IEEE 802.3 SNAP
- •Token Ring: IEEE 802.5 SNAP
- •FDDI
- •IEEE 802.11
- •WAN Media
- •Frame Relay
- •ATM: Null Encapsulation
- •ATM: SNAP Encapsulation
- •IPv6 over IPv4
- •References
- •Added Constants
- •Address Data Structures
- •in6_addr
- •sockaddr_in6
- •sockaddr_storage
- •Wildcard Addresses
- •in6addr_loopback and IN6ADDR_LOOPBACK_INIT
- •Core Sockets Functions
- •Name-to-Address Translation
- •Address-to-Name Translation
- •Using getaddrinfo
- •Address Conversion Functions
- •Socket Options
- •New Macros
- •References
- •General
- •Addressing
- •Applications
- •Sockets API
- •Transport Layer
- •Internet Layer
- •Network Layer Security
- •Link Layer
- •Routing
- •IPv6 Transition Technologies
- •Chapter 1: Introduction to IPv6
- •Chapter 2: IPv6 Protocol for Windows Server 2008 and Windows Vista
- •Chapter 3: IPv6 Addressing
- •Chapter 4: The IPv6 Header
- •Chapter 5: ICMPv6
- •Chapter 6: Neighbor Discovery
- •Chapter 8: Address Autoconfiguration
- •Chapter 9: IPv6 and Name Resolution
- •Chapter 10: IPv6 Routing
- •Chapter 11: IPv6 Transition Technologies
- •Chapter 12: ISATAP
- •Chapter 13: 6to4
- •Chapter 14: Teredo
- •Chapter 15: IPv6 Security Considerations
- •Chapter 16: Deploying IPv6
- •IPv6 Test Lab Setup
- •CLIENT1
- •ROUTER1
- •ROUTER2
- •CLIENT2
- •IPv6 Test Lab Tasks
- •Performing Link-Local Pings
- •Enabling Native IPv6 Connectivity on Subnet 1
- •Configuring ISATAP
- •Configuring Native IPv6 Connectivity for All Subnets
- •Using Name Resolution
- •Configuring an IPv6-Only Routing Infrastructure
- •Overview
- •Mobile IPv6 Components
- •Mobile IPv6 Transport Layer Transparency
- •Mobile IPv6 Messages and Options
- •Mobility Header and Messages
- •Type 2 Routing Header
- •Home Address Option for the Destination Options Header
- •ICMPv6 Messages for Mobile IPv6
- •Modifications to Neighbor Discovery Messages and Options
- •Mobile IPv6 Data Structures
- •Binding Cache
- •Binding Update List
- •Home Agents List
- •Correspondent Registration
- •Return Routability Procedure
- •Detecting Correspondent Nodes That Are Not Mobile IPv6–Capable
- •Mobile IPv6 Message Exchanges
- •Data Between a Mobile Node and a Correspondent Node
- •Binding Maintenance
- •Home Agent Discovery
- •Mobile Prefix Discovery
- •Mobile IPv6 Processes
- •Attaching to the Home Link
- •Moving from the Home Link to a Foreign Link
- •Moving to a New Foreign Link
- •Returning Home
- •Mobile IPv6 Host Sending Algorithm
- •Mobile IPv6 Host Receiving Algorithm
- •References
- •Glossary
- •Index
- •About the Author
- •System Requirements
140Understanding IPv6, Second Edition
■Prefix Information options When present, Prefix Information options contain the onlink prefixes that are used for address autoconfiguration. The link-local prefix is never sent as a Prefix Information option.
■Advertisement Interval option For more information, see Appendix F.
■Home Agent Information option For more information, see Appendix F.
■Route Information options When present, Route Information options contain routes to add to the local routing table for more efficient host forwarding decisions.
Network Monitor Capture
Here is an example of a Router Advertisement message as displayed by Network Monitor 3.1 (capture 06_02 in the \NetworkMonitorCaptures folder on the companion CD-ROM):
Frame:
+Ethernet: Etype = IPv6
+Ipv6: Next Protocol = ICMPv6, Payload Length = 96 - Icmpv6: Router Advertisement
MessageType: Router Advertisement, 134(0x86)
-RouterAdvertisement: Code: 0 (0x0)
Checksum: 8095 (0x1F9F)
CurHopLimit: 0 (0x0)
-RouterAdvertisementFlag:
M:(0.......) Not managed address configuration
O:(.0......) Not other stateful configuration
A: (..0.....) Not a Mobile IP Home Agent
RouterPreference: (...00...) Medium,0(0x0)
Reserved: (.....000)
RouterLifetime: 0 (0x0)
ReachableTime: 0 (0x0)
RetransTimer: 0 (0x0)
+SourceLinkLayerAddress:
+MTU:
+PrefixInformation:
+PrefixInformation:
Neighbor Solicitation
IPv6 nodes send the Neighbor Solicitation message to discover the link-layer address of an on-link IPv6 node or to confirm a previously determined link-layer address. It typically includes the link-layer address of the sender. Typical Neighbor Solicitation messages are multicast for address resolution and unicast when the reachability of a neighboring node is being verified.
For example, assuming that the local link is Ethernet, in the Ethernet header of the Neighbor Solicitation message, you will find the following settings:
■ The Source Address field is set to the MAC address of the sending network adapter.

Chapter 6 Neighbor Discovery |
141 |
■For a multicast Neighbor Solicitation message, the Destination Address field is set to the Ethernet MAC address that corresponds to the solicited-node address of the target. For a unicast Neighbor Solicitation message, the Destination Address field is set to the unicast MAC address of the neighbor.
In the IPv6 header of the Neighbor Solicitation message, you will find these settings:
■The Source Address field is set to either a unicast IPv6 address assigned to the sending interface or, during duplicate address detection, the unspecified address (::).
■For a multicast Neighbor Solicitation, the Destination Address field is set to the solicitednode address of the target. For a unicast Neighbor Solicitation, the Destination Address field is set to the unicast address of the target.
■The Hop Limit field is set to 255.
Figure 6-14 shows the structure of the Neighbor Solicitation message.
Type
Code
Checksum
Reserved
Target Address
Options
Figure 6-14
= 135 |
= 0 |
• • •
The structure of the Neighbor Solicitation message
The fields in the Neighbor Solicitation message are as follows:
■Type The value of this field is 135.
■Code The value of this field is 0.
■Checksum The value of this field is the ICMPv6 checksum.
■Reserved This is a 32-bit field reserved for future use and set to 0.
■Target Address The Target Address field indicates the IP address of the target. The size of this field is 128 bits.
■Source Link-Layer Address option When present, the Source Link-Layer Address option contains the link-layer address of the sender. For an Ethernet node, the Source Link-Layer Address option contains the Ethernet MAC address of the sending node. The receiving node uses the address in the Source Link-Layer Address option to determine the unicast MAC address of the node to which the corresponding Neighbor Advertisement is sent. During duplicate address detection, when the source IPv6 address is the unspecified address (::), the Source Link-Layer Address option is not included.
142 Understanding IPv6, Second Edition
Network Monitor Capture
Here is an example of a Neighbor Solicitation message as displayed by Network Monitor 3.1 (frame 1 of capture 06_01 in the \NetworkMonitorCaptures folder on the companion CD-ROM):
Frame:
-Ethernet: Etype = IPv6
+DestinationAddress: 3333FF 026EA5
+SourceAddress: 00105A AA20A2 EthernetType: IPv6, 34525(0x86dd)
-Ipv6: Next Protocol = ICMPv6, Payload Length = 32
+Versions: IPv6, Internet Protocol, DSCP 0 PayloadLength: 32 (0x20)
NextProtocol: ICMPv6, 58(0x3a) HopLimit: 255 (0xFF)
SourceAddress: FE80:0:0:0:210:5AFF:FEAA:20A2 DestinationAddress: FF02:0:0:0:0:1:FF02:6EA5
-Icmpv6: Neighbor Solicitation, Target = FE80:0:0:0:260:97FF:FE02:6EA5
MessageType: Neighbor Solicitation, 135(0x87)
-NeighborSolicitation: Code: 0 (0x0) Checksum: 3893 (0xF35) Reserved: 0 (0x0)
TargetAddress: FE80:0:0:0:260:97FF:FE02:6EA5
-SourceLinkLayerAddress:
Type: Source Link-Layer Address, 1(0x1)
Length: 1, in unit of 8 octets
Address: 00-10-5A-AA-20-A2
Notice how the last 24 bits of the target address (FE80::260:97FF:FE02:6EA5) correspond to the last 24 bits of the solicited-node destination address (FF02::1:FF02:6EA5) (corresponding bits underlined). Also notice how the last 32 bits of the solicited-node destination address (FF02::1:FF02:6EA5) correspond to the last 32 bits of the Ethernet destination address (3333FF026EA5) (corresponding bits underlined).
Neighbor Advertisement
An IPv6 node sends the Neighbor Advertisement message in response to a Neighbor Solicitation message. An IPv6 node also sends unsolicited Neighbor Advertisements to inform neighboring nodes of changes in link-layer addresses or the node’s role. The Neighbor Advertisement contains information required by nodes to determine the type of Neighbor Advertisement message, the sender’s role on the network, and typically the link-layer address of the sender.
For example, assuming that the local link is Ethernet, in the Ethernet header of the Neighbor Advertisement message, you will find the following settings:
■The Source Address field is set to the MAC address of the sending network adapter.
■The Destination Address field is set, for a solicited Neighbor Advertisement, to the unicast MAC address of the initial Neighbor Solicitation sender. For an unsolicited Neighbor

Chapter 6 Neighbor Discovery |
143 |
Advertisement, the Destination Address field is set to 33-33-00-00-00-01, which is the Ethernet MAC address corresponding to the link-local scope all-nodes multicast address.
In the IPv6 header of the Neighbor Advertisement message, you will find these settings:
■The Source Address field is set to a unicast address assigned to the sending interface.
■The Destination Address field is set, for a solicited Neighbor Advertisement, to the unicast IP address of the sender of the initial Neighbor Solicitation. For an unsolicited Neighbor Advertisement, the Destination Address field is set to the link-local scope all-nodes multicast address (FF02::1).
■The Hop Limit field is set to 255.
Figure 6-15 shows the structure of the Neighbor Advertisement message.
Type |
= 136 |
Code |
= 0 |
Checksum |
|
Router Flag |
|
Solicited Flag |
|
Override Flag |
|
Reserved |
|
Target Address |
|
Options |
• • • |
|
Figure 6-15 The structure of the Neighbor Advertisement message
The following list describes the fields in the Neighbor Advertisement message:
■Type The value of this field is 136.
■Code The value of this field is 0.
■Checksum The value of this field is the ICMPv6 checksum.
■Router flag The Router flag indicates the role of the sender of the Neighbor Advertisement message. The size of this field is 1 bit. The Router flag is set to 1 when the sender is a router and 0 when the sender is not. The Router flag is used by the neighbor unreachability detection process to determine when a router changes to a host.
■Solicited flag The Solicited flag indicates, when set to 1, that the Neighbor Advertisement message was sent in response to a Neighbor Solicitation message. The size of this field is 1 bit. The Solicited flag is used as a reachability confirmation during neighbor unreachability detection. The Solicited flag is set to 0 for both multicast Neighbor Advertisements and unsolicited unicast Neighbor Advertisements.
■Override flag The Override flag indicates, when set to 1, that the link-layer address in the included Target Link-Layer Address option should override the link-layer address
144 Understanding IPv6, Second Edition
in the existing neighbor cache entry. The size of this field is 1 bit. If the Override flag is set to 0, the enclosed link-layer address updates a neighbor cache entry only if the link-layer address is not known. The Override flag is set to 0 for a solicited anycast address or a proxied advertisement. The Override flag is set to 1 in other solicited and unsolicited advertisements. For more information about the neighbor cache, see the “Neighbor Discovery Processes” section in this chapter.
■Reserved This is a 29-bit field reserved for future use and set to 0.
■Target Address The Target Address field indicates the address being advertised. The size of this field is 128 bits. For solicited Neighbor Advertisement messages, the target address is set to the value of the Target Address field in the corresponding Neighbor Solicitation. For unsolicited Neighbor Advertisement messages, the target address is the address whose link-layer address or role has changed.
■Target Link-Layer Address option When present, the Target Link-Layer Address option contains the link-layer address of the target, which is the sender of the Neighbor Advertisement. For an Ethernet node, the Target Link-Layer Address option contains the Ethernet MAC address of the sending node. The address in the Target Link-Layer Address option is used by receiving nodes to determine the unicast MAC address of the advertising node.
Network Monitor Capture
Here is an example of a solicited Neighbor Advertisement message as displayed by Network Monitor 3.1 (frame 2 of capture 06_01 in the \NetworkMonitorCaptures folder on the companion CD-ROM):
Frame:
+ Ethernet: Etype = IPv6
-Ipv6: Next Protocol = ICMPv6, Payload Length = 32
+Versions: IPv6, Internet Protocol, DSCP 0 PayloadLength: 32 (0x20)
NextProtocol: ICMPv6, 58(0x3a) HopLimit: 255 (0xFF)
SourceAddress: FE80:0:0:0:260:97FF:FE02:6EA5 DestinationAddress: FE80:0:0:0:210:5AFF:FEAA:20A2
-Icmpv6: Neighbor Advertisement, Target = FE80:0:0:0:260:97FF:FE02:6EA5
MessageType: Neighbor Advertisement, 136(0x88)
-NeighborAdvertisement: Code: 0 (0x0)
Checksum: 35244 (0x89AC)
-NeighborAdvertisementFlag: 1610612736 (0x60000000)
R:(0...............................) Not router
S:(.1..............................) Solicited
O: |
(..1 |
.............................) |
Override |
Rsv: |
(... |
00000000000000000000000000000) |
|
TargetAddress: FE80:0:0:0:260:97FF:FE02:6EA5
+ TargetLinkLayerAddress: