One of the problems with a Directly Connected Static Route(DCSR) is that it'll arp for every IP address it wants to reach. This is usually not a problem if the route only points to a small network. If you use a DCSR as your default route it will arp for every host on the internet you want to reach. That can fill up your arp table. At least that's the case for ethernet interfaces. I have no idea about serial links for example.
In your 1st example when your using the exit interface, why don’t you need a static route in the other direction for the ping to work; or did I miss the point that it’s directly connected on the target router ?
I should have pointed out that the 10.1.1.0/24 and 20.1.1.0/24 networks are configured using a loopback interface. Since there is no other physical interface in use other than Gig 0/0, this is why we see a successful unidirectional ping initially without the second static route in place. If you were to lab this up with an additional router attached to R2 connecting the 20.1.1.0/24 network, then both static routes would need to be in place for successful communication. I hope that clarifies things. Thanks so much for watching!
Thank you Charles. You explain things so well. Thanks.
Good stuff Charles, keep them coming
Plz post more videos than one per week !
Another example of Null0 is with route summation, I found out. Great stuff!
One of the problems with a Directly Connected Static Route(DCSR) is that it'll arp for every IP address it wants to reach. This is usually not a problem if the route only points to a small network. If you use a DCSR as your default route it will arp for every host on the internet you want to reach. That can fill up your arp table. At least that's the case for ethernet interfaces. I have no idea about serial links for example.
Very Good Explanation !
Again another very clear lesson, excellent
Thank you great video
Thank you for your job 👍🏽
Nice and clear!
In your 1st example when your using the exit interface, why don’t you need a static route in the other direction for the ping to work; or did I miss the point that it’s directly connected on the target router ?
I should have pointed out that the 10.1.1.0/24 and 20.1.1.0/24 networks are configured using a loopback interface. Since there is no other physical interface in use other than Gig 0/0, this is why we see a successful unidirectional ping initially without the second static route in place. If you were to lab this up with an additional router attached to R2 connecting the 20.1.1.0/24 network, then both static routes would need to be in place for successful communication. I hope that clarifies things. Thanks so much for watching!
@@CharlesJudd - Gotcha...Thanks 😊
Very useful