| | 1 | [[PageOutline]] |
| | 2 | = IPv4 Routing Assignment = |
| | 3 | |
| | 4 | {{{ |
| | 5 | #!html |
| | 6 | <table border="0" > |
| | 7 | <tr> |
| | 8 | <td width="350" valign="top"> |
| | 9 | <h3 align="left"> <u>Overview: </u> </h3> |
| | 10 | In this experiment you will learn how to set up static routing with the <em>route</em> command. We will use the following network topology for this experiment: |
| | 11 | <br> |
| | 12 | <img border="0" src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/ECE375/routetopology.png?format=raw" alt="route topology" align="center" width="350" title="route topology" /> |
| | 13 | </td> |
| | 14 | <td> <pre> </pre> </td> |
| | 15 | <td width="350" valign="top"> |
| | 16 | <h3 align="left"> <u>Prerequisites: </u></h3> |
| | 17 | For this tutorial you need : |
| | 18 | <ul> |
| | 19 | <li> <b> access to the <a href="https://portal.geni.net"> GENI Experimenter Portal </a></b> and be a <b> member of a GENI project </b>. <br/>Please see the <a href="http://groups.geni.net/geni/wiki/SignMeUp"> Sign Me Up page for more information. </a></li> |
| | 20 | <li> <b>be familiar with reserving resources in GENI based on an rspec</b>. <br/>If you are not familiar you should first do the <a href="http://groups.geni.net/geni/wiki/GENIExperimenter/Tutorials/RunHelloGENI"> Hello GENI </a> or <a href="http://groups.geni.net/geni/wiki/GENIEducation/SampleAssignments/LabZero/Procedure"> Lab0 </a> </li> |
| | 21 | <li> be familiar with <b><a href="http://groups.geni.net/geni/wiki/HowTo/LoginToNodes" > logging in to GENI resources </a> </b> </li> |
| | 22 | <li> be familiar with <b> IPv4 addressing and routing </b> </li> |
| | 23 | </ul> |
| | 24 | |
| | 25 | </td> |
| | 26 | </tr> |
| | 27 | <tr> |
| | 28 | <td width="350" valign="top"> |
| | 29 | <h3 align="left"> <u>Tools: </u></h3> |
| | 30 | All the tools will already be installed at your nodes. For your reference we are going to use: |
| | 31 | <ul><li><a href="http://www.hscripts.com/tutorials/linux-commands/route.html"> the route linux command </a> </li> </ul> |
| | 32 | |
| | 33 | </td> |
| | 34 | |
| | 35 | <td> <pre> </pre> </td> |
| | 36 | <td width="350" valign="top"> |
| | 37 | <h3 align="left"> <u>Where to get help: </u></h3> |
| | 38 | 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 <a href="mailto:help@geni.net?Subject=Help%20with%20ECE375%20tutorial"> help@geni.net </a> |
| | 39 | </td> |
| | 40 | </tr> |
| | 41 | </table> |
| | 42 | }}} |
| | 43 | |
| | 44 | |
| | 45 | == Set Up == |
| | 46 | |
| | 47 | [[Image(design.png, left)]] |
| | 48 | |
| | 49 | This experiment assumes you have already setup your account at the GENI Portal. In particular ensure that: |
| | 50 | 1. You can login to the [https://portal.geni.net GENI Portal] |
| | 51 | 2. You are a member of a GENI Project (there is at least a project listed under the ''Projects'' tab. |
| | 52 | 3. You have setup your ssh keys (there is at least one key listed under the ''Profile->SSH Keys'' tab. |
| | 53 | |
| | 54 | If all of the above are done then follow these steps to setup the topology for this exercise: |
| | 55 | 4. Login to the [https://portal.geni.net GENI Portal] and create a slice |
| | 56 | 5. Reserve resources within this slice using the [http://www.gpolab.bbn.com/experiment-support/IPRouting/EG-3nodes-mesh.rspec EG-3nodes-mesh] rspec |
| | 57 | |
| | 58 | Wait until your resources are ready and move to the next part. |
| | 59 | |
| | 60 | == Experiment == |
| | 61 | |
| | 62 | [[Image(execute.png, left)]] |
| | 63 | |
| | 64 | 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. In the current setup packets from A to C go directly. : |
| | 65 | 1. Verify the default routing behavior using the [http://en.wikipedia.org/wiki/Traceroute traceroute] linux command. Include the output of the traceroutes commands in your writeup. |
| | 66 | 2. Use the linux [http://www.hscripts.com/tutorials/linux-commands/route.html route command] to create static routes that match the routing behavior of the diagram. Include the routing commands in your writeup. |
| | 67 | 3. Verify that you have created the intended routing behavior using traceroute. Include the output of the traceroutes commands in your writeup along with screenshots from node A that shows traceroutes for both IP addresses of node C. |
| | 68 | [[BR]][[BR]] |
| | 69 | |
| | 70 | '''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.[[BR]] |
| | 71 | '''Note''': In order to enable forwarding of packets on node B you have to execute the following command: |
| | 72 | {{{ |
| | 73 | echo 1 > /proc/sys/net/ipv4/ip_forward |
| | 74 | }}} |
| | 75 | '''Note''': A new slice will always be in its initial state with NO routing set up! |
| | 76 | |
| | 77 | == Finish == |
| | 78 | |
| | 79 | [[Image(finish.png, left)]] |
| | 80 | |
| | 81 | 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. |
| | 82 | 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. |
| | 83 | 3. Do this for as many aggregates as you got resources from. |
