IPv4 Static Routes 1

By certskills May 9, 2016 09:05

One of the best ways to learn IPv4 routing is to think hard about IPv4 static routes. Today’s lab gives you more of that with a typical config lab. It starts with a topology and with IPv4 addresses configured. Your job: add IPv4 static routes for all remote subnets on all four routers in the topology.



Configure static IPv4 routes on the routers shown in the figure so that each router can forward packets to all the subnets shown in the figure. The specific rules for this lab are:

  • Configure static routes on each of the four routers
  • Configure static routes to each subnet that is not a connected subnet
  • Assumptions:
    • All router interfaces shown in the lab are up, working and have correct IPv4 addresses assigned per the figure
    • All PCs have been configured with an IPv4 address and are working



Figure 1: Simple Hub and Spoke Topology


Initial Configuration

Examples 1, 2, 3 and 4 show the beginning configuration state of Core, Branch1, Branch2 and Branch3.


Example 1: Core Config


Example 2: Branch1 Config


Example 3: Branch2 Config


Example 4: Branch3 Config


Answer on Paper, or Maybe Test in Lab

Next, write your answer on paper. Or if you have some real gear, or other tools, configure the lab with those tools.

If you do implement the entire network in a lab, you can test the solution by going to each PC and pinging the other three. All the pings should work. Additionally, you could use an extended ping command to ping from each router’s G0/2 interface to each other router’s G0/2 interface IP address. For instance, from R1, the command ping source would test the forward route to R4’s G0/2 subnet, and the reverse route back to R1’s G0/2 subnet. Finally, issuing a traceroute command from any of the PCs in the lab would let you see the path through the network.


Do This Lab with Cisco’s VIRL

You can do these labs on paper and still get a lot out of the lab. As an extra help, we have added files for the Virtual Internet Routing Lab (VIRL) software as well. The .VIRL file found here is a file that when used with VIRL will load a lab topology similar to this lab’s topology, with the initial configuration shown in the lab as well. This section lists any differences between the lab exercise and the .VIRL file’s topology and configuration.

Download this lab’s VIRL file!

All interfaces in topology match the lab figure.

Network Device Info:

The switches used for this lab are all unmanaged layer 2 switches.

Host device info:

This table lists host information pre-configured in VIRL, information that might not be required by the lab but may be useful to you.

Device IP Address User/password
PC1 cisco/cisco
PC2 cisco/cisco
PC3 cisco/cisco


Handy Host Commands:

To see PC IP address: ifconfig eth1

Ping example: ping -c 4

Trace example: tracepath

To connect to another node within the topology: telnet

Answers: IPv6 Special Addresses 1
Answers: IPv4 Static Routes 1
By certskills May 9, 2016 09:05
Write a comment


  1. LT April 9, 18:42

    There’s a typo in the initial configs above. Core router interface Gi0/3 and router Branch3 interface Gi0/1 have the same IP address. Branch3 should be

    Reply to this comment
View comments

Write a comment

Comment; Identify w/ Social Media or Email


Subscribe to our mailing list and get interesting stuff and updates to your email inbox.

Thank you for subscribing.

Something went wrong.