| ICMPv6 (Internet Control Message Protocol version 6) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Family: | Internet minutes family | |||||||||||||||||
| Operational area: | Mandatory additive to IPv6, error messages, diagnosis, Autoconfiguration, Routing | |||||||||||||||||
| ||||||||||||||||||
| Standard: | RFC 2463 (1998) | |||||||||||||||||
The Internet Control Message Protocol V6 (ICMPv6) is together the version of the Internet Control Message Protocol used with IPv6. It serves, like already with IPv4 in networks for the change of error and information messages. It however still finds additional to the replacement of the Address Resolution Protocol use in the Neighbor Discovery Protocol.
Even if ICMPv6 on the same network layer is as IPv6, the ICMPv6 message before dispatching is packed up in IPv6-Pakete and sent away in such a way. As minutes number 58 in the NEXT header field of the IPv6-headers is inserted.
colspan= " 1 " |0 | Type | Code | Check sum | |||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
colspan= " 1 " |" | ICMPv6 message" | |||||||||||||||||||||||||||||||
The field type gives to be specified the class of the ICMP message to which with the field code more exactly can. The check sum is used for examining the validity of the ICMPv6-Pakets. Remaining contents of the ICMP message are determined by the respective type. With error messages after the possible additional fields still as much is attached as possible by the error-causing package.
The message types are divided into two groups. The first 128 types (0-127), with the Most Significant bit on 0, are error messages. The second 128 types (128-255), with the Most Significant bit on 1, are information messages.
{|| style= " vertical align: top; "|
| Type | Description | RFC |
|---|---|---|
| 1 | Destination Unreachable | RFC 2463 |
| 2 | Pack Too Big | RFC 2463 |
| 3 | Time Exceeded | RFC 2463 |
| 4 | Parameter problem | RFC 2463 |
| 100 | Private one experimentation | |
| 101 | Private one experimentation |
|
| Type | Description | RFC |
|---|---|---|
| 128 | Echo Request | RFC 2463 |
| 129 | Echo Reply | RFC 2463 |
| 130 | Multicast Listener Query | |
| 131 | Multicast Listener report | |
| 132 | Multicast Listener Done | |
| 133 | Rout Solicitation | RFC 2461 |
| 134 | Rout Advertisement | RFC 2461 |
| 135 | Neighbor Solicitation | RFC 2461 |
| 136 | Neighbor Advertisement | RFC 2461 |
| 137 | Redirect | RFC 2461 |
| 138 | Rout Renumbering | |
| 139 | ICMP Node information Query | |
| 140 | ICMP Node information Response | |
| 141 | Inverse Neighbor Discovery Solicitation Message | RFC 3122 |
| 142 | Inverse Neighbor Discovery Advertisement Message | RFC 3122 |
| 143 | Version 2 multicast Listener report | |
| 144 | Home agent ADDRESS Discovery Request Message | RFC 3775 |
| 145 | Home agent ADDRESS Discovery Reply Message | RFC 3775 |
| 146 | Mobile Prefix Solicitation | RFC 3775 |
| 147 | Mobile Prefix Advertisement | RFC 3775 |
| 148 | Certification Path Solicitation Message | RFC 3971 |
| 149 | Certification Path Advertisement Message | RFC 3971 |
| 150 | ICMP of messages utilized by experimental mobility protocols look for as Seamoby | RFC 4065 |
| 151 | Multicast rout Advertisement | |
| 152 | Multicast rout Solicitation | |
| 153 | Multicast rout Termination | |
| 200 | Private one experimentation | |
| 201 | Private one experimentation | |
| 255 | Reserved for expansion OF ICMPv6 informational messages |
|}
| 0 | IPv6 sender address | |||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 32 | IPv6 a goal address | |||||||||||||||||||||||||||||||
| 64 | IPv6 pay load size | |||||||||||||||||||||||||||||||
| 96 | Check sum 0 | NEXT header 58. | ||||||||||||||||||||||||||||||
The check sum of a ICMPv6-Pakets is a 16Bit complement-on-one of the sum of the complement-on-one of the entire ICMPv6-Nachricht. Additionally to the message still another IPv6 pseudo header is in front attached. For the computation of the Chechsumme the check total field is set to 0. The pseudo header used for the computation of the check sum looks as next door in the pattern.
This is one of the innovations of ICMPv6 opposite ICMP, where the check sum was computed only over the ICMP headers.
To the processing of ICMPv6-Nachrichten the following rules apply.
We found here 28 articles.
We found here 6 related websites.
Index | Privacy | Terms Of Use | Sitemap | Feedback