Please Whitelist This Site?
I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)
If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.
If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.
Thanks for your understanding!
Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide
|
NOTE: Using software to mass-download the site degrades the server and is prohibited. If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.
|
|
|
|
ICMPv6 Destination Unreachable Messages
(Page 3 of 3)
ICMPv6 Destination Unreachable Message Subtypes
There are a number of different reasons
why a destination may be unreachable. To provide additional information
about the nature of the problem to the device that originally tried
to send the datagram, a value is placed in the message's Code
field. One interesting difference between ICMPv4 and ICMPv6 Destination
Unreachable messages is that there are many fewer Code values
for ICMPv6. The ICMPv6 Code values were streamlined,
mainly because several of the ICMPv4 codes were related to relatively
obscure features that aren't applicable to ICMPv6.
Table 103
shows the different Code values, corresponding message subtypes
and a brief explanation of each:
Table 103: ICMPv6 Destination Unreachable Message Subtypes
Code Value
|
Message
Subtype
|
Description
|
0
|
No Route
To Destination
|
The datagram was not delivered
because it could not be routed to the destination. Since this means
the datagram could not be sent to the destination device's local network,
this is basically equivalent to the Network Unreachable
message subtype in ICMPv4.
|
1
|
Communication
With Destination Administratively Prohibited
|
The datagram
could not be forwarded due to filtering that blocks the message based
on its contents. Equivalent to the message subtype with the same name
(and Code value 13) in ICMPv4.
|
3
|
Address Unreachable
|
There was a problem attempting
to deliver the datagram to the host specified in the destination address.
This code is equivalent to the ICMPv4 Host Unreachable code
and usually means the destination address was bad or there was a problem
with resolving it into a layer two address.
|
4
|
Port
Unreachable
|
The destination
port specified in the UDP or TCP header was invalid or does not exist
on the destination host.
|
Note that Code value
2 is not used. Also, Destination Unreachable messages are only
sent when there is a fundamental problem with delivering a particular
datagram; they are not sent when a datagram is dropped simply due to
congestion of a router.
Processing of Destination Unreachable Messages
It is up to the recipient of an ICMPv6
Destination Unreachable message to decide what to do with it.
However, just as the original datagram may not reach its destination,
the same is true of the Destination Unreachable message itself.
Therefore, a device cannot rely on the receipt of one of these error
messages to inform it of every delivery problem. This is especially
true given that it is possible some unreachable destination problems
may not be detectable.
Key Concept: ICMPv6 Destination Unreachable messages are used in the same manner as the ICMPv4 message of that name: to inform a sending device of a failure to deliver an IP datagram. The messages Code field provides information about the nature of the delivery problem (though the Code values are different than they are in ICMPv4.) |
If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support! |
|
|
Home -
Table Of Contents - Contact Us
The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005
© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.
|