Cisco Route Protocol RIP v1 (2)

Source: Internet
Author: User

Cisco router RIP version1 (2)
 
* Note: This article is intended for the majority of users to learn. Some of them will mention some professional Internet terms or abbreviations. If you do not understand the network, you can learn and explore it together. If you have any questions, you can add QQ or YY. (QQ: 914560310, YY: 283755973) "//" is not a command output or description.
 
This time we will talk about the RIP version1 passive interface and unicast update:
 
Next we will use experiments to better understand what passive interfaces, unicast updates, and their application scenarios are.
 
Passive interface, experiment topology:

* Note: because Ethernet f0/0 and f0/1 are connected to the host, you do not need to send route updates like some interfaces, so you can configure them as passive interfaces.
 
After configuring the IP address, we can configure the RIP Protocol. Next we will directly describe how to configure the RIP Protocol (using router R1 as an example)
 
R1 (config) # router rip // start the Routing Protocol
R1 (config-router) # version 1 // configure version 1
R1 (config-router) # network 10.0.0.0 // advertise the network
R1 (config-router) # network 172.16.0.0
R1 (config-router) # network 192.168.12.0
R1 (config-router) # passive-interface f0/0 // configure interface f0/0 as passive interface
R1 (config-router) # passive-interface f0/1 // configure interface f0/1 as passive interface
Then we configure R2 and then debug the experiment.
 
R1 # debug ip rip // view the Update Status of the RIP route protocol
RIP protocol debugging is on // The system prompts that RIP protocol debugging is enabled.
R1 # clear ip route * // clear all route tables
R1 # RIP: sending v1 update to 255.255.255.255 via Serial0/3/0 (192.168.12.1)
// The output of this sentence shows that RIP uses broadcast update. This statement uses the broadcast image interface "Serial0/3/0" to send updates.
RIP: build update entries // RIP is ready to create the updated route entry
 
Network 10.0.0.0 metric 1 // This is the created route entry "metric 1", which means the number of hops is 1.
 
Network 172.16.0.0 metric 1
 
 
R1 # RIP: sending v1 update to 255.255.255.255 via Serial0/3/0 (192.168.12.1)
// This is to send another RIP update to someone else.
RIP: build update entries
 
Network 10.0.0.0 metric 1
 
Network 172.16.0.0 metric 1
 
 
R1 # no debug ip rip // disable this function to view route updates.
RIP protocol debugging is off // The system prompts that the request has been disabled.
 
The above output indicates that router R1 does not send route updates to the passive interfaces g/0 and G/1.
 
* Note: The Passive interface can only receive route updates. It cannot send updates in broadcast or multicast mode, but it can send updates in Unicast mode. The command is as follows: R1 (config-router) # neighbor (followed by the destination network address). We will use the following experiment to better understand unicast updates.
RIP version 1 Dynamic Interface unicast update experiment topology,


As shown in, router R1 only sends route updates to router R3. Because RIP version1 is a broadcast update, by default, the router sends the update information to any device on the Ethernet. To prevent this from occurring, configure the f0/0 interface of R1 as a passive interface. Then, we use the unicast update method to send route updates for the specified vror3 R3.
 
After all routers are configured with RIP version1, we will perform experimental configuration on R1.
R1 (config) # route rip
R1 (config-router) # version 1
R1 (config-router) # network 172.16.1.0
R1 (config-router) # passive-interface f0/0 // set f0/0 as the passive Port
R1 (config-router) # neighbor 172.16.1.3 // send the RIP update protocol only to 172.16.1.3
 
* Note: When rip version1 is updated, it carries subnet information, but it must meet the following two conditions:
1. All the resistance of the entire network in the same primary network,
2. The subnet mask length must be the same,


** We are about to go home for the Chinese New Year. I wish you a happy Spring Festival and a wonderful year!
Red/Black alliance Up ~

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.