Skip to main content

Route This Way: Introduction To Routing Protocols + RIP

Less 'introduction' and more "Well, I paid and studied to take the CCNA, so I'm going to put this information to use somehow."




Also, apparently network administrators feel very strongly about their routing protocol of choice, and will fight people over it.

To be clear, I'm 🤔 at the person who went through all that effort to make an account to do this. I have that kind of time as well, but I'm not doing that, I'm doing this.


So, what is a Routing Protocol?

Graphic Design in My Passion

Routing protocols do a lot of the configuring for you on a network. No need for incessantly typing in static routes, which don't scale easily across a large network and take up a lot of time.

Distance Vector -
  • How far away is the destination. This is usually counted via hops.
  • Slower convergence because it sends the entire routing table.
  • Prone to loops.

Link State -
  • The router knows about every other router and it's, well, link state. 
  • The only information that is sent or received is changes in links - are they up or down?
  • Converge much quicker, at the cost of using more CPU.
  • Has three tables:
    • Neighbor - "Who's running the same routing protocol?"
    • Topology - "Where is everybody?"
    • Routing  -"How can I get to this place quickest?"
Let's start with RIP, so this post isn't woefully short:


Here is the topology so far; The following configurations are focused on the highlighted bits.



Configuration is simple:

I don't recall version 1 being used...a ton - or at all in the learning present day - so we're going with version 2.


Everything in the 192.168 and 10 networks are being advertised to Router 2 (on the left).

 show ip route



The 10 and 192.168.1 networks are 'directly connected', as they're on the same router where I ran the command.

Let's set up Router 2 (on the left) and show ip route again on router 1.


The highlighted area says "Yes, we're connected with the RIP routing protocol.". We can also stop the PCs from receiving RIP updates with the passive-interface command within the routing protocol configuration:

passive-interface [int]

 This network is small, so the 15 hop count limit that plagues RIP will be no issue here. But what if the network was far bigger?

Keep reading.

Comments

Popular posts from this blog

What Do You Need? [AKA; List of Offered Services / My Next Role] (2020)

UPDATED 2021 I am a trusted outsourced remote consultant for your company.   I enjoy having the flexibility to take on temporary projects from time to time! I start at part-time, temp work for now. If we like each other, we can renegotiate. If anything sounds weird, out there, or unusual - Feel free to e-mail me .  3 Services Offered Technical: Cloud Technician     Azure [ See tag ] WORKING ON: Infrastructure As Code (Specifically Terraform/Azure and CloudFormation/AWS)  Support [Web: Example Job Description ] [Text : Example Description ]     I help you with adjustments in HTML, CSS, and Javascript.     When you email a business a question and they answer? That's me.   IT Operations Tech [ Example Job Description ]     Hardware and SaaS support.     Cisco routing and switching (Networking). CCNA, A+, Sec+, Azure certified WORKING ON: Junos Networking  Writing :      You want to pay me to write more of *waves hand* this blog? I am game .     I write B2C e-mails going out to o

Contactless Tech’s Role in the New Guest Experience ft. Intelity and The George

 Contactless hospitality technology is growing. You want to get away, and you'll be damned if a little thing like a deadly virus will stop you! But you still don't want to touch things. Ew. During the chat between INTELITY CEO Robert Stevenson and THE GEORGE Director of Operations Kerrie Hunter, you’ll learn how the historic boutique hotel has adapted a mobile-first guest experience in the wake of COVID-19—and how they see contactless technology affecting the future of hospitality. I don't remember how I found INTELITY (probably hoping to score a position with them), but I liked them enough to stay on the e-mail lists.  

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H