Dynamic Route RIP
RIP broadcasts UDP packets to exchange route information and sends route information updates every 30 seconds. The maximum number of hops supported by RIP is 15.
The experiment has been verified, but the topology is borrowed.
Tutorial topology:
650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/04533355B-0.png "title =" dsfds.png "/>
1. IP Address Table:
PC1 ip: 192.168.10.2/24
Gateway: 192.168.10.1
PC2 ip: 192.168.40.2/24
Gateway: 192.168.30.1
R1 F0/0192.168.10.1/24
R1 S2/0192.168.20.1/24
R2 S2/0192.168.20.2/24
R2 S3/0192.168.30.1/24
R3 F0/0192.168.40.1/24
R3 S2/0192.168.30.2/24
2,
R1 Configuration:
R1 (config) # interfacefastethernet 0/0 // enter the interface mode
R1 (config-if) # ipaddress 192.168.10.1 255.255.255.0 // configure the interface address
R1 (config-if) # noshutdown // activation Interface
R1 (config-if) # exit
R1 (config) # interfaceserial 2/0 // enter the interface mode
R1 (config-if) # ipaddress 192.168.20.1 255.255.255.0 // configure the interface address
R1 (config-if) # noshutdown // activation Interface
% LINK-5-CHANGED: Interface serial/0, changed state to down
R1 (config-if) # exit
R1 (config) # routerrip // enable the RIP Protocol
R1 (config-router) # network192.168.10.0 // advertise the connected CIDR Block
R1 (config-router) # network192.168.20.0 // advertise the connected CIDR Block
R1 (config-router) # exit
R1 (config) # exit
% SYS-5-CONFIG_ I: Configured from console by the console
R1 # write
Destinationfilename [startup-config]?
Buildingconfiguration...
[OK]
R1 #
R2 Configuration:
R2 (config) # interfaceserial 2/0
R2 (config-if) # ipaddress 192.168.20.2 255.255.255.0
R2 (config-if) # noshutdown
% LINK-5-CHANGED: Interface serial/0, changed state to up
R2 (config-if) # clockrate 64000
R2 (config-if )#
% LINEPROTO-5-UPDOWN: Line protocol on Interface serial/0, changed state to up
R2 (config-if) # exit
R2 (config) # interfaceserial 3/0
R2 (config-if) # ipaddress 192.168.30.1 255.255.255.0
R2 (config-if) # noshutdown
% LINK-5-CHANGED: Interface seri_3/0, changed state to down
R2 (config-if) # clockrate 64000
R2 (config-if) # exit
R2 (config) # routerip // enable the RIP Protocol
R2 (config-router) # network192.168.20.0 // advertise the connected CIDR Block
R2 (config-router) # network192.168.30.0 // advertise the connected CIDR Block
R2 (config-router) # exit
R2 (config) # exit
% SYS-5-CONFIG_ I: Configured from console by the console
R2 # write
Destinationfilename [startup-config]?
Buildingconfiguration...
[OK]
R2 #
R3 Configuration:
R3 (config) # interfacefastEthernet 0/0
R3 (config-if) # ipaddress 192.168.40.1 255.255.255.0
R3 (config-if) # noshutdown
R3 (config-if) # exit
R3 (config) # interfaceserial 2/0
R3 (config-if) # ipaddress 192.168.30.2 255.255.255.0
R3 (config-if) # noshutdown
% LINK-5-CHANGED: Interface serial/0, changed state to up
R3 (config-if )#
% LINEPROTO-5-UPDOWN: Line protocol on Interface serial/0, changed state to up
R3 (config-if) # exit
R3 (config) # routerip
R3 (config-router) # network192.168.40.0
R3 (config-router) # network192.168.30.0
R3 (config-router) # exit
R3 (config) # exit
% SYS-5-CONFIG_ I: Configured from console by the console
R3 # write
Destinationfilename [startup-config]?
Buildingconfiguration...
[OK]
R3 #
Verify Configuration:
PC1 to pingPC2
PC> ping192.168.40.2
Pinging192.168.40.2 with 32 bytes of data:
Reply from192.168.40.2: bytes = 32 time = 161 ms TTL = 125
Reply from 192.168.40.2: bytes = 32 time = 148 ms TTL = 125
Reply from192.168.40.2: bytes = 32 time = 132 ms TTL = 125
Reply from192.168.40.2: bytes = 32 time = 154 ms TTL = 125
Ping statistics for192.168.40.2:
Packets: Sent = 4, stored ED = 4, Lost = 0 (0% loss ),
Approximate roundtrip times in milli-seconds:
Minimum = 132 ms, Maximum = 161 ms, Average = 148 ms
PC1 and PC2 can communicate, indicating that the RIP Protocol experiment is successful!
Other rip commands: show ipprotocols // view IP Route Protocol configuration and statistics
Debug ip rip // view the dynamic update process of the RIP route protocol
Show ip rip database // view the RIP database
This article is from the "beyond and beyond" blog, please be sure to keep this source http://franksyl.blog.51cto.com/3207517/1293620