So now that we're done with the process off manually, entering in routes into a routing table called static routing, where we have to manually enter the route to Metro 10 on router to one, we're gonna cover the process of dynamic routing.
Dynamic routing is the process when to routers, shared networks or remote networks or remote route or route to remote destinations. Automatic me by running these programs called routing Protocols on them. In our case, if we were running
dynamic routing on router to one route or to a one would automatic me learn how to get to Network 10 from Router one. Rather, too, would send information about Network 10 to Router one, and rather one would send information about Network 10 and how to get there to router to a one.
Now there are two types off
dynamic routing protocols. The first kind is your distance vector routing protocols and your second kind are your link state routing protocols.
pure distance vector routing protocol we're going to cover in this class is called Route Information Protocol or rip for short.
This inspector routing protocols possessed some qualities. Some common general qualities
when a router is running a distance Vector out in Peru calls it, sends
the contents off his whole routing table, every set interval in routing updates.
So every 30 seconds Route Information protocol is gonna send the contents off his whole routing table to the directly connected devices to it's directly connected neighboring devices.
this inspector out on parole, send the contents of the whole routing table every set interval, and this interval is 30 seconds for rip or route information protocol,
which is not a good thing, because every 30 seconds the router next to you is getting hit by all this information, whether it needs it or not.
For once, it's already learned this information. It doesn't need to re hear it over and over again, but distance vector routing for calls send the contents of the routing table every set interval. And for rip, this interval is 30 seconds.
This inspector out in Coco's also send the routing update through the address to 55255255255 Basically the all hosts all sub nets broadcast, which is also not a good thing because everybody on the network unless there's a router president and the router blocks this broadcast
because broadcasts can't trust transfers a router.
But otherwise everybody on the network is going to hear this update whether they want to or not.
Distance Vector outing protocols also use something called hop count as their metric
Now. First, let me define what a metric is.
the measure of distance between your local router and a remote network.
So once again, a metric is a measure off Distin's between your local router and a remote destination or the destination network.
So in this case, I've drawn out a little diagram. You see Network 10 is available to Router two and one True Router. Three.
using Hop Countess Metric Router to Is one router Hop away from Network 10.
The hot being router three.
Router three is zero hops away from Network 10 since it is directly connected, so Router three will send information about network 10 automatically to router to if they're running a distance, vector out in protocol
with the hop count of zero router to will incriminate that hop count to one, so Router two will be one hop
one hops. One hop away from network chin
router to will send information about Network 10 with the hop count of 12 router one and rather one will interment that hop count to two,
due to note that Roger one is to router hops away from Network 10.
Now, distance vector routing protocols are prone to routing loops
because they're out by rumor.
Now what do I mean by route by rumor? Well, from Router one's point of view. Rather, one doesn't really know whether Network 10 is actually two hops away. Or if Network 10 actually exists somewhere down here.
actually, I should say, if Network 10 exists somewhere up here, so the closer to the destination network you are, that is the source. So this is upstream.
so rather, one is not completely sure
that Network 10 is too router hops upstream.
It is just believing, router to and router To tells it that hey, I'm one rather hop away
and that Network 10 exists in that direction.
When we get to link state routing protocols, the other type of routing protocol,
the alternate to distance vector out in Peru calls you will see that router one will be completely aware off this link between itself and router to and the link between router to and router three and Network 10. So Router one will have an end to end view of the topology. But with this inspector routing protocols,
you just believe what the next top router is telling you,
which makes it prone to routing loops.
So let's see how routing Luke happens now. You don't actually need to know
in detail how routing loop happens for you. See CNN, you just need to know that they can happen. However, I will go ahead and demonstrate how routing room cat Luke can happen in a topology.
For that, I need to draw a diagram. Now I'm going to demonstrate how a routing Luke can happen.
So if I were to say,
Network 10 Net 10 or Network Chen is available to Router 412 and three through Router five, I would expect a resounding yes from you guys.
Router five. Let's say these routers are running route information protocol. Router five is sending its updates or its whole routing table, which at this point only consists of network 10 to router for every 30 seconds and then every 30 seconds. Router four is forwarding that information to Router one, and then every 30 seconds or out of one
is forging that information to Router to and router three.
Now from the point of view of Router three, let's look at Router three.
Network 10 is available to Router three
through Router one with a hop count off. 123
Network 10 is also available to Router three
through router to with the hot count off 1234
So hop count of three.
I'll write it here. Hop kind of three to Router one and how. Count of four through router to
now, let's say Network 10 feels this link on the router fails. Something goes wrong with that interface, and it fails.
Router five waits around for a little bit and then sends
another date to router for saying that Work 10 is down
after 30 seconds since we're running rip router foretells rah rah Juan. Hey, network 10 is down
Now, remember, Four Router three. Metro 10 is available to two part pats y our outer one with the top down to three and buy a round or two with a hop count of four.
Rather, one turns around and sends an update to Router True and Router three saying, Hey, guys, where 10 is down.
But since these updates are not synchronized, it could happen that while rather one was sending that update and that update arrived at Router three before it arrived at Router to in the meantime router to sends an update to Router three announcing that Network 10 is available to router to with a hop count of four
and now a router three also learns that Network 10 is down through Router three,
so this option gets taken away.
So router, two things about it and router three things about It and says, well before it was available through a closer distance or a closer metric with Hakan a Tree. But I have no other option, so I will go through a router to to get to Network 10
three increments the hop count for network 10 to 4
and keeps it in the routing table. But now, throughout her too
router to his update from Router one. That network 10 is down
at the same time sends an update to Router one saying, Hey, Network 10 is well in alive through me with the hop count of Fine.
So Router one learns this
doesn't know that it's gonna the update just came from itself.
So Router one doesn't know that if it goes to Router, three out of three will send it to Router to and back to Route A one
robber. One's view of the topology is Guru's as far as the next router over because this inspector out in Protocols Route by rumor,
Router one now learns that Metro 10 is well in alive with the hot count of five
Router one sends an update back this wonderful news to router for saying that Network 10 is melon alive with the hop count of six through outer. One
router of one writer four actually sends another big back to router five and Say's Network 10 is alive and well with the How count of six to router for
So basically any packets destined to that network are being black hold because they're going nowhere.
Router. One Also sense this updated received from Router three back to router to seeing Net wrote 10 is alive and well through me with the hop count of five
rotter to gets this update and goes, Hey, the hop count went up from 4 to 5.
Since this update two Router three
with the hop count of five and Router three instrumented to hop count of six.
This update again is sent from router 32 Router one and the hop counters instrumented and rather one turns around sense update back throughout or two. And what happens is a loop and you will constantly be implementing the hop count
which this process is called. Count counting to infinity
and eventually enough packets will jumble of this network that these routers will crash.
So that is how a routing group can happen.
Now this inspector routing protocols have an inbuilt lou prevention mechanism. Well, there are several invent built Lou prevention mechanism, so now we'll go over the distance vector routing protocol. Lou prevention mechanisms