Hi ! everyone on today we are going to learn about how to configure rip GNS3 lab in packet tracer as before going to the topic we will do A quick summary of RIPv2:
Configuring interfaces for R0, R1 & R2:
On Router R0:
R0(config)#interface s0/0
R0(config-if)#ip address 192.168.1.2 255.255.255.0
R0(config-if)#no shutdown
R0(config-if)#interface loopback0
R0(config)#ip address 12.0.0.1 255.0.0.0
On Router R1:
R1(config)#interface s0/0
R1(config-if)#ip address 192.168.1.1 255.255.255.0
R1(config-if)#no shutdown
R1(config-if)#interface f0/0
R1(config-if)#ip address 192.168.2.1 255.255.255.0
R1(config-if)#no shutdown
On Router R2:
R2(config)#interface f0/0
R2(config-if)#ip address 192.168.2.2 255.255.255.0
R2(config-if)#interface lo0
R2(config-if)#ip address 200.200.200.1 255.255.255.0
Before enable RIP we should check the routing table on these routers to understand what has been changed in these routers.
Verify:
when we check now we look the Serial and FastEthernet are connected properly.
R0#show ip route
R1#show ip route
R2#show ip route
R0#exit
> Routing Information Protocol (RIP) is a true distance-vector routing protocol
> RIP permits a hop count of up to 15, so anything that requires 16 hops is deemed unreachable.
> RIP sends the complete routing table out to all active interfaces every 30 seconds (RIP updates occur every 30 seconds)
> RIP version 2 does send subnet mask information with the route updates. This is called classless routing.
> RIP only uses hop count to determine the best way to a remote network (a hop is a router)
> Administrative Distance is 120
> Support VLSM & dis-contiguous networks we have shown below topology.> RIP permits a hop count of up to 15, so anything that requires 16 hops is deemed unreachable.
> RIP sends the complete routing table out to all active interfaces every 30 seconds (RIP updates occur every 30 seconds)
> RIP version 2 does send subnet mask information with the route updates. This is called classless routing.
> RIP only uses hop count to determine the best way to a remote network (a hop is a router)
> Administrative Distance is 120
Configuring interfaces for R0, R1 & R2:
On Router R0:
R0(config)#interface s0/0
R0(config-if)#ip address 192.168.1.2 255.255.255.0
R0(config-if)#no shutdown
R0(config-if)#interface loopback0
R0(config)#ip address 12.0.0.1 255.0.0.0
On Router R1:
R1(config)#interface s0/0
R1(config-if)#ip address 192.168.1.1 255.255.255.0
R1(config-if)#no shutdown
R1(config-if)#interface f0/0
R1(config-if)#ip address 192.168.2.1 255.255.255.0
R1(config-if)#no shutdown
On Router R2:
R2(config)#interface f0/0
R2(config-if)#ip address 192.168.2.2 255.255.255.0
R2(config-if)#interface lo0
R2(config-if)#ip address 200.200.200.1 255.255.255.0
Before enable RIP we should check the routing table on these routers to understand what has been changed in these routers.
Verify:
when we check now we look the Serial and FastEthernet are connected properly.
R0#show ip route
R1#show ip route
R2#show ip route
Notice that these 3 routers only see the directly connected routers.
Now if you ping from the loopback (or any interface) of R0 to the loopback (or any interface) of R2 then the it will not successful because R0 doesn’t know which interface it should send the packets out to reach network 200.200.200.0.
Now enable RIPv2 on three routers
R0(config)#router rip
R0(config-router)#version 2
R0(config-router)#network 12.0.0.0
R0(config-router)#network 192.168.1.0
R1(config)#router rip
R1(config-router)#version 2
R1(config-router)#network 192.168.1.0
R1(config-router)#network 192.168.2.0
R2(config)#router rip
R2(config-router)#version 2
R2(config-router)#network 200.200.200.0
R2(config-router)#network 192.168.2.0
Notice that with RIP protocol we just need to type the main network without subnet mask or wildcard mask. If you type a subnetwork, it will be auto summary into the main network.
Check the routing tables of these routers we will see the differences
Verify
R0#show ip route
R1#show ip route
R2#show ip route
Now we can ping from the R0’s loopback interface to the R2’s loopback interface as the routing table of R0 has a path to R2’s loopback interface and vice versa.
If you want to check what is inside the update packet, use the command debug ip rip.
R0#debug ip rip
RIP protocol debugging is on
To turn off the debug ip, use the command undebug ip rip. If you want to disable all the debug processes, use the command undebug all.
No comments:
Post a Comment