Changes between Version 31 and Version 32 of GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure/Execute


Ignore:
Timestamp:
06/23/16 11:21:59 (5 years ago)
Author:
tteixeir@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure/Execute

    v31 v32  
    5757   * A principal investigator node, called {{{PI}}} and a experimenter node, called {{{Experimenter}}} that will send {{{Interest}}} requests to the {{{Custodian}}} via UDP tunnels.
    5858
     59Download the scripts and Python codes to your computer and extract it.
     60   * [http://192.1.242.151/files/ndn-tutorial.gz ndn-tutorial.gz]
     61                 
     62Or alternatively,
     63     {{{ 
     64     $ wget http://192.1.242.151/files/ndn-tutorial.gz
     65     $ tar -xvf ndn-tutorial.gz
     66     }}} 
     67                 
     68In the '''ndn-tutorial-config.sh''' configuration file, edit the fields according to your GENI username, SSH key, GENI Aggregate name, pc and port numbers.
     69Keep the quotes format unchanged, otherwise the script may not run.
     70                 
     71Run {{{copy-scripts.sh}}}, this will automatically transfer the necessary files to the nodes in our topology.
     72     {{{ 
     73         $ ./copy-scripts.sh
     74     }}}
    5975
    60 Login into the node {{{Custodian}}} and start the NDN Forwarding Daemon (NFD),
     76Login into the node {{{Custodian}}} and re-start the NDN Forwarding Daemon (NFD). This will make sure the content store is refreshed and the routes are cleared.
    6177     {{{
    6278     $ nfd-stop
     
    90106
    91107=== 5.2 Run the NDN application on the entire topology ===
    92 In this section, we are going to start the NFD and register the forwarding faces on the remaining nodes. On your host machine, do the following:
    93 
    94 SSH to the {{{Internet Router}}}, start the NFD and register the forwarding face
    95      {{{
    96      $ nfd-start
    97      $ nfdc register / udp4://10.0.20.2
    98      }}}
    99 
    100 We will repeat the procedure for the {{{Campus Router}}}. Note the different IP address this time.[[br]]
    101 SSH to the {{{Campus Router}}}, start the NFD and register the forwarding face
    102      {{{
    103      $ nfd-start
    104      $ nfdc register / udp4://10.0.10.2
     108In this section, we are going to start the NFD and register the forwarding faces on the remaining nodes. We have automated these tasks for the {{{Campus-Router}}}, {{{Internet-Router}}}, and {{{PI}}} nodes using a script. On your host machine, do the following:
     109     {{{ 
     110     $ ./setup-app.sh
    105111     }}}
    106112
     
    113119     }}}
    114120
    115 SSH to the {{{Experimenter}}} node, register the namespace, and start the {{{consumer}}} application
     121SSH to the {{{Experimenter}}} node, register the namespace, and start the consumer application
    116122     {{{
    117123     $ nfdc register / udp4://10.0.0.1
     
    121127This time the {{{Interest}}} request travels the entire topology, leaving breadcrumbs. The {{{Data}}} packet follows the breadcrumbs back to the {{{consumer}}}, leaving cached versions of the content. This is call in-network caching and it is one of the most important features in {{{Information Centric Networking (ICN)}}}
    122128You can check this phenomenon by running the same consumer application in the {{{PI}}} node.
    123 SSH to the {{{PI}}} node, register the namespace, and start the {{{consumer}}} application
     129SSH to the {{{PI}}} node and start the consumer application
    124130     {{{
    125     $ nfdc register / udp4://10.0.0.1
    126131     $ cd /local
    127132     $ python consumer.py -u /nytimes/science
    128133     }}}
    129 This time your {{{PI}}} node gets the content back, but nothing happens on the {{{Custodian}}} because the requested content is cached in the {{{University}}} node.
     134This time your {{{PI}}} node gets the content back, but nothing happens on the {{{Custodian}}} because the requested content is cached in the {{{Campus Router}}} node.
    130135You can repeat the experiment with different namespaces
    131136     {{{