Tip:
Highlight text to annotate it
X
There is another situation where a static route might be useful, let me demonstrate
another network:
Here the Headquarters router is connected to the ISP. There are many networks on the
Internet so do we require all of those networks on the Internet in our routing table? The
answer is no because we can use a default route, let me show you what it is:
First we'll configure an IP address on the Fastethernet 1/0 of the headquarters router.
Now we will check our connectivity from the Headquarters router to the ISP router. A quick
ping to the ISP router proves that we can reach the ISP.
Now let's look at our routing table
Right now the Headquarters router only knows how to reach network 1.1.1.0 because it‟s
directly connected.
Now I will configure our Headquarters router to use google dns servers or you can use any
other public dns servers, just to inform our router to use these dns servers for name resolving.
So I say Ip name-server 8.8.8.8 8.8.4.4
Now I'll ping www.yahoo.com
It doesn't work, configuring the dns servers on our router wouldn't get us the connection
to the internet. It's just for name resolving. And it wouldn't resolve as long as it can't
connect to these public dns servers on the internet.
So Let's configure a default route so that we can reach the Internet: Headquarters(config)#ip
route 0.0.0.0 0.0.0.0 1.1.1.1 Let me explain this one:
The first 0.0.0.0 is the network address; in this case it means all networks.
The second 0.0.0.0 is the subnet mask; all 0s means all subnet masks.
1.1.1.1 is the next hop IP address. In this case the IP address of the ISP router.
In other words, this static route will match
all networks and that‟s why we call it a default route. When our router doesn‟t know
where to deliver IP packets to, we‟ll throw it over to the ISP and it will be their job
to deliver it.
Let's now test our internet connectivity.
Ping www.yahoo.com
This time is working as you see
I'd like to thank you for viewing. See you next video.