The fourth work: using Packet Tracer understand RIP routing protocol

• Name: Wong Choi Chak
• Student ID: 201821121014　　
• Class: calculated 1811

1 Purpose

• Understanding and establish RIP routing table updates
• RIP feeling bad news travels slow

2 Experimental content

Use Packet Tracer, properly configure network parameters, use the command to view and analyze RIP routing information.

• Establish a network topology
• Configuration parameters
• Analysis of RIP routing information

3. The test report

3.1 Establish a network topology

Network topology as shown below:

 

3.2 Configuration Parameters

• IP address of the client is192.168.1.14
• Routing configuration:

R1 (config) #interface GigabitEthernet0 / 0 // router R1 enters G0 / 0 port configuration ip

R1(config-if)#ip address 192.168.1.15 255.255.255.0

R1(config-if)#no shutdown

R1 (config) #interface GigabitEthernet0 / 1 // router R1 enters G0 / 1 port configuration ip

R1(config-if)#ip address 192.168.2.14 255.255.255.0

R1(config-if)#no shutdown

 

R1 (config) #router rip // RIP configuration

R1(config-router)#version 2

R1(config-router)#192.168.1.0

R1(config-router)#192.168.2.0

3.3 Testing Network Connectivity

In PC1, PING PC2, the whole link connectivity test given screenshot:

 

 

 

3.4 understand RIP routing table to establish and update

• View information routing processshow ip protocols

Routing Protocol is "rip"

Sending updates every 30 seconds, next due in 22 seconds

Invalid after 180 seconds, hold down 180, flushed after 240

Outgoing update filter list for all interfaces is not set

Incoming update filter list for all interfaces is not set

Redistributing: rip

Default version control: send version 2, receive 2

Interface Send Recv Triggered RIP Key-chain

GigabitEthernet0/0 2 2

GigabitEthernet0/1 2 2

Automatic network summarization is in effect

Maximum path: 4

Routing for Networks:

192.168.1.0

192.168.2.0

Passive Interface(s):

Routing Information Sources:

Gateway Distance Last Update

192.168.2.15 120 00:00:24

Distance: (default is 120)

Explanation: This result indicates that the routing protocol is RIP, updated every 30 seconds, the maximum path length is 4, and the route network ip

• View the routing tableshow ip route

Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP

i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area

* - candidate default, U - per-user static route, o - ODR

P - periodic downloaded static route

 

Gateway of last resort is not set

 

192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks

C 192.168.1.0/24 is directly connected, GigabitEthernet0/0

L 192.168.1.15/32 is directly connected, GigabitEthernet0/0

192.168.2.0/24 is variably subnetted, 2 subnets, 2 masks

C 192.168.2.0/24 is directly connected, GigabitEthernet0/1

L 192.168.2.14/32 is directly connected, GigabitEthernet0/1

R 192.168.3.0/24 [120/1] via 192.168.2.15, 00:00:07, GigabitEthernet0/1

Explanation: This result indicates that the two ports are directly connected routes, R represents a line that has a non-direct route learned

• View RIP send and receive messagesdebug ip rip

RIP: sending v2 update to 224.0.0.9 via GigabitEthernet0/0 (192.168.1.15)

RIP: build update entries

192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

192.168.3.0/24 via 0.0.0.0, metric 2, tag 0

RIP: sending v2 update to 224.0.0.9 via GigabitEthernet0/1 (192.168.2.14)

RIP: build update entries

192.168.1.0/24 via 0.0.0.0, metric 1, tag 0

RIP: received v2 update from 192.168.2.15 on GigabitEthernet0/1

192.168.3.0/24 via 0.0.0.0 in 1 hops

RIP: sending v2 update to 224.0.0.9 via GigabitEthernet0/0 (192.168.1.15)

RIP: build update entries

192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

192.168.3.0/24 via 0.0.0.0, metric 2, tag 0

RIP: sending v2 update to 224.0.0.9 via GigabitEthernet0/1 (192.168.2.14)

RIP: build update entries

192.168.1.0/24 via 0.0.0.0, metric 1, tag 0

RIP: received v2 update from 192.168.2.15 on GigabitEthernet0/1

192.168.3.0/24 via 0.0.0.0 in 1 hops

RIP: sending v2 update to 224.0.0.9 via GigabitEthernet0/0 (192.168.1.15)

RIP: build update entries

192.168.2.0/24 via 0.0.0.0, metric 1, tag 0

192.168.3.0/24 via 0.0.0.0, metric 2, tag 0

RIP: sending v2 update to 224.0.0.9 via GigabitEthernet0/1 (192.168.2.14)

RIP: build update entries

192.168.1.0/24 via 0.0.0.0, metric 1, tag 0

Explain: the G0 / 0 port send updates to 224.0.09, received updated information from 192.168.2.15. Hop from 192.168.3.0 to 0.0.0.0

4. appreciated RIP message travels slowly

Command by shutdownclosing an interface R1 G0 / 0/0. View RIP routing updates on R1 debug ip rip, and briefly (do not need every step of the analysis) analysis R1 routing table is how to re-converge.

RIP: received v2 update from 192.168.2.15 on GigabitEthernet0/1
192.168.3.0/24 via 0.0.0.0 in 1 hops
RIP: received v2 update from 192.168.2.15 on GigabitEthernet0/1
192.168.3.0/24 via 0.0.0.0 in 1 hops
RIP: received v2 update from 192.168.2.15 on GigabitEthernet0/1
192.168.3.0/24 via 0.0.0.0 in 1 hops
RIP: received v2 update from 192.168.2.15 on GigabitEthernet0/1
192.168.3.0/24 via 0.0.0.0 in 1 hops

Analysis: After the R1 interface G0 / 0 off, G0 / 0 RIP does not send update information. R1 receives every 30 seconds the updated routing table information to the first network to the distance 16, but this time not to the unreachable R2, R1 pass the routing table, the routing table updates to the web is less than the distance R1 16, net after a 16-hop routing R1 to know the network is not reachable, news travels slowly routing table, routing table only after a long period of convergence again.