- [Instructor] Alright, let's run over to the corp router,
and let's prepare our internet work to configure ip routing.
So, I know that doesn't make sense,
so lets take a look at it.
So, the first thing is that we understand
that a router was called forwarders at first, right?
And so by looking at the map of the internet work,
with the show ip route command,
show ip route, we can see the path the packet will take,
or that ip will use to get to a remote network.
So, by looking at this routing table,
we'll see the seize, stand for directly connected,
and the codes are up above, right?
And I can even scroll up a little bit here,
and we see l is local and c is connected.
Now, l means this is the ip address on my local interface.
C stands for connected, s is for static and r is for RIP.
There's some other ones we'll talk about when we get into
icnd two such as osp ah-vee-a-jayr-a-pee-an-so-um.
So, we can see going down now to our map,
see 10.10.10.0/24 is directly connected
off of fast ethernet zero zero.
In the link address, the fast ethernet zero zero,
is 10.10.10.1, shows us there with a 32 bit mask.
And now we can see 172.16.0.0/16
is subnetted using variable length subnet mass.
And notice that we have slash 30 mass under there
and then our link addresses.
Now, these are all directly connected.
Those are my WAN links, aren't they?
And then further down still,
we have what's called RIP injected routes,
and we'll take a look at that in a minute,
what we're here for is to turn off RIP.
It is on because for me to get
my inter-networking working
and to run through our previous labs,
I had to have some sort of routing working,
and RIP is a great thing for a small network like this.
Quick and fast, easy to configure.
But that's all it's good for, so we'll see.
First off, let's talk about this.
We see our RIP routes, these are injected in here
by the routing protocol,
the routing protocol builds our network,
builds our routing table between routers.
Alright, so what I'm gonna do is
I'm gonna go into each router now
and I'm gonna turn off RIP.
So config t, no router RIP, that's it. Right?
Now if I was to look at my routing table
I might still have some entries in there
for a few minutes, but then they'll be gone
and that's my system's log telling me
that I've gotten out of my console.
Now, alright, it does take a minute for those to get out
so if I show ip route we'll see
that our RIP is probably gone by now, it is.
Now, why is this important?
Well, I wanna show you your directly connected networks.
This is important because we're gonna
do static routing next.
And when we do static routing,
meaning we're putting the routes
to the remote networks by hand.
That means we're going to have administrative overhead.
When I had RIP in here we had overhead
from the routing protocol with bandwidth,
memory, processing, and so on.
Now we don't have that overhead,
but administratively we'll see
there's a lot of overhead involved.
And in a small network static routing is good,
in a large network it's hard.
The key for static routing is having a network map.
So, going to each router
and understanding what they're directly connected to
is important because we never type in a route
to my directly connected networks.
Alright, let's run out to San Francisco
and remember, I set my host names, right?
So, I can just type in San Francisco
and this is a good reason to use your local host database.
So, I'm in San Francisco now, let's do show ip route.
We can still see that we have RIP routes in here,
we have our directly connected, our local link addresses.
So, I'm going to do config t no router rip.
And then I'll come out,
and we'll take a look at the routing table
and understand what we're directly connected to.
Show ip route.
So, we can see now I'm directly connected
to 172.16.10.0 off of serial 0/1/1.
192.168.10.0 is my LAN right off at fast ethernet 0/0.
And I also have a loopback address.
Now, a loopback interface, very simple to create.
I haven't showed you before.
So, if I said interface loopback question mark
you can see I can create 2.1 billion,
that's not necessarily true,
I can just use that high of a number.
I am limited on some processes.
So, if I just create another loopback
this is gonna be used for diagnostics and so on.
This is exactly what I'm using it for here.
In this case here, I've got a 192.168.40 on that loopback,
zero 192.16.10 is my LAN
and my WAN interface the corp is 172.16.10.
So, I understand this.
So, I'm gonna go ahead and type exit.
Come back, and oops, get into my corp router.
And make sure we verify and understand,
you know, so I can see my 172.16.10.0
connected to serial 0/1/1.
170.16.10 four subnet and 10 eight subnet
are connected to LA.
So, I'm gonna just type in LA,
because we did create a host table on this.
Alright, so let's go ahead and telnet to the LA router.
Notice if I try to use the host name here
and say LA that it's not going to work
Cause there's a command that starts with LA,
so it doesn't know it's a host name so actually
I have to type out the whole command telnet,
and then my password.
Now I can do a show ip route,
and let's see what we got going on.
Don't see any rip injected routes
even though rip is running
because I've turned off my other routers, right?
So, I'm gonna say config t,
I'm gonna turn it off anyways, no router rip.
Now, let's go ahead and take a look
at what we've got going on here.
We're directly connected to 10.4 and 10.8
subnets to the corp router,
show cpd neighbors will show us that as well.
So we'll see I've got my LAN switch,
and I've the corporate router off at serial 0/1/0
and serial 0/0/1, and so those are the 10.4
and 10.8 subnets respectively
with ip addresses dot six and dot 10,
corp routers dot five and dot nine.
192.168.20 is off the LAN,
and off the loopback is 192.168.30.
Alright, that is how we set up our routers.
We understand where each routers at,
what they're directly connected to,
don't have any routing protocols running,
and by the way, to see if you have any protocols running,
I showed you this before,
but if you remember,
show ip protocols, right?
And there's nothing running.
Okay, let's exit back out to the corp
and get ready to configure ip routing.