Добавил:
Upload Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
Скачиваний:
51
Добавлен:
11.04.2015
Размер:
22.9 Mб
Скачать

116 Understanding IPv6, Second Edition

ICMPv6 Informational Messages

The ICMPv6 informational messages defined in RFC 4443 provide a simple diagnostic capability to aid in troubleshooting and consist of the following messages:

Echo Request (ICMPv6 Type 128)

Echo Reply (ICMPv6 Type 129)

Additional ICMPv6 informational messages are used for ND and MLD. For more information, see Chapter 6 and Chapter 7.

Echo Request

An IPv6 node sends an ICMPv6 Echo Request message to a destination to solicit an immediate Echo Reply message. The Echo Request/Echo Reply message facility provides a simple diagnostic function to aid in the troubleshooting of a variety of reachability and routing problems. Figure 5-6 shows the structure of the Echo Request message.

Type

 

= 128

 

 

Code

 

= 0

 

 

 

 

Checksum

 

 

 

 

 

 

Identifier

 

 

 

 

 

 

Sequence Number

 

 

 

 

 

 

Data

 

 

• • •

 

 

 

 

 

 

Figure 5-6 The structure of the Echo Request message

In the Echo Request message, the Type field is set to 128 and the Code field is set to 0. Following the Checksum field are the 16-bit Identifier and 16-bit Sequence Number fields. The Identifier and Sequence Number fields are set by the sending host so that they can be used to match an incoming Echo Reply message with a sent Echo Request message. The Data field is zero or more bytes of optional data that is also set by the sending host.

Network Monitor Capture

Here is an example of an Echo Request message as displayed by Network Monitor 3.1 (frame 1 of capture 05_03 in the \NetworkMonitorCaptures folder on the companion CD-ROM):

Frame:

+ Ethernet: Etype = IPv6

-Ipv6: Next Protocol = ICMPv6, Payload Length = 40

+Versions: IPv6, Internet Protocol, DSCP 0 PayloadLength: 40 (0x28)

NextProtocol: ICMPv6, 58(0x3a) HopLimit: 128 (0x80)

SourceAddress: FE80:0:0:0:260:97FF:FE02:6E8F DestinationAddress: FE80:0:0:0:260:97FF:FE02:6D3D

Chapter 5 ICMPv6

117

- Icmpv6: Echo request, ID = 0x0, Seq = 0x18 MessageType: Echo request, 128(0x80)

-EchoRequest: Code: 0 (0x0)

Checksum: 52045 (0xCB4D) Identifier: 0 (0x0) SequenceNumber: 24 (0x18)

EchoData: Binary Large Object (32 Bytes)

Echo Reply

An IPv6 node sends an ICMPv6 Echo Reply message in response to the receipt of an ICMPv6 Echo Request message. Figure 5-7 shows the structure of the Echo Reply message.

Type = 129

Code = 0

Checksum

Identifier

Sequence Number

Data

• • •

Figure 5-7 The structure of the Echo Reply message

In the Echo Reply message, the Type field is set to 129 and the Code field is set to 0. Following the Checksum field are the 16-bit Identifier and 16-bit Sequence Number fields. The Identifier, Sequence Number, and Data fields are set with the same values as those in the Echo Request message that prompted the Echo Reply.

Echo Request messages can be sent to a multicast address. As specified in RFC 4443, an Echo Request message sent to a multicast address should be answered with an Echo Reply message, sent from a unicast address assigned to the interface on which the Echo Request was received. The IPv6 protocol for Windows Vista and Windows Server 2008 does not respond to multicast Echo Request messages.

Network Monitor Capture

Here is an example of an Echo Reply message as displayed by Network Monitor 3.1 (frame 2 of capture 05_03 in the \NetworkMonitorCaptures folder on the companion CD-ROM):

Frame:

+ Ethernet: Etype = IPv6

-Ipv6: Next Protocol = ICMPv6, Payload Length = 40

+Versions: IPv6, Internet Protocol, DSCP 0 PayloadLength: 40 (0x28)

NextProtocol: ICMPv6, 58(0x3a) HopLimit: 128 (0x80)

SourceAddress: FE80:0:0:0:260:97FF:FE02:6D3D DestinationAddress: FE80:0:0:0:260:97FF:FE02:6E8F

Соседние файлы в папке Lecture 2_10