Practical No.

4
Q4) Configure IP routing using RIP.

Routing Information Protocol - RIP

There are two versions of RIP: RIPv1 and RIPv2.

Comparing between RIPv1 and RIPv2

1.Both RIPv1 and RIPv2 have the Administrative distance 120.

2.Both RIPv1 and RIPv2 are distance vector routing protocol.

Both RIPv1 and RIPv2’s metric is hop count.

Maximum hop count = 15. Max routers = 16.

For example, all routers are running RIP and network 10.0.0.0 goes down.
After hold timer expires, that network will be advertised by metric 16 and everyone will know that
the network is down and that network will be seen in routing table as possibly down.

4.Both RIPv1 and RIPv2 send routing updates or complete routing table or broadcast every 30
seconds. i.e. The default routing update period for both version of RIP is 30 seconds. i.e. Both have
the same timers.

5.Both RIPv1 and RIPv2 use split horizon to prevent routing loops.

6.Both RIPv1 and RIPv2 are configured with router rip.

7.network command tells both RIPv1 and RIPv2 to send hellos, out an interface, to find neighbors
and to advertise routes.

R1(config-router)#network ?
A.B.C.D Network number
R1(config-router)#network 172.16.0.0 ?
<cr>
R1(config-router)#^Z
R1#

8.Both RIPv1 and RIPv2 are verified with show ip protocols.

Router#show ip protocols
R 10.0.0.10[120/3] via 20.0.0.7, 00:00:15, Serial0/0

The first number in the brackets is the administrative distance of the information source. 
The second number is the metric for the route.
In this case, the administrative distance is 120, default AD for RIP routes, and the 3 represents the
metric, which is the number of router hops in RIP. 

Difference
1. RIPv1 used broadcast. RIPv2 used multicast(224.0.0.9).

2. RIPv1 is a classful.(Classful: all subnet mask must be the same in the network.) RIPv2 is a classless.

3. RIPv1 does not support VLSM. RIPv2 supports VLSM. subnet mask field was added to the RIPv2
message header by RFC 1723 to add support for VLSM and CIDR.

4. RIPv1 does not allow authentication. RIPv2 allows MD5 authentication

5. RIP enabled interfaces send version 1(RIPv1) updates.Do not send version 2(RIPv2) updates.
RIP enabled interfaces receive any version(RIPv1 and RIPv2).

6. RIPv2 sends the subnet mask in updates and RIPv1 does not. i.e. Subnet mask information is
included in RIPv2 routing updates that is not included in RIPv1.

Advantage of RIPv2 over RIPv1

1. RIPv2 supports MD5 authentication for routing updates. i.e. RIP version 2 supports routing update
authentication.

2. RIPv2 used multicast(224.0.0.9) rather than broadcast.

3. RIPv2 auto summarize advertised routes across classful boundaries.

To disable this behavior, should apply no auto-summary command under the RIP process.

4. RIPv2 is classless routing protocol means that it sends subnet mask information when updates.
By sending the subnet mask information with the updates, RIPv2 can support Variable Length
Subnet Mask(VLSMs) as well as the summarization of network boundaries.

Disadvantage of RIPv1 and RIPv2

1.Both RIPv1 and RIPv2 send full routing tables out every 30 seconds. It’s a lot of overhead, require
too much bandwidth. Sending full routing table is unnecessary.

2.RIPv1 and RIPv2 does not form adjacency.

3.RIPv1 and RIPv2 work only on hop count(not consider the bandwith).

4.RIPv1 and RIPv2 have slow convergence.

5.Not scalable, because hop count is only 15.

 RIP Command

1.The command show ip route followed by the protocol will show that protocol's route from the
entire routing table.

R1#show ip route rip

2.The command show protocols is used to view the RIP routing protocol settings and configuration.

3.The command show ip rip database will display RIP routing updates or RIP routing information as
they are sent and received. But to see the updates in real time, we need command Debug not Show.
But don't do debug ip rip, don't do debug all. It may crash your router.Because all possible debugs
will start and consume router's whole processing and memory.

4.If The command Router(config-router)# version 2 is entered on the routers, only version 2 updates
are sent to 224.0.0.9.

5.If The command Router(config-router)# no version 2 is entered on the routers, version 1 and 2
updates will be received and the version 2 updates will not be sent.

6.The command debug ip rip shows the routes being advertised in RIP updates and the metrics of
these routes. i.e. debug ip rip will display RIP activity as it occurs on a router.
R1#debug ip rip

7.The command clear ip route * should apply after the command debug ip rip to clear the routing
table of its dynamic routes.

R1#clear ip route * 

8.The command undebug all turn off all debugs.

R1#undebug all 

9.To turn off specific debugs, run the command no debug followed by the type of debug you want to
turn off.

R1#no debug ip rip

__________________________________________________________________________
PRINT-OUT
___________________________________________________________________________

RIPv1 Lab with Packet Tracer

Configure RIPv1 on  Cisco Routers with following information:

Network: 172.16.0.0/16, 192.168.0.0/24, 10.0.0.0/8
Gateway Address: 172.16.0.1/16, 192.168.0.1/24, 10.0.0.1/8

Putting three IP addresses, subnet mask and default gateway to three PCs.
Click PC1/ Desktop/IP Configuration /Static
Click PC2/ Desktop/IP Configuration /Static

Click PC3/ Desktop/IP Configuration /Static

Configure Router R1

Router>en
Router#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#host R1
R1(config)#int fa 0/1
R1(config-if)#ip address 172.16.0.1 255.255.0.0
R1(config-if)#no shut
R1(config-if)#int fa 1/0
R1(config-if)#ip address 192.168.0.1 255.255.255.0
R1(config-if)#no shut
R1(config)#int fa 0/0
R1(config-if)#ip address 100.0.0.1 255.255.255.252
R1(config-if)#no shut
R1(config-if)#exit
R1(config)#

Configure Router R2

Router>en
Router#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#host R2
R2(config)#int fa 0/0
R2(config-if)#ip address 100.0.0.2 255.255.255.252
R2(config-if)#no shut
R2(config)#int fa 0/1
R2(config-if)#ip address 10.0.0.1 255.0.0.0
R2(config-if)#no shut
R2(config-if)#exit
R2(config)#

Configure RIPv1 to router R1Here we put all three network those are connected to R1 router.

A numeric value is required for EIGRP, OSPF. With EIGRP, AS number, with OSPF, the process
number, but RIP, there is no number.

R1(config)#router rip
R1(config-router)#network ?
  A.B.C.D  Network number
R1(config-router)#network 172.16.0.0 ?
  <cr>
R1(config-router)#network 172.16.0.0 
R1(config-router)#network 192.168.0.0 
R1(config-router)#network 100.0.0.0 
R1(config-router)#^Z
R1#

Configure RIPv1 to router R2

Here we put two network those are connected to R2 router.

R2(config)#router rip
R2(config-router)#network ?
  A.B.C.D  Network number
R2(config-router)#network 100.0.0.0
R2(config-router)#network 10.0.0.0
R2(config-router)#^Z
R2#

See routing table of router R1

R1#show ip route

Gateway of last resort is not set

R    10.0.0.0/8 [120/1] via 100.0.0.2, 00:00:20, FastEthernet0/0

       100.0.0.0/30 is subnetted, 1 subnets
C       100.0.0.0 is directly connected, FastEthernet0/0
C    172.16.0.0/16 is directly connected, FastEthernet0/1
C    192.168.0.0/24 is directly connected, FastEthernet1/0
R1#

R1#show ip rip database

10.0.0.0/8  
    [1] via 100.0.0.2, 00:00:12, FastEthernet0/0
100.0.0.0/30      directly connected, FastEthernet0/0
172.16.0.0/16     directly connected, FastEthernet0/1
192.168.0.0/24    directly connected, FastEthernet1/0
R1#

See routing table of router R2

R2#show ip route

Gateway of last resort is not set

C    10.0.0.0/8 is directly connected, FastEthernet0/1
     100.0.0.0/30 is subnetted, 1 subnets
C       100.0.0.0 is directly connected, FastEthernet0/0
R    172.16.0.0/16 [120/1] via 100.0.0.1, 00:00:09, FastEthernet0/0
R    192.168.0.0/24 [120/1] via 100.0.0.1, 00:00:09, FastEthernet0/0
R2#

R2#show ip rip database

10.0.0.0/8        directly connected, FastEthernet0/1
100.0.0.0/30      directly connected, FastEthernet0/0
172.16.0.0/16
    [1] via 100.0.0.1, 00:00:19, FastEthernet0/0
192.168.0.0/24
    [1] via 100.0.0.1, 00:00:19, FastEthernet0/0
R2#

Now check IP connectivity

Click PC-1/ Desktop/Command Prompt

PC>ping 10.0.0.2

Pinging 10.0.0.2 with 32 bytes of data:

Reply from 10.0.0.2: bytes=32 time=12ms TTL=126

Reply from 10.0.0.2: bytes=32 time=13ms TTL=126
Reply from 10.0.0.2: bytes=32 time=12ms TTL=126
Reply from 10.0.0.2: bytes=32 time=20ms TTL=126

Ping statistics for 10.0.0.2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 20ms, Average = 14ms

PC>

We can reach 10.0.0.0 network.

Click PC-2/ Desktop/Command Prompt

PC>ping 10.0.0.2

Pinging 10.0.0.2 with 32 bytes of data:

Reply from 10.0.0.2: bytes=32 time=12ms TTL=126

Reply from 10.0.0.2: bytes=32 time=14ms TTL=126
Reply from 10.0.0.2: bytes=32 time=24ms TTL=126
Reply from 10.0.0.2: bytes=32 time=11ms TTL=126

Ping statistics for 10.0.0.2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 24ms, Average = 15ms

PC>

We can reach 10.0.0.0 network.

Click PC-3/ Desktop/Command Prompt

PC>ping 172.16.0.2

Pinging 172.16.0.2 with 32 bytes of data:

Reply from 172.16.0.2: bytes=32 time=10ms TTL=126

Reply from 172.16.0.2: bytes=32 time=11ms TTL=126
Reply from 172.16.0.2: bytes=32 time=12ms TTL=126
Reply from 172.16.0.2: bytes=32 time=16ms TTL=126

Ping statistics for 172.16.0.2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 16ms, Average = 12ms

PC>

We can reach 172.16.0.0 network.

PC>ping 192.168.0.2
Pinging 192.168.0.2 with 32 bytes of data:

Reply from 192.168.0.2: bytes=32 time=12ms TTL=126

Reply from 192.168.0.2: bytes=32 time=11ms TTL=126
Reply from 192.168.0.2: bytes=32 time=22ms TTL=126
Reply from 192.168.0.2: bytes=32 time=10ms TTL=126

Ping statistics for 192.168.0.2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 22ms, Average = 13ms

PC>

We can reach 192.168.0.0 network.