Now our last network command is going to be our route. Command now around command allows us to view and modify our internal computer routing table. Now. We talked a little bit about routing tables with what we talked a lot about, about about our routing tables in our previous module on routers.
But it's essential to know that our computers themselves also have routing tables.
These routing tables allow us to know how to connect to other computers on our network. How to connect computers outside our network, in which interfaces in which gateways that we need to use Wilmore connecting to these computers to these other networks. This is also extremely important, say, when we're connecting to computers
when we're on a computer with multiple network interface cards
and our computer needs to know which network interface card to use when it's trying to connect to a certain network and what gateway it needs to connect to in order to connect to those networks. So our route command has several different options. We can associate with it our first command. Our first option is going to be print now. Route Space Print
is going to print our current routing table. It was going to show us all of our different routing table options.
If we see something that says on Link, that means we can directly connect to that device without having to go through an additional router. Weaken just connected that, say, threw a switch or hub or just a cable directly connected to it
and then devices that are not on link. It will show us what our gateway is, what device were connecting to before we can connect to those devices.
Next we have our route space, dash F, and this is going to clear all the entries out of our routing table. Now, this isn't something to be taken lightly, especially if you set a lot of static routes on a device. If you clear out your routing table entries, you won't be able to connect to anybody for a little bit
unless you go and immediately set manual entries.
This route space Dash F is going to clear all of your routing table entries so your computer doesn't know how to get to anyone, so you need to know you need to understand the implications of doing a route dash F before you just run one. And if you have a device like a server that serves a lot of different clients or, uh,
a domain controller or a router itself,
you don't want to just,
you know, at the drop of a hat and run a route dash f and clear out that routing table and say, Oh, well, there's a bad route or two in here, but I don't feel like going through and manually changing them. Yes, spend the time and manually change them because running a route dash F, especially on a device which routes a lot of traffic throughout a network,
you're gonna have to have a talk with somebody or you're gonna need to talk with somebody. And you're going to need to confer with several different people before you run that because that's gonna clear out that routing table and that device not going to be able to connect to any of the devices that it previously was able to connect to, and neither is gonna have toe spend a long time and wait for the next
cycle in order to receive the routing table information
or it's going to need to have round tables manually set
Next, we have, ah, route space, dash our space. Add on and this is going to come in when we're running our We're talking about a command here and when we see and when we run ad that's going to add a new route to our routing table.
Change is going to change an existing route in our routing table and delete is going to delete an existing route from our routing table with our add change and delete
these all use. Several options that we have here are masked. Option is going to specify the network mask of where we're connecting two is going to specify the network portion.
I f is going to specify the interface that we're connecting over, and our metric is essentially going to specify the route cost. So if we have multiple different routes that we can use to connect to a certain location than our computer is gonna want to use, the one with a lower route are a lower cost.
So we have our we have an example of adding a ah, a new route to a routing table, and first we're gonna talk about our syntax up here And then after that, we're gonna replace the syntax with actual i p addresses on actual values.
So we have our route ad and then whatever
destination we're trying to connect to whatever destination network we're trying to connect to
Mask and the sub net mask of that destination network,
followed by the gateway of that destination network. Essentially the gateway router that we're going to go through
metric and then following that, the value of this route, the metric of this route, the cost
If for interface. And then we're specifying what interface that we're using. We're connecting. We're specifying what network interface card interface were using as we're one we're using connecting this route.
now let's replace this with actual numbers. So route add 1 57 0.0 That one. We're connecting to the 1 57 dozen without 00 network
with the sub net. Matt, that and that network has a sub net mask of 2 55 to 50 to 55 000
The gateway for that we're going to use to connect into this network is going to be 1 57 55.80 dot one.
The metric for this particular route is going to be three in the interface that we're going to use in order to connect is going to be, too.
And all of this is going to be on one line and then we'll hit. Return will hit enter.
if we're using devices. If we're modifying a computer that has static route set this route command is a very important command to know in a very important command to get the syntax right on the way that we form with the way that we order the words right. We need to make sure that we have that correct so that we can add change or delete routes.
Or if we just want to view the current routes that we have
in our routing table. Then we know that we just have the Route Space Print Command that we can just print those routes. So use those commands in the proper situations, use the dash f very cautiously, and we'll be able to use that route command in order to help us make our network connections.
So thank you for joining us here today on Cyberia today we talked about several different software tools that we can use in order to troubleshoot network connectivity issues. We talked about everything from our protocol analyzers to our different command prompt commands that we can run in order to troubleshoot network connectivity issues.
So feel free to take these and just practice with them and play with them
in a test environment in order to see how they function and to get an idea of how they work. Make sure that you establish baselines so that you know what your network looks like when it's functioning normally. And make sure you play a lot with those command prompt commands and that you get get the syntax down and you get the wording of them down and what they do.
That way, if you need to use them, you can and that you'll be able to use them properly
and you'll be able to use them without having many errors or having unexpected results. So again, thank you for joining us here today. We hope you learned something that you can add to your toolbox, and we hope that we can see here next time on Cyberia