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". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||^$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!

Get The TCP/IP Guide for your own computer.
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 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 Fundamentals and General Operation

Previous Topic/Section
RIP Protocol Limitations and Problems
Previous Page
Pages in Current Topic/Section
Next Page
RIP Version-Specific Message Formats and Features
Next Topic/Section

RIP Special Features For Resolving RIP Algorithm Problems
(Page 1 of 4)

The simplicity of the Routing Information Protocol is its most attractive quality, but also leads to certain problems with how it operates. Most of these limitations are related to the basic algorithm used for determining routes, and the method of message passing used to implement the algorithm. In order for RIP to be a useful protocol, it was necessary that some of these issues be addressed, in the form of changes to the basic RIP algorithm and operational scheme we explored earlier in this section.

The solution to problems that arise due to RIP being too simple is to add complexity, in the form of features that add more intelligence to the way that RIP operates. Let’s take a look at four of these: split horizon, split horizon with poisoned reverse, triggered updates and hold-down.

Split Horizon

The “counting to infinity” problem is one of the most serious issues with the basic RIP algorithm. In the example in the previous topic, the cause of the problem is immediately obvious: after Network 1 fails and Router A notices it go down, Router B “tricks” Router A into thinking it has an alternate path to Network 1 by sending Router A a route advertisement to N1.

If you think about it, it doesn't really make sense—under any circumstances—to have Router B send an advertisement to Router A about a network that Router B can only access through Router A in the first place. In the case where the route fails it causes this problem, which is obviously a good reason not do it. But even when the route is operational, what is the point of Router B telling Router A about it? Router A already has a shorter connection to the network and will therefore never send traffic intended for Network 1 to Router B anyway.

Clearly, the best solution is simply to have Router B not include any mention of the route to Network 1 in any RIP Response messages it sends to Router A. We can generalize this by adding a new rule to RIP operation: when a router sends out an RIP Response on any of the networks to which it is connected, it omits any route information that was originally learned from that network. This feature is called split horizon, since the router effectively splits its view of the internetwork, sending different information on certain links than on others.

With this new rule, let's consider the behavior of Router B. It has an interface on Network 2, which it shares with Router A. It will therefore not include any information on routes it originally obtained from Router A when sending on N2. This will prevent the “counting to infinity” loop we saw in the previous topic. Similarly, since Router D is on Network 3, Router B will not send any information about routes it got from Router D when sending on Network 3.

Note, however, that split horizon may not always solve the “counting to infinity” problem, especially in the case where multiple routers are connected indirectly. The classic example would be three routers configured in a triangle. In this situation, problems may still result due to data that is propagated in two directions between any two routers. In this case, the “hold down” feature may be of assistance (see below).

Previous Topic/Section
RIP Protocol Limitations and Problems
Previous Page
Pages in Current Topic/Section
Next Page
RIP Version-Specific Message Formats and Features
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 (
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.