wiki:WikiImunesRIPExample

RIP

Open the topology Examples/RIP/RIP.imn and you should see this:

RIP example - topology picture.

Execute the experiment, right click on the router3 node and use Wireshark to listen to the eth3 interface.

You will see Request RIPv2 packets and their Response packets.

Response packet has the list of all the IP addresses and their metrics (number of routers in between) that router1 can "see", so now
the router3 knows how to reach every one of them. Every router receives their neighbours' Responses and depending on the lowest
metric to reach some other non-neighbour route, specific router is selected as the next hop.

Next example shows what happens when one of the routers stop working.

Terminate the current experiment, open the topology Examples/RIP/RIP1.imn and you should see this:

RIP1 example - topology picture.

Execute the experiment, right click on the router2 node and use Wireshark to listen to the eth2 interface.
To show the router2 route table, right click on the router2 node, open the Quagga console shell (vtysh) and execute:

show ip rip

The output should be:

router2# show ip rip
Codes: R - RIP, C - connected, S - Static, O - OSPF, B - BGP
Sub-codes:
      (n) - normal, (s) - static, (d) - default, (r) - redistribute,
      (i) - interface

     Network            Next Hop         Metric From            Tag Time
R(n) 0.0.0.0/0          10.0.7.2              2 10.0.7.2          0 02:51
C(i) 10.0.0.0/24        0.0.0.0               1 self              0
C(i) 10.0.1.0/24        0.0.0.0               1 self              0
R(n) 10.0.2.0/24        10.0.1.2              2 10.0.1.2          0 02:51
R(n) 10.0.3.0/24        10.0.0.1              2 10.0.0.1          0 02:51
R(n) 10.0.4.0/24        10.0.7.2              2 10.0.7.2          0 02:51
R(n) 10.0.5.0/24        10.0.1.2              3 10.0.1.2          0 02:51
R(n) 10.0.6.0/24        10.0.7.2              3 10.0.7.2          0 02:51
C(i) 10.0.7.0/24        0.0.0.0               1 self              0

If you ping the server node from the pc node, you will get the ping reply. According to the table, router2 should send every packet
with the destination address for the 10.0.4.0/24 subnet on the Next hop router 10.0.7.2 (router7). You can turn the router7 off by
right clicking on the router7 node and selecting Stop. Now the pc node will not be able to ping the server node until routes are changed
or router7 starts again.

You can also check every route status in the vtysh shell with the show ip rip status command.

Last modified 3 years ago Last modified on Nov 26, 2013 1:57:11 PM

Attachments (4)

Download all attachments as: .zip