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 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  Internet Control Message Protocol (ICMP/ICMPv4 and ICMPv6)                 9  ICMP Message Types and Formats                      9  ICMP Version 4 (ICMPv4) Informational Message Types and Formats

ICMPv4 Timestamp (Request) and Timestamp Reply Messages 1 2 3 4 ICMPv4 Address Mask Request and Reply Messages

In the overview topic describing IP routing fundamentals, I discussed a critical aspect of IP internetwork design: the difference between the roles of a router and that of a host with regard to routing. Routers are charged with the job of routing datagrams, and therefore, of knowing routes and exchanging route information. Hosts generally do not know a great deal about routes; they rely on routers to convey datagrams intended for destinations outside the local network.

This dependence means that before a host can really participate on an internetwork, it needs to know the identity of at least one router on the local network. One way to ensure that this is the case is to just manually configure each host with the address of a local router as its default router. This method is simple, but has the typical drawbacks associated with manual processes—it is time-consuming to set up, difficult to maintain, and inflexible.

It would be better if there were some method whereby a host could automatically discover the identity of local routers, and learn important information about them. In IP, this process is called router discovery, and was first defined in RFC 1256, ICMP Router Discovery Messages. The messages referenced in the RFC title are the ICMP Router Advertisement message and the Router Solicitation message, and were added to the ICMP message types defined in earlier standards such as RFC 792.

Routers are responsible for sending Router Advertisement messages. These messages tell listening devices that the router exists, and provide important information about the router such as its address (or addresses, if it has more than one) and how long the host should retain information about the router. Routine Router Advertisement messages are sent on a regular basis, with the time between messages administrator-configurable (usually between 7 and 10 minutes). Hosts listen for these messages; when an advertisement is received, the host processes it and adds the information about the router to its routing table.

A host that has no manually-configured routing information will have no knowledge of routers when it first powers on. Having it sit for many minutes looking for a routine Router Advertisement message is inefficient. Instead of waiting, the host may send a Router Solicitation message on its local network(s). This will prompt any router that hears it to immediately send out an extra Router Advertisement message directly to that host.

ICMPv4 Timestamp (Request) and Timestamp Reply Messages 1 2 3 4 ICMPv4 Address Mask Request and Reply Messages