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.

The Book is Here... and Now On Sale!

Read offline with no ads or diagram watermarks!
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Lower-Layer (Interface, Internet and Transport) Protocols (OSI Layers 2, 3 and 4)
      9  TCP/IP Internet Layer (OSI Network Layer) Protocols
           9  TCP/IP IPv6 Neighbor Discovery Protocol (ND)

Previous Topic/Section
IPv6 ND Host-Host Communication Functions: Address Resolution, Next-Hop Determination, Neighbor Unreachability Detection and Duplicate Address Detection
Previous Page
Pages in Current Topic/Section
1
Next Page
TCP/IP Routing Protocols (Gateway Protocols)
Next Topic/Section

IPv6 ND Redirect Function

The last of the major responsibilities of the IPv6 Neighbor Discovery protocol is the redirect function. This is used by a router to inform a host of a better route to use for datagrams sent to a particular destination. An argument could be made that the redirect function should be part of the host-router group since it represents a form of communication between routers and regular hosts. However, it is somewhat different from the other “discovery” functions and so the standard treats it separately.

Routers are responsible for detecting situations where a host on the local network has made an inefficient first-hop routing decision, and then attempting to correct it. For example, consider a network that has two routers on it, R1 and R2. A host H1 wants to send a datagram to device X2 on another network that is connected to H1's network through router R2. If H1 sends the datagram to R1, R1 will of course know it has to go through R2 and will send it there. Seeing that R2 was also on the local network, R1 therefore knows that H1 made a poor initial routing decision: the datagram should have been sent to R2 directly, not R1. If this sounds very similar to ICMPv4 redirect feature, that’s because it is.

In response, R1 will create a special Redirect ICMPv6 message. This message will tell H1 that for any subsequent datagrams to be sent to X2 should be first sent to R2 instead of R1. It is also possible that a router may determine other situations where the first hop from a particular host should be different and will advise the host using a Redirect message. This is illustrated in Figure 170.


Figure 170: ND Host Redirection Using an ICMPv6 Redirect Message

H1 sends to R1 an IPv6 datagram destined for a device on network N2. However, R1 notices that R2 is on the same network as the source device and is a more direct route to N2. It forwards the datagram on to R2 but also sends an ICMPv6 Redirect message back to H1 to tell it to use R2 next time.

 


Only routers send Redirect messages, not hosts. Hosts are responsible for looking for these Redirect messages and processing them. A host receiving such a message will look in it to see which destination's datagram led to the redirect, and which new first hop the router is saying the host should use in the future for that destination. In this case, H1 will see that R1 is saying any further datagrams to X2 should be sent to R2 instead of R1. H1 will update its destination cache for X2 accordingly.

Key Concept: The Neighbor Discovery protocol redirect function allows a router to tell a host to use a different router for future transmissions to a particular destination. It is similar to the IPv4 redirect feature and is implemented using ICMPv6 Redirect messages.


When a router sends a Redirect, it may also include in the message the data link layer address of the destination to which it is redirecting. This address is used by the host to update its address resolution cache, if necessary. This may save bandwidth in the future by eliminating an address resolution cycle, when the redirected host tries to send to the new, redirected location. In our example, R1 may include R2’s own layer two address in the redirect. This can be used by H1 the next time it has a datagram for X2.

IPv6 also supports authentication of Redirect messages, to prevent unauthorized devices from causing havoc by sending inappropriate Redirects. A host may be configured to discard Redirects that are not properly authenticated.

 


Previous Topic/Section
IPv6 ND Host-Host Communication Functions: Address Resolution, Next-Hop Determination, Neighbor Unreachability Detection and Duplicate Address Detection
Previous Page
Pages in Current Topic/Section
1
Next Page
TCP/IP Routing Protocols (Gateway Protocols)
Next Topic/Section

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!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



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.