How RIP Works Network Fundamentals Part 20

Time to see some dynamic routing in action! We’re going to start with RIP, or Routing Information Protocol. It’s a simple protocol that’s been around for a long time.
RIP is a type of Distance Vector Routing Protocol. This has a different approach to a Link State Protocol like OSPF. While Link State protocols have each router build a full map of the network, Distance Vector protocols are more concerned with just the next hop. They have ‘sign posts’ pointing the way.
To run RIP, the process must be started with ‘router rip’. This is also where most RIP configuration goes. This includes ‘version 2’, to limit the router to RIPv2 only, ‘no auto-summary’ to prevent automatic summarization to classful boundaries, and network statements to enable RIP on interfaces, and to advertise their connected routes.
If we don’t want RIP running on all interfaces, we can use ‘passive-interface’ or ‘passive-interface default’ to stop the updates being sent and received, while still allowing connected routes to be advertised.
Of course, we could also consider authentication between neighbours. We can configure this using MD5, which uses an encrypted password.
Each dynamic routing protocol uses a metric. This is a way to measure how good a link is. The routing protocol will use this metric to decide which path is best. RIP uses hop count as its metric.
It’s important to prevent routing loops. Distance Vector protocols do this by using the ‘split horizon’ rule. This prevents a router from sending an update for a network out an interface that the network update was received on.
If there are bad networks, RIP can ‘poison’ the route by setting the metric to 16. 16 hops is invalid in RIP terms. This causes other routers to know that this route is bad and shouldn’t be used.
If a router or a network fails, the network needs to ‘converge’. Convergence is the process that routers go through to find alternative paths during a failure, or to add new paths when new networks come online. We want convergence to be as quick as possible.
And we shouldn’t forget the default route. Rather than configure a static route everywhere, we can get RIP to share the default route with the rest of the network.
Be sure to try the labs, they will be worth your time!
Overview of this video:
0:00 Introduction
0:21 RIP Basics
1:19 Distance Vector and Link State
2:56 RIP Configuration
10:18 Passive Interfaces and Authentication
14:26 Metrics
17:12 Split Horizon and Route Poisoning
19:40 Convergence
22:36 Default Route Distribution
23:40 Labs
Quiz Link: https://networkdirection.net/labsandquizzes/quizzes/rip-quiz/
Lab Challenge 1: https://networkdirection.net/labsandquizzes/labs/lab-rip-configuration-1/
Lab Challenge 2: https://networkdirection.net/labsandquizzes/labs/lab-rip-configuration-2/
(Affiliate Link) CCNA 200-301 Official Guide (Volume 1): https://click.linksynergy.com/link?idRL4E8CmbSY&offerid145238.2955226&type2&murlhttp%3A%2F%2Fwww.ciscopress.com%2Ftitle%2F9780135792735
(Affiliate Link) CCNA 200-301 Official Guide (Volume 2): https://click.linksynergy.com/link?idRL4E8CmbSY&offerid145238.2885639&type2&murlhttp%3A%2F%2Fwww.ciscopress.com%2Ftitle%2F9781587147135
Patreon information: https://networkdirection.net/patreon/
LET'S CONNECT
https://www.youtube.com/c/networkdirection
https://twitter.com/NetwrkDirection
https://www.patreon.com/NetworkDirection
https://www.networkdirection.net
#NetworkDirection
#networking
#routing