Changes between Version 3 and Version 4 of Tutorials/Stitching/Procedure


Ignore:
Timestamp:
03/17/15 19:25:21 (9 years ago)
Author:
sedwards@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Tutorials/Stitching/Procedure

    v3 v4  
    9292      </td>
    9393      <td>
    94          <h3><u> 3. Setup the routing </u></h3>
    95          The goal of this exercise is to setup the routing as indicated in <a href="#IPv4RoutingAssignment">Figure 1</a>; i.e.  packets from A sent to IP address 192.168.2.12 on node C should be routed via node B. In order to create this routing behavior you will need to modify the routing tables in your nodes using the linux
    96 <a href ="http://www.hscripts.com/tutorials/linux-commands/route.html"> route command </a>
    97          <h4> Questions: </h4>
     94         <h3><u> 3. Test Connectivity </u></h3>
    9895             <ol>
    99               <li> <b>What happens when you traceroute from A to IP address 192.168.2.12 before you setup the static routes? Why? </b> <br/>Include the output of the traceroute in your writeup</li>
    100               <li> <b>Setup the routing from A to 192.68.2.12 so that it goes through B. Was it enough to just modify the routing tables? What else  did you need to change in order for the traffic to flow? Ensure that you have connectivity by running a ping from A to 192.168.2.12</b> <br/>In your writeup include all the commands you ran and a screenshot of the routing configuration</li>
    101               <li> <b>What happens when you traceroute from A to IP address 192.168.2.12 after you setup the static routes? </b> <br/>In your writeup include a screenshot of the traceroute output.</li>
     96              <li>Log into one of the nodes and ping the other node.</li>
    10297             </ol>       
    103 
    10498          </td>
    10599       </tr>
     
    117111             
    118112               <h3><u> 4. Cleanup </u></h3>
    119            After you are done with the exercise and you have captured everything requested for the writeup, you should release your resources so that other experimenters can use
    120 them. In order to cleanup your slice :
     113           After you are done with the exercise, delete your resources:
    121114              <ol type="a">
    122                  <li>In Flack, press the <b>Delete</b> button in the bottom of your canvas </li>
    123                  <li> Select <b>Delete at used managers</b> and <b>confirm</b> your selection. </li>
     115                 <li> </li>
     116
    124117              </ol>
    125 Wait and after a few moments all the resources will have been released and you will have an empty canvas again. Notice that your slice is still there. There is no way to delete a slice, it will be removed automatically after its expiration date, but remember that a slice is just an empty container so it doesn't take up any resources.
    126               <h3><u> What to hand in: </u></h3>
    127                  <ol>
    128                    <li> A screenshot of your slice when all the nodes are ready.</li>
    129                    <li> The answers to questions 1-3. </li>
    130                    <li> Screenshots of the output of the traceroute command invoked on Node A for IP 192.168.2.2 <b>before</b> and <b>after</b> the setup of static routes. </li>
    131                    <li> Screenshots of the route table of Nodes A, B and C </li>
    132                  </ol>                   
    133           </td>
     118Wait and after a few moments all the resources will have been released and you will have an empty canvas again.
     119         </td>
    134120       </tr>
    135121</table>