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  TCP/IP Routing Protocols (Gateway Protocols)                 9  TCP/IP Interior Routing Protocols (RIP, OSPF, GGP, HELLO, IGRP, EIGRP)                      9  TCP/IP Routing Information Protocol (RIP, RIP-2 and RIPng)                           9  RIP Version-Specific Message Formats and Features

RIP Version-Specific Message Formats and Features 1 2 3 RIP Version 2 (RIP-2) Message Format and Features

RIP evolved as an industry standard and was popularized by its inclusion in the Berkeley Standard Distribution of UNIX (BSD UNIX). This first version of RIP (now sometimes called RIP-1 to differentiate it from later versions), was eventually standardized in RFC 1058. As part of this standard the original RIP-1 message format was defined, which of course serves RIP-1 itself, and is also the basis for the format used in later versions.

As explained in the general discussion on RIP operation, route information is exchanged in RIP through the sending of two different types of RIP messages: RIP Request and the RIP Response. These are transmitted as regular TCP/IP messages using the User Datagram Protocol (UDP), using UDP reserved port number 520. This port number is used as follows:

• RIP Request messages are sent to UDP destination port 520. They may have a source port of 520 or may use an ephemeral port number.
  
  
• RIP Response messages sent in reply to an RIP Request are sent with a source port of 520, and a destination port equal to whatever source port the RIP Request used.
  
  
• Unsolicited RIP Response messages (sent on a routine basis and not in response to a request) are sent with both the source and destination ports set to 520.

RIP Version-Specific Message Formats and Features 1 2 3 RIP Version 2 (RIP-2) Message Format and Features