How do packet knows where to go from the host computer, whether it’s desktop workstation or home router to the destination? The answer is the routing table (also called the forwarding table), which contains rules, where to send the packet, based on the destination IP address. Every hop in the route to the final destination, contains routing table, to decide where to forward packet next.

What does routing table contains?

Viewing routing table is pretty straightforward. Under the Linux, using: netstat -r -n or route -n will do the trick. In other OS there must be similar tools. Here is output from the netstat running on the local machine:

netstat -r -n

Destination Gateway Genmask Flags MSS Window irtt Iface UG 0 0 0 wlp2s0 U 0 0 0 wlp2s0 U 0 0 0 docker0 U 0 0 0 wlp2s0

The most important fields here are: Destination, Gateway, Genmask and Iface, all others are additional to show some table related information and can be examined in manual.

Let’s go over main fields:


This field can be anything, the network, particular host or multi-cast address. This field is matched with the IP address from the source packet to choose what route to take. What does address means? This address has different meanings in different context, when used in destination field, it indicates that if nothing matched in routing table, then you use this one.


This field is used to tell whether the destination is on the local network, in this case it can be directly forwarded to the destination host, otherwise, it’s on a remote network, then it must be sent to the gateway address, which use it’s own routing table and will forward data-gram further. What does address means in gateway? It says that the destination host is directly connected to the network and no need to use gateway router.


Bit mask that is used in combination with data-gram IP address to find appropriate entry in a routing table destination field and use gateway field to decide where to send data.


Network interface that is using the send the data. In the output above, the wlp2s0 indicates the Wireless card and docker0 is what the name says, network interface used for Docker.

Do hosts have routing tables?

Better question would be - why they contain the routing table? Isn’t only router need to use this table? The reason why hosts need routing table is to move traffic on the local network, if the destination address not on the LAN, then we need to send packet to the gateway, otherwise just use the destination MAC address and send the packet directly to the destination host.

How routing table is updated?

The routing table can be updated manually (static) or using protocols that are used to find networks and update routing tables on routers (dynamic). Network with a limited number of gateways is good candidate for static routing. Routes can be added/deleted using route command. Static routing is static, it’s not adjusted to network changes, if it’s needed to react on network changes than dynamic routing is a way to go. Dynamic routing is achieved using routing protocols which can reflect network changes (destination not reachable, new best route available, etc) in routing table and must be used in large networks if more than one route is can used to reach the destination.