Simple Static Routing Experiment

Overview

In this experiment you will learn how to set up static routing with the route command. We will use the following network topology for this experiment:

picture goes here

Set Up

For this experiment you need a GENI account, ssh credentials, and the class VirtualBox image. You also need to set up the experiment with Flukes. If you do not already have this set up, go ​to the setup page for instructions on how to set up your account.

Experiment

The goal of your final experiment is to setup the routing as indicated in Figure 1. You might want to review the slides on IPv4 addressing and routing (also chapter 4.4 in the book)

route picture here

After you have set up the routing correctly, packets from A send to IP address 192.168.2.12 on node C should be routed via node B. Packets from A send to IP address 192.168.3.12 on node C should be directly forwarded to C. You can verify this by performing a traceroute to the respective IP addresses of node C from node A. Since we’re not using a routing algorithm but set the route statically, we will make use of the “route” command. The following link gives you an introduction on how to use the command:

​route command

Remember that you can use “ifconfig” to determine which Ethernet interface (e.g., eth0) is bound to what IP address at each of the nodes.

To enable forwarding of packets on node B you have to execute the following command:

echo 1 > /proc/sys/net/ipv4/ip_forward

To demonstrate that you have set up the routing correctly you have to submit a screenshot from node A that shows traceroutes for both IP addresses of node C. Note: You should document the steps you perform to set up the static routes since all configurations will be lost when your slice is deleted. A new slice will always be in its initial state with NO routing set up!

Finish

1. Return to the Slice page on Portal. On the row in the aggregate table for the aggregate you used, press the Delete Resources button.
2. When prompted, confirm that you want to delete this sliver. Then, make sure you see a message that you have successfully deleted resources at this aggregate.
3. Do this for as many aggregates as you got resources from.