Version 6 (modified by 11 years ago) (diff) | ,
---|
IPv4 Routing Assignment
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: |
|
Prerequisites:For this tutorial you need :
|
Tools:All the tools will already be installed at your nodes. For your reference we are going to use: |
|
Where to get help:For any questions or problem with the tutorial ask your TA or Professor for help. If you are doing this exercise outside the context of a course, please email help@geni.net |
Set Up
This experiment assumes you have already setup your account at the GENI Portal. In particular ensure that:
- You can login to the GENI Portal
- You are a member of a GENI Project (there is at least a project listed under the Projects tab.
- You have setup your ssh keys (there is at least one key listed under the Profile->SSH Keys tab.
If all of the above are done then follow these steps to setup the topology for this exercise:
- Login to the GENI Portal and create a slice
- Reserve resources within this slice using the EG-3nodes-mesh rspec
Wait until your resources are ready and move to the next part.
Hand in: A screenshot of the topology after it is ready from Flack.
Experiment
The goal of this exercise is to setup the routing as indicated in Figure 1; i.e. packets from A send to IP address 192.168.2.12 on node C should be routed via node B. The default behavior between your nodes is different.
Question 1
Verify the default routing behavior using the traceroute linux command.
Hand in: Screenshots with the output of the traceroutes commands.
Question 2
Use the linux route command to create static routes that match the routing behavior of the diagram.
Hand in:The routing commands your ran. The final route configuration.
Question 3
Verify that you have created the intended routing behavior using traceroute.
Hand in: Screenshots from node A that shows traceroutes for both IP addresses of node C.
Tips
Note: 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.
Note: In order to enable forwarding of packets on node B you have to execute the following command:
echo 1 > /proc/sys/net/ipv4/ip_forward
Note: A new slice will always be in its initial state with NO routing set up!
Finish
- Return to the Slice page on Portal. On the row in the aggregate table for the aggregate you used, press the Delete Resources button.
- 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.
- Do this for as many aggregates as you got resources from.
Attachments (1)
- routetopology.png (106.3 KB) - added by 11 years ago.
Download all attachments as: .zip