Routing tables store the routes a router uses to forward packets toward their destination, identifying each path by a next-hop IP address or exit interface. This content examines what routing table entries contain and demonstrates how to read them on both a Windows host and a Cisco router.
Routing Tables & Routes
We know that a packet that comes into the router is going to look up on the routing table to determine what is the next best hop. But what is inside of that routing table? Well, the routing table has a bunch of routes in it. It's just how it can get to this location, this network. So within that routing table, it'll have a list of networks and where it is that that packet needs to go in order to send it in the direction towards that network. We call those routes. The routes are just what networks are within the reach of that router, and what direction it needs to go, or what's the next best hop. And so the information will be looked up and then it will send it to the next best hop.
Now, as we mentioned, this routing table has a list of networks that are in it, and then where the destination is, what the next hop is. And it can specify this by one of two different ways. Number one is it could just specify what the next hop address is, how it's going to get to that next hop address. Or it could specify it by the exit interface. So often we'll see an IP address for the next hop interface, or we'll see just the exit interface outside of this router right here. But that's what you'll find within these routing tables. So it knows, if I'm trying to get to this network, what I need to do is send it to this destination IP address next — that's my next hop — or I need to send it out this interface.
I thought it'd be a great idea to take a look at what these routes actually look like. So I'm going to hit the start button here. I'm going to type in cmd and bring up a command prompt. And then I'll just type in route print and hit enter. And what we can see here, I'm going to scroll up to the IP version 4 routing table. So this is the routing table, and in here, we've got a bunch of routes. Each one of these lines is a separate route.
So what do we have part of this? We have the destination network, so this is the network destination. If it's going to something in the 10.0.0.0 range, then this is the network mask. This is the gateway for that. So it's got a bunch of information here: the gateway on how to get to that network, the interface that it's going to use, and something called a metric. We don't need to be too concerned about all of this at this point in time, but just know that each one of these is a route in this routing table.
Let's also take a look at a route on a router. So here I've SSHed into this router right here. If I do a show ip route, this is what comes up. So this is the routing table, and in this routing table here are all of the different routes. So what do we have here? Once again, we have the destination network here. So these are all the destination networks. We've got some information here — this is what's actually the metric there — but it tells us what the next hop is. So the next hop here is 10.240.0.1, and that exit interface needs to go out FastEthernet0/1 to reach this 10.240.0.1, to reach this network right here.
There's quite a bit of other information in here. We see how it learned of this route, and if it's a link local, and if it's directly connected. So we've got some other information in here, but essentially the goal here is just to take a look at each one of these.
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →