Routing tables map destination networks to their next-hop addresses, organizing entries into three categories: directly connected networks, remote networks, and the router's own local interface. Understanding these distinctions is foundational to how routers make forwarding decisions.
Routing Tables Overview
Our routing table is just a list of destination networks, so it has a list of networks and what is the next hop. There's really three different kinds of networks that we'll see within here.
One is a local network. Here we have a directly connected network to this router. When we have an interface on the router and we assign an IP address to it, it recognizes that that IP address that's assigned to it, there's a whole network that that's a part of. So it will recognize this network right here. It's actually connected to two other directly connected networks, this one right here and this one right here. So those are all directly connected networks.
Then it also has a destination network of possibly some remote network. So here in this example right here we have a remote network that this router is going to need to know the location of. In order for it to get packets to there, then it needs to know of that remote network. So we have our directly connected networks, we have our remote networks.
There's actually two more remote networks that are here, and that's this link right here and this link right here. This router may or may not need to know about those networks right there for it to get to this final destination right here. It just needs to know about this remote network and the next hop, so it doesn't necessarily need to know about these networks right here. But in a lot of cases, for instance, if this router wants to communicate with this router, then it will probably need to know about this network right here. For the most part — there are some exceptions to that — those are remote networks.
So we've got directly connected networks, we've got remote networks, and we also have the machine itself. The machine itself, the local link: some traffic is actually destined for that router. It could be taking that information in, and perhaps it's some sort of management traffic to get on and SSH onto that machine, or to analyze, to do some sort of network management. It's managing those links. So there's reasons for us to communicate directly to that router. We can make a connection to the router, it has directly connected networks, and it has remote networks.
I'm on a router here and I thought we could look at these three different types of destination networks.
First of all is that directly connected network. It's a network that's connected to this machine. This is labeled with a C. As we see here, here's one right here, so that's a C. Here's two of them right here, those are both C's, and this one. So according to this there are four directly connected networks.
The other thing that I had mentioned is that there's the local link, the local interface, and so that is the L right here. The L is the local. So we see that this is the actual IP address of this router right here, which is 10.240.0.2, and we have another one which is 10.240.2.2. So those are IP addresses that are actually assigned on the machine.
The rest of these are remote networks. So this 10.110.0 is some other network that's been actually learned. If we look at this, this is learned through OSPF. We haven't learned about how these actual routes get into here, but this is showing us that it's learned it through OSPF.
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 →