Skip to main content

Emulating RIP(Routing information protocol) in GNS3

 RIP(Routing Information Protocol)

Being one of the Oldest distance vector routing protocols, RIP is based on the Bellman-ford algorithm. 
There are two versions of this protocol, which were published in 1998. We can find the complete documentation on internetsociety.org the file is located at RIP Official Documentation.

GNS3

Many professionals and students use Graphical Network Simulator to experiment with networking paradigms. we are using it to emulate the RIP routing algorithm.

Components

  • VPCs - 2
  • switch - 2
  • router(c7200) - 3

Topology


Topology constructed for this exercise 



Commands to set the IP address to interfaces in the router

config
interface <Interface_Name>
ip address <IP_addr> <Mask>
no shutdown


Commands used for initiating the RIP routing in a server are as follows

config
router rip
network <subnet1_network_addr>
network <subnet2_network_addr>

if all the commands are entered correctly we will see a result similar to the above diagram. here "R" in front of 10.0.0.0 represents the route found using the RIP protocol.


Nodes after assigning the IP address

Scenario analysis


Let only R1 and R3 routers be activated with the RIP routing. here we can now reach up to 192.168.2.2/24 and 192.168.1.2/24, beyond that the router R2 will not be having any knowledge of how to forward IPs between nodes around it. below ping results prove this.


once we activate the routing in Router R2, we will be able to reach the PC and another end of the network.


the Below Ping results confirm this


we can confirm the protocol that we are using by capturing the packets using the Wireshark tool. here we are using RIP version 1  we can use RIP version 2 by adding the command "version 2" during configuring RIP in the router. after the "router rip" command



Happy learning!!😊

Comments

Popular posts from this blog

Importance of identifying and tracking errors in DevOps

For almost three years I am curious about tracking errors in my daily work, there are lot of tools like Data dog, Splunk, Dynatrace etc... available as observability tools. it would have been easy to use those, rather I though why not build one. There is an advantage for projects that are small to rely on tools that are built around them. Standards set by industries are important, what if certain configuration don't align with general market standards. I think some developers agree with this approach. The idea of tracking error is not new, but the way we categorise them is unique to different environments. the nature of these categories depends on infrastructure used, network topology, development strategy. A tool designed to handle them all might be bit over engineered for the purpose, because I think the value it creates by reducing our efforts in identifying problems is not more valuable than the product itself. Again this is my opinion on projects that are small but needs quali...

Failed attempt of capturing pictures of the Milkyway

Picture of the night I went star gazing  I got a full frame camera, and I wanted to capture milky way. What I initially understood was it is easy to do it if I have a good equipment, I was proven wrong. I have nikon z5 with a zoom kit lens of f4. I traveled to nearest hills where there is less light pollution, the thing is I should have stayed on top of the hill to get good glimpse of the horizon. In southern hemisphere during the time of November milky way rise and set in south west region, we don't get the full view of it.  The failed attempt I stayed in a valley where they grow coffee beans. The other gamble I made was trusting the weather, this year(2024) post monsoon has extended and lot of clouds can be seeing near horizon. One observation I did was early morning before all the fog drops down the sky will be clear like a still pond this will be early 3 to 4 am in the morning. Next time I will try following what others are doing, get a tripod, also possibly a pollution fi...