If two routers cannot exchange routes, the problem is usually not “the routing protocol.” It is almost always the network configuration: the wrong subnet, a shut interface, a missed network statement, or a version mismatch. This guide shows you how to build a working RIP setup between two routers, verify it, and troubleshoot the common failures without guessing.
Cisco CCNA v1.1 (200-301)
Learn essential networking skills and gain hands-on experience in configuring, verifying, and troubleshooting real networks to advance your IT career.
Get this course on Udemy at the lowest price →RIP is one of the easiest routing protocols to understand because it uses hop count, not complex metrics. That makes it useful in labs, small legacy networks, and training environments where you want to see dynamic routing in action before moving on to more advanced routing setup work. The steps here fit Cisco IOS, Packet Tracer, GNS3, and real hardware, so the same logic applies whether you are practicing for Cisco CCNA v1.1 (200-301) or building a small test topology.
There is a reason this topic shows up early in networking training. Once you understand how RIP advertises routes, learns neighbors, and populates a routing table, a lot of other topics start making sense: subnet id, subnet mask of /24, layer 1 vs layer 2, and even why a router needs a correct interface IP before any dynamic protocol can work. If you need a refresher on the protocol stack itself, the Cisco OSI model overview is a solid reference for protocols by osi layer.
Understanding RIP and When To Use It
RIP, short for Routing Information Protocol, is a distance-vector routing protocol that selects paths based on the number of routers a packet must cross. That hop-count logic is simple, which is exactly why RIP is easy to configure and easy to diagnose. It is also why it is rarely the best choice for large production networks.
RIP v1 versus RIP v2
The most important difference is that RIP v1 is classful, while RIP v2 is classless. Classful routing ignores subnet masks in route updates, which causes trouble with VLSM and discontiguous networks. RIP v2 carries subnet mask information, supports authentication, and is the version you normally want when learning or configuring modern lab networks.
That distinction matters any time you are working with a subnet list or comparing a subnet mask list for a lab. For example, if one router sees 192.168.10.0/24 and another sees 192.168.10.0/25, RIP v1 will not handle that cleanly. RIP v2 is designed to preserve the mask information so the receiving router can install the correct route.
Why RIP is limited
RIP’s maximum metric is 15 hops. A route with 16 hops is considered unreachable. That alone rules it out for many enterprise designs. RIP also converges more slowly than modern protocols such as OSPF or EIGRP, which means it takes longer to recover from a link failure and can temporarily black-hole traffic during reconvergence.
The official Cisco routing documentation explains how these protocol behaviors affect deployment choices, and the broader routing fundamentals are also covered in the Cisco routing overview. If you want to understand why RIP is still taught, the answer is simple: it makes the mechanics of dynamic routing visible without hiding them behind complex calculations.
RIP is not the protocol you choose for scale. It is the protocol you choose when you want routing behavior to be easy to see, easy to explain, and easy to verify in a lab.
Where RIP still makes sense
RIP can still be useful in small isolated networks, training labs, and legacy environments where simplicity matters more than efficiency. It is also a good teaching tool because it shows how routers advertise connected networks and learn remote ones automatically. If your goal is to build intuition, RIP is worth knowing.
- Lab practice for routing fundamentals
- Small isolated networks with minimal hop count
- Legacy gear that only supports basic dynamic routing
- Educational demos for route exchange and convergence
For comparison, OSPF is usually preferred in larger networks because it converges faster and scales better, while EIGRP offers efficient metric-based path selection. RIP is simpler, but simplicity is not the same thing as capability.
Planning the Two-Router Topology and Routing Protocols
A clean two-router lab should be small enough to understand at a glance and complete enough to show route learning. The standard design is Router A and Router B connected by one point-to-point or Ethernet link, with one LAN behind each router. This creates a visible before-and-after: before RIP, each router only knows its own connected networks; after RIP, each router should learn the remote LAN.
Sample topology layout
Use separate subnets for each segment. That means one subnet for Router A’s LAN, one for the inter-router link, and one for Router B’s LAN. Keep them non-overlapping and easy to read. A good planning habit is to label each interface with the IP address, mask, and purpose before you type a single command.
| Segment | Example subnet |
| Router A LAN | 192.168.10.0/24 |
| Inter-router link | 10.0.0.0/30 |
| Router B LAN | 192.168.20.0/24 |
That example gives you a clear subnet mask of /24 for each LAN and a tighter /30 for the transit link. It is also a good way to practice table subnetting because the address plan is simple enough to verify manually, yet realistic enough to reflect actual network design work.
Why documentation matters before configuration
Write down the interface names, IPs, masks, and expected routes. If you are using Cisco IOS, this can be as simple as a notes file or a lab worksheet. If you are using Packet Tracer or GNS3, label the interfaces in the topology. The goal is to know exactly which network should appear on which router after RIP is enabled.
This is also where a quick diagram saves time. A visual sketch helps you avoid common mistakes like assigning the same subnet to both sides of the link or forgetting to place a LAN behind one router. In troubleshooting, good planning is not optional; it is the fastest way to spot what should exist but does not.
Key Takeaway
Plan the addressing first. RIP will only advertise what the router already understands, so the interfaces, masks, and subnets must be correct before dynamic routing can work.
Preparing the Routers Before RIP Configuration
Before you configure RIP, both routers need working interfaces and valid IP addresses. RIP does not fix broken physical connectivity, incorrect masks, or shutdown ports. If the directly connected network is not up, the routing protocol has nothing to advertise.
Check physical or virtual connectivity
Start by confirming the link exists. On real hardware, check the cable, port type, and speed/duplex settings if needed. In a simulator, make sure the correct interfaces are actually connected and not left unlinked. This is where switching tech and the physical side of layer 1 vs layer 2 become relevant: a router cannot exchange RIP updates over a dead interface.
- Verify cable or virtual link association
- Check interface status with
show ip interface brief - Look for up/up state on active ports
- Use
pingacross the directly connected link
Assign and verify IP addressing
Each router should have one interface facing its LAN and one interface facing the other router. A common lab design is:
- Router A LAN: 192.168.10.1/24
- Router A transit: 10.0.0.1/30
- Router B transit: 10.0.0.2/30
- Router B LAN: 192.168.20.1/24
Once the addresses are configured, test direct reachability. Router A should ping Router B’s transit interface, and vice versa. If that fails, there is no point in moving forward to RIP yet. This is also the stage where you confirm both devices use compatible masks and no address overlaps exist.
For a broader refresher on common interface and protocol concepts, Cisco’s networking documentation is useful, and the Cisco IP address guide helps reinforce how subnets and host ranges fit together. If you are still shaky on what is subnet /24, this is the time to review it.
Warning
If the inter-router link is not reachable with a basic ping, RIP will not solve the problem. Fix the physical link, IP address, or mask first.
Configuring RIP on the First Router
RIP configuration is short, but each command matters. The router only advertises the networks that you explicitly include under the RIP process, so the routing setup must match the actual interfaces and addressing plan. If you omit one network, the other router will not learn it.
Basic RIP v2 setup
- Enter global configuration mode.
- Start the RIP process with
router rip. - Set the version to 2 with
version 2. - Disable auto-summary with
no auto-summary. - Add the connected major networks using
networkstatements.
On Router A, that typically means advertising the LAN subnet and the transit network. If the LAN is 192.168.10.0/24 and the transit link is 10.0.0.0/30, the router needs both major networks in its RIP process. The commands tell RIP which interfaces to include and which connected routes to advertise to neighbors.
router rip
version 2
no auto-summary
network 192.168.10.0
network 10.0.0.0In Cisco IOS, the network statement matches the major network, not the exact host IP. That is why a correct addressing plan matters. For more detail on official Cisco routing behavior, see the Cisco RIP configuration guide.
Why version 2 and no auto-summary matter
RIP v2 carries subnet mask information, which is necessary for classless routing and for keeping routes correct across different subnet sizes. Auto-summary can silently break routing in networks that use multiple subnets from the same major network. If you are using a lab with modern subnetting, disabling auto-summary is usually the safe choice.
This is the point where routing protocols stop being abstract and become operational. The router now has enough information to advertise its local networks to the neighbor. If the configuration is right, the remote router should eventually learn them without manual static routes.
Configuring RIP on the Second Router
Router B uses the same logic as Router A. The process must match on both sides, or the two devices will not exchange updates correctly. A common mistake is configuring version 2 on one router and leaving the other at the default version, or forgetting to advertise the transit network that connects the routers.
Mirror the RIP settings
On Router B, enable RIP, select version 2, disable auto-summary, and add the connected networks. The local LAN and the inter-router network should both be part of the routing process. If Router B has 192.168.20.0/24 on the LAN side and 10.0.0.0/30 on the transit side, the configuration should reflect that.
router rip
version 2
no auto-summary
network 192.168.20.0
network 10.0.0.0That is the core of the routing setup. Once both routers are advertising the transit link and their local LANs, each router should be able to learn the opposite LAN through RIP updates. In a lab, that is the moment where the routing table finally shows a remote network code learned dynamically rather than statically entered.
Common setup errors
- Wrong major network: entering the wrong network statement, so the interface is never included in RIP
- Missing network statement: forgetting to advertise the LAN or the transit link
- Version mismatch: one router using RIP v1, the other RIP v2
- Auto-summary left on: causing route summarization that does not fit the addressing plan
- Interface disabled: the router is configured correctly, but the port is still shutdown
When you are learning routing protocols, it helps to think in terms of interfaces, not commands. RIP runs on interfaces. If the interface is wrong, the command is wrong by extension.
Verifying RIP Route Exchange and Routing Protocols
Verification tells you whether the routing protocol is actually working or just configured. The most useful check is the routing table, because it shows whether each router learned the remote LAN through RIP and installed it with the proper route code.
Check the routing table
On Cisco IOS, use show ip route. A successful RIP-learned route appears with an R code. For example, Router A should learn 192.168.20.0/24 through the inter-router link, and Router B should learn 192.168.10.0/24 the same way. If those routes are missing, RIP updates are not being received or accepted.
show ip routeYou can also inspect RIP behavior with show ip protocols. That output confirms which version is active, which networks are being advertised, which interfaces are passive, and what timers are in use. This is one of the fastest ways to catch a mismatch without digging through the entire configuration.
Test end-to-end reachability
After the routes appear, test connectivity from a host on Router A’s LAN to a host on Router B’s LAN. If the router interfaces are correct, the ping should succeed across the full path. If the ping fails but the route exists, the issue is likely on the endpoint, the return path, or a local firewall setting.
For quick protocol context, remember that FTP TCP port number is 21 and secure file transfer uses different behavior than plain FTP. That kind of protocol awareness matters when you later mix routing verification with application testing. If you ever need to explain what port for SFTP, the answer is that SFTP typically runs over SSH on port 22, not FTP on port 21.
If a route is in the table but traffic still fails, the routing protocol is not your only problem. Verify the host IPs, default gateways, masks, and return path.
For an official reference on Cisco command behavior, the Cisco RIP configuration guide remains the best source for exact IOS syntax and route-learning behavior.
Troubleshooting Common RIP Problems
RIP problems are usually simple, but they are not always obvious. Missing routes, one-way connectivity, and incomplete routing tables usually point to an issue with interface state, version compatibility, or a missing network statement. The key is to troubleshoot in a fixed order instead of jumping around.
Work from the physical layer upward
- Check interface status with
show ip interface brief. - Confirm the IP address and mask on both sides of the link.
- Ping the directly connected neighbor.
- Verify the RIP version and network statements.
- Inspect the routing table for learned routes.
- Test host-to-host connectivity across both LANs.
This order matters because it narrows the failure domain. A shut interface or a bad mask is a lower-level problem than a routing protocol issue. In other words, do not blame RIP until the link itself works.
Typical RIP-specific failures
- Mismatched versions: one router runs RIP v1, the other RIP v2
- Passive interface mistakes: updates are blocked where they should not be
- Auto-summary confusion: classful summarization hides the real route
- Incorrect subnet mask: the router believes a network is different from the one planned
- Overlapping subnets: route selection becomes ambiguous or invalid
Passive interfaces deserve special attention. They are useful on LAN-facing ports because you usually do not want to send routing updates to end hosts, but if you accidentally make the inter-router link passive, the routers will stop exchanging RIP updates. That is a classic one-way routing failure.
If you need an external reference for protocol and configuration behavior, Cisco’s routing documents are the most relevant official source. For broader operational thinking, NIST’s guidance on network resilience and secure configuration is available through NIST, which is useful when you move beyond lab work into production-style change control.
Note
When RIP fails, the fix is usually visible in the interface table, not hidden in the routing table. Start with connectivity, then move to protocol settings.
Optimizing and Securing RIP in a Small Network
RIP is basic, but even a basic routing protocol needs guardrails. In small networks, the goals are usually stability, predictability, and limiting who can inject routing information. You do not need a heavyweight design to take those seriously.
Use RIP v2 authentication where possible
RIP v2 supports authentication on many platforms. That matters because it prevents unauthorized devices from sending spoofed route updates. In a small lab or branch network, route authentication is one of the easiest ways to avoid accidental or malicious changes to the routing table.
If your platform supports it, pair RIP v2 with a simple shared secret. Then verify both routers use the same authentication settings before expecting the route exchange to work. That kind of basic trust control is often overlooked in training labs, but it reflects good operational practice.
Use passive interfaces intelligently
Passive interfaces are a practical optimization. On LAN-facing interfaces, they stop unnecessary RIP advertisements from reaching end devices while still allowing the router to advertise the network if the platform supports it that way. On router-to-router links, do not make the interface passive if you want the routers to exchange routes.
RIP also uses built-in loop-prevention features such as split horizon and route poisoning. Split horizon stops a router from advertising a route back out the same interface it learned it on. Route poisoning marks failed routes with an unreachable metric so neighbors remove them quickly. These features reduce simple routing loops, but they do not make RIP immune to bad design.
Think about timers and stability
RIP timers affect how fast updates are sent and how quickly failures are detected. In a stable network, that may be fine. In a noisy environment with frequent link changes, slower convergence can become a real operational problem. That is one reason RIP is a poor fit for larger or unstable networks.
For more formal network hygiene, the NIST Cybersecurity Framework is a useful reference point for configuration management and resilience principles. The framework is not about RIP specifically, but the discipline applies: document your setup, back it up, and verify changes before you call the job done.
Practical Example Walkthrough
Here is a complete sample lab you can copy into a simulator or real router pair. The design is intentionally small so you can focus on the routing behavior instead of the topology itself. It uses two routers, two LANs, and one point-to-point transit link.
Sample IP plan
- Router A LAN interface: 192.168.10.1/24
- Router A transit interface: 10.0.0.1/30
- Router B transit interface: 10.0.0.2/30
- Router B LAN interface: 192.168.20.1/24
- Host on Router A LAN: 192.168.10.10/24, gateway 192.168.10.1
- Host on Router B LAN: 192.168.20.10/24, gateway 192.168.20.1
Router A configuration
interface g0/0
ip address 192.168.10.1 255.255.255.0
no shutdown
interface g0/1
ip address 10.0.0.1 255.255.255.252
no shutdown
router rip
version 2
no auto-summary
network 192.168.10.0
network 10.0.0.0Router B configuration
interface g0/0
ip address 192.168.20.1 255.255.255.0
no shutdown
interface g0/1
ip address 10.0.0.2 255.255.255.252
no shutdown
router rip
version 2
no auto-summary
network 192.168.20.0
network 10.0.0.0After the configuration is up, show ip route on Router A should include 192.168.20.0/24 as an R route, and Router B should show 192.168.10.0/24 the same way. That is the practical proof that the routing protocols exchange is working correctly.
show ip route
show ip protocols
ping 192.168.20.10When the ping succeeds, you have verified more than just RIP. You have verified addressing, interface status, routing advertisement, route installation, and the return path. That is exactly the kind of end-to-end check that makes a lab useful.
For official background on routing and protocol fundamentals, Cisco’s networking resources are relevant, and if you want to connect this lab to broader job skills, the U.S. Bureau of Labor Statistics offers the Network and Computer Systems Administrators occupational outlook, which shows why routing basics still matter in operations roles.
Cisco CCNA v1.1 (200-301)
Learn essential networking skills and gain hands-on experience in configuring, verifying, and troubleshooting real networks to advance your IT career.
Get this course on Udemy at the lowest price →Conclusion
RIP is one of the simplest ways to learn how dynamic routing works. If you plan the topology correctly, assign the right IP addresses, enable RIP v2, and verify the routing table, two routers will exchange routes with very little effort. If something breaks, the fix is usually found by checking interfaces, masks, network statements, and version matching in that order.
The important limitation is scale. RIP is easy to configure, but it is not efficient for larger or more complex networks. That is why it remains valuable as a learning tool and a small-network option, while OSPF and other protocols are generally preferred in production environments.
Use this guide as a repeatable lab exercise. Build it in a simulator, break it on purpose, and then repair it. That is the fastest way to understand routing setup, route advertisement, and the logic behind all dynamic routing protocols. If you are working through Cisco CCNA v1.1 (200-301), this is the kind of hands-on practice that turns theory into muscle memory.
For more structured networking practice, keep using official vendor documentation and lab the same scenario until you can verify every step without notes. That is how routing concepts stick.
CompTIA®, Cisco®, Microsoft®, AWS®, EC-Council®, ISC2®, ISACA®, and PMI® are trademarks of their respective owners.